This article will discuss project roles, including what they are, how to use them, and the primary role. Project roles are used in Taskflow. Roles make it possible to assign the tasks based on responsibilities in the project, rather than on the specific user.
Any user can be given a project role on a specific project by a project Admin. To assign a role for more than one project, use the Org > Members tool. The Mass Update Permissions Advanced tool can also be used to assign project roles for all existing projects or for a subset of existing projects.
To assign a role for a single project, follow the steps below.
- Navigate to the Team section. Search for and click on the desired project in the “Search for a project” search box in the top left corner. In this project, find and select the “Team” section from the lefthand side menu.
- Find the user. In the Team section, find the user by clicking on “Guests,” “Followers,” or “Collaborators,” depending on the user’s team status. Search for the user in the “Filter project [team status]” box. Once you’ve located the user card of the user, click on it to open the options menu.
- Select “Other Roles.” Click on the “Other Roles” option to open a list of possible roles.
- Choose and save roles. In the list of other roles, click on a role to select it for that user. Hold Ctrl (⌘ for Macs) to select multiple roles at once, and then click “Save.”
- (Optional) Make a primary. If your user is a follower, you will have the option to make them a primary. Click on that user card, and select “Make *Primary” from the options. If you’d like to make a non-followers user a primary, you will need to move them to followers first.
“Primary/*primary” is a special type of role. The primary is the lead role on a project and is the one responsible for most tasks and deadlines. Taskflow task assignments will default to the primary if the task does not have an assignee or if a user with the assigned role is not present. Refer to the table on taskflow logic for more detail.
Every project must have a primary role, and that primary should always be a follower. If a project has multiple primaries, the *primary, or “first primary,” will fulfill the role of primary.
By default, the *primary role will be assigned automatically to the user who creates the project. Project Admins can change the *primary assignment. Steps for making a user a *primary can be found in the Assigning Roles step-by-step above.
When a *primary is created, the current primary will be moved, the current *primary will automatically be moved to primary.