Editing rights are not to be mistaken for roles. Roles are always global permissions, while the editing permissions discussed here can be set individually for project master data/settings, tasks and subtasks in order to lock these objects and prevent them from being edited falsely or accidentally. If you want to learn more about roles, follow the link βοΈ.
Sometimes there are things that are best left unchanged π€·. Maybe a task has sensitive or important field information or description text that only you and 2-3 other people should be able to edit. This is where editing permissions come into play.
The permission settings of objects determine whether members are allowed to edit them or not.
Permissions overview
For which objects can editing permissions be set?
- Project master data and project settings: The master data and settings are locked and are read-only. The permission applies to both master data and settings at the project level.
- Tasks: All fields of a task are locked and can only be changed by authorized persons. All others have read-only access.
- Subtasks: All fields of a subtask are locked and are changeable only for authorized persons. All others have read-only access.
Difference between permissions and visibility (of projects)
Editing permissions determine whether members are allowed to edit objects or not. The visibility of projects, on the other hand, determines whether a project receives the private tag and thus becomes invisible to all those who have not been explicitly added in the project settings.
The visibility of projects can be configured under Manage project
> Settings
> Visibility
Learn more.
The visibility of tasks cannot be restricted. If you see a project, all the tasks it contains are also visible for you.
Who can edit restricted objects or remove the restriction?
If the editing permissions are restricted in an object (a task / a project), the following persons (groups) always retain the editing rights:
- Administrators
- The person who has restricted the object
In addition, other persons (groups) can be selected who should have editing permission.
Everyone of the persons mentioned above can also remove the restriction.
Important: If editing permissions are restricted in an object, all persons (groups of persons) except those mentioned above have read-only rights. In addition, comments can always be made (in tasks), regardless of the status of the permission.
Restrict editing permissions in projects (master data / settings)
An active restriction always applies to master data and settings.
- Open the project master data via
Options
>Manage project
- Choose the lock symbol π in the action buttons to
Manage access
- Choose
Restrict access
- After enabling the restriction, all persons who still have editing rights are always displayed above the search field. "Everyone" will have read-only rights from this moment on. Administrators always have the right to edit a task or to remove the restriction.
Restrict editing permissions in tasks/subtasks
- Open a task/subtask
- Select the lock icon from the action buttons πto
Manage access
- Choose
Restrict access
Note that in the default setting (without restriction) "Everyone" will have full access. This is the normal behavior when editing tasks. - After enabling the restriction, all persons who still have editing rights are always displayed above the search field. "Everyone" will have read-only rights from this moment on. Administrators always have the right to edit a task or to remove the restriction.
Making Tasks (including Subtasks) Private
Once a task is restricted, another permission option appears: Make Private.
Private tasks are only visible to individuals who explicitly have the permission. For all others, these tasks are completely invisible. It can also be determined for authorized individuals whether they should have read-only access or full access.
Private tasks are private and cannot be viewed or altered by admins, unlike writing restrictions.
To make a task visible again, there are two options:
- Click on
Remove Restriction
: Makes the task visible to everyone and removes any other restrictions. - Click on
Make public
: Makes the task visible to everyone, but any writing restrictions remain in place.
Differences Between Writing Restrictions and Private Marking
- Editing rights can be restricted at all task levels (main task, subtask, all further subtask levels).
- The option to mark as private is only available at the main task level and always applies to the entire task including all subtasks (at all levels).
- If a task along with its subtasks is marked as private, the private marking cannot be removed at the subtask level, but only at the main task level.
Request editing permission
If you want to inform the person who has restricted an object that you would like to be included in the group of people with editing permission, you can send a request.
Option 1: Point to the lock icon π in the task or project and select in the tooltip Request access
.
Option 2: Open the menu for managing access and select Request access
.
An email and in-app notification will then be sent to the person who initially locked the task.
Note: Admins can always bypass the restriction and unlock it or make changes regardless of the restriction.
Remove the editing restriction
Prerequisite: You must be authorized to edit in the respective object.
- Open the task/project
- Select the lock symbol π among the action buttons to
Manage access
- The restriction can be removed in two ways:
- By hovering over the icon and selecting
Remove lock
- By opening the permissions menu and selecting
Remove restriction
- By hovering over the icon and selecting
Note
In the course of introducing the setting of editing rights on objects, a change in the marking of private projects was introduced. Previously, private projects were marked with a π
in the project portfolio and other places for authorized persons. The new way shows a Private
label marking private projects:
The lock symbol π
now stands for restricted editing rights across the system. It is displayed in projects as well as in tasks in the different views.
Comments
0 comments
Please sign in to leave a comment.