---
title: Roles & permissions
slug: roles-and-permissions
icon: 🚦
docTags: 
createdAt: 2024-09-26T13:13:07.184Z
---

# Organization roles

In an **organization**, a user can have one or several of the following roles: 

`Member`, `Time reporter`, `Time report manager`, `Team manager` and `Admin`. 

The table below describes the high-level access (in terms of features and actions) granted to each role. 

:::hint{type="info"}
Organization roles control organization-level features and actions. These are configured from [Organization administration](docId\:xSnwYhqVd7uQpHL1Iglgn).
:::

|                                 | **Member** | **Time reporter** | **Time report manager** | **Team manager** | **Admin** |
| ------------------------------- | ---------- | ----------------- | ----------------------- | ---------------- | --------- |
| **My tasks**                    | ✅          | ✅                 | ✅                       | ✅                | ✅         |
| **Campus**                      | ✅          | ✅                 | ✅                       | ✅                | ✅         |
| Peer productivity               | ✅          | ✅                 | ✅                       | ✅                | ✅         |
| User productivity               | ✅          | ✅                 | ✅                       | ✅                | ✅         |
| My performance                  | ✅          | ✅                 | ✅                       | ✅                | ✅         |
| **Team management**             | ❌          | ❌                 | ✅                       | ✅                | ✅         |
| Teams                           | ❌          | ❌                 | ❌                       | ✅                | ✅         |
| Productivity insights           | ❌          | ❌                 | ❌                       | ✅                | ✅         |
| Idle members                    | ❌          | ❌                 | ❌                       | ✅                | ✅         |
| Manage team reports             | ❌          | ❌                 | ✅                       | ❌                | ✅         |
| **Organization administration** | ❌          | ❌                 | ❌                       | ❌                | ✅         |
| User management                 | ❌          | ❌                 | ❌                       | ❌                | ✅         |
| **Report time**                 | ❌          | ✅                 | ❌                       | ❌                | ❌         |

# Workspace roles

In a workspace, a user that is part of the organisation that owns the workspace can have one or several of the following roles: 

`Member`, `Annotation manager`, `Project manager`, `Developer` and `Admin`. 

If a user is part of an organisation that has been invited as a collaborator to the workspace, the roles available to them will depend on the collaboration type assigned to their organisation. How workspace roles relate to collaborator types are described in [this table](https://docs.kognic.com/collaborators#CQURK). 

The table below describes the high-level access (in terms of features and actions) granted to each role. 

:::hint{type="info"}
Workspace roles control workspace-level features and actions. These are configured from [Workspace administration](docId\:YBgkK5zAWzVfUHnD9Sq-L).

Whether someone can access request-level features and actions will depend on their organisation's assigned [request role](docId\:ofZICvod6cGlj5sUvji6T) in the specific request.
:::

|                              | **Member** | **Annotation manager** | **Project manager** | **Developer** | **Admin** |
| ---------------------------- | ---------- | ---------------------- | ------------------- | ------------- | --------- |
| **Receive tasks**            | ✅          | ✅                      | ✅                   | ✅             | ✅         |
| **Project management**       | ❌          | ✅                      | ✅                   | ✅             | ✅         |
| Create projects              | ❌          | ❌                      | ✅                   | ❌             | ✅         |
| Create request               | ❌          | ❌                      | ✅                   | ❌             | ✅         |
| Request                      | ❌          | ✅                      | ✅                   | ✅             | ✅         |
| Annotation instructions      | ❌          | ❌                      | ✅                   | ✅             | ✅         |
| **Data Orchestration**       | ❌          | ❌                      | ❌                   | ✅             | ✅         |
| Scenes                       | ❌          | ❌                      | ❌                   | ✅             | ✅         |
| Integrations                 | ❌          | ❌                      | ❌                   | ✅             | ✅         |
| **Workspace administration** | ❌          | ✅                      | ✅                   | ✅             | ✅         |
| Workspace settings           | ❌          | ❌                      | ❌                   | ❌             | ✅         |
| Members                      | ❌          | ✅                      | ✅                   | ✅             | ✅         |
| Collaborators                | ❌          | ❌                      | ✅                   | ✅             | ✅         |
| **API credentials**          | ❌          | ❌                      | ❌                   | ✅             | ✅         |

# FAQ

**Why can’t a user see Project Management or request details even after being added to a workspace?**

Adding the user as member of a workspace is not enough. Make sure that the following conditions are true: 

1. The organization that the user belongs to are added as a [collaborator](docId\:cQcqf1jwpZOH14g580-b0) with type `Annotation Partner` , `Producer Partner` or `Data Partner`.
2. The organization has [project access](https://app.archbee.com/docs/a_Z2X5g73vsVY_af9aUDR/cQcqf1jwpZOH14g580-b0#UWTb1) configured for the relevant project.
3. The organization is added as a request producer of the request.
4. The user is assigned the workspace role `Annotation manager`, `Project manager` or `Developer`.