Permission management in awork
Configure permission roles in awork's Rechtemanagement settings to control workspace and project-level access and editing rights for your team members.
Control who can see and edit what. Learn how to manage permissions efficiently.
Key benefits and use cases
- Easy role management: Understand who has access to what.
- Clear structure: General roles and project roles define specific access rights.
- Flexibility: Adapt permissions to your team's needs.
Permission management in awork is based on two levels:
- General permission roles (workspace level): Apply to the entire awork workspace.
- Project roles (project level): Apply only to specific projects that a user is a member of.
Opening permission management
- Go to Einstellungen (the gear icon in the bottom-left corner of the main menu).
- Click Rechtemanagement.
Only users with the Admin role can configure these settings.
General permission roles
- Everyone in the workspace has a general permission role (e.g. Admin or User).
- Important: If a user isn't a project member, only the permissions of their general role apply.
Creating a general role
- In the Allgemeine Berechtigungsrollen section, click + Rolle.
- Enter a name and choose either a blank role or a template.
- Customize the individual permissions.
Preconfigured roles
- Admin: Full access and can manage workspace settings.
- User: Can work with projects but can't change central settings.
Setting menu visibility for each role
In the details of a permission role, you'll find the Menü-Sichtbarkeit tab, where you can choose which areas are visible in the menu.
Important: If the eye icon is disabled, the role doesn't have the required permissions.
Assigning general roles
At the bottom of the Rechtemanagement page, you'll find a list of all users, where you can assign a role to each person.
Note: You can't remove yourself from the Admin role.
Managing project roles
Project roles define specific permissions at the project level.
Important: Project roles can extend permissions, but they can't restrict them. Restrictions are always controlled through the general role.
Creating a project role
- In the Projektspezifische Berechtigungsrollen section, click + Rolle.
- Enter a name and set the viewing and editing permissions.
Optional: Mark the role as a Standardrolle so it's preselected when members are added to projects.
Editing or deleting a role
In the role overview, you can edit or delete roles using the action button.
Important: The system role Admin can't be edited or deleted. If you delete a role that's already assigned to users, you'll need to choose a replacement role.
Permissions in detail
Projekte
Projekt erstellen | Aktiv Users can create projects.
Users can't create projects.
|
Projektdetails | Verwalten
Lesen
Keine
|
Projektaufgaben | Verwalten
Lesen
Keine
|
Projektzeiten | Verwalten
Lesen
Keine
|
AI permissions
With a paid AI plan, you can configure in the general permission role who can use, share, and edit the awork Agent and specialized agents.
👉 Learn more: AI- und Agent-Berechtigungen
User
Only Admins can add new users.
User-Details | Verwalten
Lesen
Keine
|
User-Zeiten | Verwalten
Lesen
Keine
|
User-Planung | Verwalten
Lesen
Keine
|
Kunden
Kunden-Details | Verwalten
Lesen
Keine
|
Einstellungen
Projekteinstellungen |
|
Aufgabeneinstellungen |
|
Allgemeine Einstellungen |
Hinweis: Only Admins can delete the workspace. |
Tips and notes
-
Project roles only extend permissions. They can't remove permissions.
-
You can't remove yourself from the Admin role.
-
Project creators always retain full permissions for their projects.
-
Access to specific projects only: If users should only have access to selected projects, we recommend the following:
- Keep cross-project permissions (e.g. visibility of all projects, project tasks, or project time entries) restrictive in the general role.
- Then add the person as a project member and grant them the permissions they need for that project through the project role.
FAQ
Can users see only their own projects and tasks?
Yes. You can configure a general role so that users can only see projects they're members of.
Is there a setting that prevents users from tracking time altogether?
Yes. Admins can disable time tracking for the entire workspace under Einstellungen > Workspace. This is available starting with the Professional plan.
Who can delete projects?
Users who are allowed to manage project details (through their general role and/or a project role) can delete projects. In addition, users can always delete projects they've created themselves.
Do these permissions also apply to the API?
Yes, the permissions configured in permission management also apply to access through the awork API.
