Skip to main content

Roles

Create custom roles, define editing permissions in a structured way, and correctly assign them at user and project level.

Updated over 2 weeks ago

In the Roles tab, you define which editing areas and access rights a role has within the system.

Roles are configured system-wide but must also be created in the user dashboard and assigned at project level to become active.

Standard roles:

Company User

  • Can view all project content

  • No editing rights

  • No access to the dashboard or settings

Company Admin

  • Full access to the entire system

  • Can modify all settings and content

Step-by-Step Guide

Create a New Role

  1. Open the Roles tab.

  2. Click Add New Role.

  3. Enter a name for the new role.

  4. Choose a base configuration:

  • Include all permissions

  • Exclude all permissions

Important:

This selection defines the starting point of the role.

Any changes you make afterward override this initial selection.

Example:

If you choose “Include all permissions” and then deactivate a specific section, that section will be excluded — even though all permissions were initially included.

5. Configure the editing permissions.

Permissions are grouped into topic packages.
Within each package, you can:

  • Include all permissions

  • Exclude all permissions

  • Selectively include or exclude individual permissions

This allows you to configure the role precisely.

6. Click Save Role at the bottom of the page.


2. Create the Role in the User Dashboard

To make the role assignable to users:

  1. Open the Users tab.

  2. Create a role there with exactly the same name.

The naming must be identical to ensure correct assignment.


3. Assign the Role at Project Level

To activate the role within a project:

  1. Open the Project Settings.

  2. Select the Roles tab.

  3. You will see an overview of all available roles.

  4. Open the Assignment section.

  5. Assign the new role to the desired project.

  6. Assign the role configured in the Company Dashboard and confirm.

Wichtig:
Die Benennung muss exakt übereinstimmen, damit die Rolle korrekt zugeordnet wird.

System Dependencies

  • Roles define editing and access permissions system-wide.

  • The base configuration only defines the starting point.

  • Changes to a role affect all users assigned to that role.

  • A role only becomes active once assigned at project level.

  • Inconsistent naming prevents proper assignment.

Tips & Tricks

  • Use clear and precise role names.

  • Do not create more roles than necessary.

  • For restricted roles, start with “Exclude all permissions.”

  • Assign the Company Admin role only to users who require full system control.

  • After renaming a role, verify that project assignments still work correctly.

Did this answer your question?