Roles and access
In Assist there is no single set of capabilities for everyone: each person is assigned a role, and the role defines what they see and what they can do. That is why colleagues' menus and buttons may differ. This is expected behavior, not an error.
What a role's permissions consist of
| Level | What it defines | Example |
|---|---|---|
| Pages | Which menu items and screens are available | The role has no permission for the “Roles” page, the item is hidden |
| Page tabs | Which tabs are visible inside a project, release, and task | A project's “Tracks” tab is hidden |
| Collections | What can be done with data: view, create, change, delete | Tasks can be viewed and changed but not deleted |
| Record scope | Which records are available: all, only projects where you are on the team, or only your own | An assignee sees tasks only of their projects |
| Fields | Access to individual fields of a record | The “Rate” field is hidden |
| Special permissions | Exceptions to the general rules | Logging time retroactively |
Default roles
Assist has three main roles. The administrator can change their permissions, create new roles, and copy existing ones.
| Role | For whom | Typical capabilities |
|---|---|---|
| Admin | The cabinet administrator | Sees and configures everything, including roles, workflows, fields, users, notification transports |
| Manager | A project manager | Works with projects, releases, tasks, and the team; sees the “Team” mode on “My work”; views reports |
| Developer | An assignee. The default role for new users | Works with tasks in available projects, writes comments, logs time |
The exact set of permissions of any role is shown in the role editor. The summary table: “Permission matrix”.
How to find out what is available to you
- Look at the left menu: what is not in the menu is unavailable to you as a page.
- Open a project, release, or task and look at the tabs: a hidden tab is unavailable.
- If there is no pencil next to a field, your role has no permission to change this field.
- If the buttons Create …, Delete, Apply transition are absent or inactive, there is no corresponding permission or the conditions are not met (for example, a transition gate).
Why a colleague sees more or less
| Cause | How to check |
|---|---|
| They have a different role | The administrator opens Admin → Users and looks at the “Role” column |
| You are not on the project team, and the role's scope is limited to team projects | Open the project's “Settings” tab and look at the “Project team” block |
| The record is hidden by the “Hide final stages” filter | Turn the switch off in the list |
| The record is deleted | Check the audit log |
What to do if the needed section is missing
- Make sure you are signed in under your own account: “My sessions”.
- Contact the administrator and name the section or action you need and why.
- The administrator will add a permission to your role or assign another role. After the change, refresh the page in the browser.
The role of an API key
An API key gets the permissions of the role you chose when creating it. For a key you can choose your own role or a role with lower priority. Role priorities are shown in the role list. More: “API keys”.
What next
- How to configure roles: “Roles” and the process “Users and roles”.
- Which permissions are needed for which screen: “Permission matrix”.