Migration and editing permissions -- effect project plan

Question

Editing permissions are copied from Paratext 7 to Paratext 8 during migration. This can potentially cause problems if a project plan is used to manage permissions after migration. The editing permissions that are set in Users, Roles and Permissions override the attempts of the project plan to give and take away permissions as work on the translation project progresses. The potential exists for more than one person having editing permission for the same verse. It is recommended that the permissions in Users Roles and Permissions be set to none when a project plan is used. At the very least, administrators should be aware of how project plans and Users, Roles and Permissions can interact and use the appropriate caution.

Answer 1

It is somewhat different for a Back Translation project linked to a project. In the Project Plan you cannot give permission to edit the BT and you don’t want to give permission to edit the translation itself, because the person doing the BT is different from the translator for that book. In the Assignment of tasks, you can assign the preparing of a BT for a book to a certain person but that does not give this person editing rights to that book. This has to be done through the main User Roles and Permissions for the BT project. Whether this is by design I do not know.

Comments

Okay, I see. The bug is that assigning a back translation check to a user gives them edit permissions for the main project. I’ll write it up.

---

It seems to me that if the following setting is used in the Project Plan, a person is not given editing privileges for the base project when he is assigned a task for the Back Translation.

image.png860×453 23.1 KB

---

Thanks, I had already done that for every task. The problem is not from the Project Plan, but from the assignment of the check Back Translation Status Complete.
I can manage it by keeping that particular check unassigned.

---

Based on this screen capture, then Iver+Larsen has found a bug.

---

He did find a bug and I’ve written it up (see my previous post).

Answer 2

If you would like to manage the permissions manually and still have a project plan, you can make the Requires Editing field for all tasks be No. This will keep the project plan from changing the book permissions.

Comments

Yes, this is possible, but would take away one of the advantages of using a project plan. I know of at least one team where the team leader gives every team member permission for everything. The combinations are many. I want to encourage what is the use case we expect most teams to follow.