Roles

Create, clone, and edit console roles' permissions using ready-made bundles or individual permissions.

The Roles screen is where you define console roles that determine who sees which screen and what actions they can perform in the console. A role is a set of permissions; when you assign a role to a user, they gain all permissions in that role. You prepare roles on this screen and assign them to users on the Users screen.

There are two types of roles:

• system role — These are built-in roles. When a new feature is added, these roles are updated as well. Their permissions are generally not editable; you clone them to customize.
• your role — Roles created in your workspace or cloned from a system role. You can edit their permissions, rename, and delete them. A cloned role remains as is even if the source system role is updated later; this prevents anyone's permissions from expanding without your knowledge.

Accessing the screen

Follow the menu path Settings & Access › Access › Roles. The screen is also accessible as a shortcut on the Settings & Access card in the product launcher. If you don't see it in the menu, your account lacks permission for this screen.

Screen sections

1. Title — Roles and the note "System roles cannot be changed; clone for a custom role."
2. New role card — fields for Role code, Role name, and the New role button.
3. Role list — all defined roles with appropriate buttons on each row.

When you open a role's permissions, you move to a separate role permissions page (explained below in the Role permissions page section).

List

There is no search or pagination in the list; all roles appear in a single list. Buttons on the right side of a row vary depending on whether the role is editable:

Whether a role is editable is determined by the system: your roles are editable, system roles are generally read-only. Clone appears only on non-editable roles; to copy one of your roles, you must create a new role and mark permissions separately. When the clone box is open on a row, the View permissions button on that row is hidden.

Actions

Creating a new role

Use this when you want to create a role from scratch that does not resemble any ready-made role. If you want a role similar to an existing one, Clone is faster.

1. Enter the short code for the role in the Role code field (example in field: DepoSorumlusu). The code appears as a role label in the user list and cannot be changed later.
2. Enter the readable name in the Role name field (example: "Warehouse Manager"). If left blank, the code is used as the role name.
3. Click the New role button. The button is inactive if Role code is empty.

A "Created." notification appears, fields clear, and the role is added to the list. Then define permissions using Edit permissions on the role's row. If creation is rejected, a red notification titled "Something went wrong" explains the reason and fields retain your input.

Cloning a role

Use this to adapt a system role to your needs. The clone starts with the source role's permissions and is editable as your role.

1. Click the Clone button on the non-editable role's row.
2. A New role code box opens in the row; enter the new role's code.
3. Click the Clone button next to the box. The button is inactive if the code is empty.

A "Role cloned." notification appears and the new role is added to the list. After the box opens, there is no close button; to cancel, leave the box empty. Clicking Clone on another row moves the box there.

Renaming a role

1. Click the Rename button on the role's row.
2. A small browser window opens with the current Role name; enter the new name and confirm.

A "Saved." notification appears. If you cancel or leave the name empty, no change occurs. The role code cannot be changed; only the name changes.

Deleting a role

1. Click the Delete role button on the role's row.
2. Confirm the "Delete this role?" prompt.

A "Deleted." notification appears and the role is removed from the list. Deletion cannot be undone. System roles can never be deleted; the button does not appear for them. If the system rejects deletion, a red error notification explains why.

Before deleting, check who holds the role in the Console roles column on the Users screen; users losing the role may no longer see screens associated with it.

Role permissions page

Opened via Edit permissions or View permissions on a role row. The title shows the role name, below it the role code and permission count. Top right contains:

• Role type badge (system role / your role).
• Orange "N pending changes" badge if unsaved changes exist.
• Save — visible only if the role is editable; inactive if no pending changes.
• Cancel (for editable roles) or Back to overview (for read-only roles) — both return you to the Roles list. Cancel discards unsaved changes without confirmation.

If the role is read-only, a note appears under the title: "System role: permissions cannot be changed. Clone for a custom role." and checkboxes are disabled. If you have permission to edit a system role, an orange warning appears instead: "System role: this change affects users in all workspaces." Be cautious when making changes.

Filtering and searching

Ready-made bundles

"A sequence of permissions needed to perform a task." Bundles allow marking all permissions needed for a task at once. The table shows 10 bundles per page.

If the role is editable, each row has buttons:

• Add — marks missing permissions from the bundle.
• Remove — visible if all bundle permissions are already marked; removes all bundle permissions.

Adding a bundle only marks permissions individually; roles store permissions, not bundles. If the bundle content changes later, your role does not change. The same permission can appear in multiple bundles; removing one bundle removes permissions even if used by others, so check other bundles' Status after removal.

Permissions

The table shows 25 permissions per page.

Editing role permissions

1. Click Edit permissions on the role row.
2. Use search, module, and Picked / Not selected filters to find relevant permissions.
3. To grant all permissions for a task, click Add in the Ready-made bundles table; for individual permissions, check or uncheck the Granted box in the Permissions table.
4. Track changes with the "N pending changes" badge at top right. Navigating pages and filters does not clear marks.
5. Click Save.

A "Saved." notification appears and you return to the Roles list. If saving is rejected, you remain on the page and pending changes are preserved. Only changed permissions are sent; permissions added by another admin simultaneously are not removed. Changes apply to all users with this role, affecting their menus and permissions.

You cannot add a permission you do not have to a role; if you mark such a permission, saving is rejected with a red error notification explaining why. Remove that permission and save again.

Common situations

• I cannot change permissions of a system role. System roles are read-only; checkboxes are disabled. Clone the role and edit the clone's permissions, then assign the clone to users.
• I get an error when saving. The most common cause is trying to add a permission you do not have. Check the error message, remove the relevant permission, and save again.
• "No matching permission" appears. The search text or module selection matches no permissions. Change the search or module filter; if Picked filter is active, switch to All.
• "No ready-made bundles for this module" appears. No bundles are defined for the selected module. Mark permissions individually in the Permissions table.
• Role permissions page says "Page not found." The role was deleted or the link is broken. Return to the Roles list and open the role from there.
• I changed permissions but the user still sees the old menu. Make sure you clicked Save. You can preview the user's view on the Users screen using Preview.
• Marked permissions disappeared. Pending changes are kept only while the page is open. Clicking Cancel or navigating away discards unsaved changes without warning. If the "N pending changes" badge is visible, click Save before leaving.

Related screens

• Users
• API clients
• Using list screens