Skip to main content

Introduction to the permissions of the roles in tasks and projects


Introduction to Roles

Different roles have different permissions in tasks and projects.

Task: owner (creator has the same permissions as owner), task member

Project: owner, administrator and project members

Subtasks: Owners and members

The following figure provides a detailed description of each role in tasks and projects.

I. Projects and tasks

Permissions of the roles in the project to the tasks in the project

  1. Permissions to view details of all tasks under the project:

Project owner and project administrator have this permission.

For the project members and the people to whom the project is visible, set the permission as needed.

  1. Permission to modify task information, for example, adjust the board, modify task name, description, etc.

Project owner and project administrator have this permission.

Other people do not have this permission.

Permissions of the roles in the task for the project to which the task belongs

  1. Task owners and members can only view the project name, and the board (phase) to which the task belongs. Clicking on the project name or board will indicate no permission.

  2. Task owners and members cannot view other tasks in the project to which the task belongs that they are not involved in.

  3. Task owners and members cannot adjust the board (phase) to which this task belongs, nor can they view other boards (phases) of the project to which the task belongs.

Tips: A project member or a person to whom the project is visible can modify the board (phase) of the task if he/she is also a member of the task, but cannot modify it if he/she is not a member of the task, and can only view it.

II. Tasks and subtasks

Task - Subtask

  1. Task owner can view the details of all subtasks, including subtasks of subtasks.

  2. Task members can only see the names of all subtasks in this task, and cannot view the details.

Subtask - Task

  1. Subtask owners and members can only see the names of the tasks they belong to, not the details.

Add project members and set project visibility

Select the project and click [Details] to add or set it.


Project members' permissions to view tasks in the project

Project administrators can set permissions for project members (and members of the groups the project is visible to) to view tasks.

There are three kinds of permissions:

1. View all tasks in the project and their details.

Project members can view the details of the task regardless of whether they are involved in the task or not .

2. View the titles of all tasks in the project, but not the details of unparticipated tasks.

Project members can only view the details of tasks that they are involved in. For tasks they are not participating in, project members can only see the task name and can apply to join the task.

3. Project members cannot view tasks they are not participating in and cannot view details).

Settings:

As shown in the picture below, click the project name and the top right button, and select [Options] to set it.


About adding members

Project or task members can receive notifications about discussion updates and be able to participate in discussions. So how do we add members after we create a task or project?

We can make use of the RACI model.

RACI is a model that provides a relatively intuitive description of the roles and responsibilities in project management. There are processes in an organization that cannot be done spontaneously or automatically, and someone must play a role in them.

  • Who performs (R = Responsible). It is the role responsible for performing the task.

  • Who is responsible (A = Accountable). It is the role that is fully responsible for the task, and only after its approval or signature, the project can be carried out.

  • Who is Consulted (C = Consulted). It is the person who provides the specified advice before or during the implementation of the task.

  • Who is informed (I = Informed). It is the person who is informed of the results in a timely manner and does not have to be consulted or asked for advice.


Have questions about this article? Send us feedback