Roles & permissions
Grant global roles, individual permissions, and presets in a controlled way
Artwork combines global roles with individual permissions. This lets you provide broad responsibility or restrict access to specific areas and actions.
Global roles
Global roles define a fundamental position across the whole system. The administrator role has extensive access and should be granted only to a small number of explicitly responsible people. Other roles may also provide predefined capabilities depending on your setup.
A global role acts organisation-wide. Do not confuse it with a project role, which describes a function in one project only.
Individual permissions
User permissions groups rights by subject. Each permission describes a specific capability, such as viewing an area, creating or editing content, deleting records, or managing settings.
Groups can be expanded and collapsed. Select all and Deselect all change a complete group. Changes are saved on the profile.
A visible menu does not mean every action is allowed
One permission may allow entry to an area while another is required to edit or delete. Project access, team membership, and individual responsibility can also apply in addition.
Permission presets
Presets are reusable packages of individual permissions, for example for production management, scheduling, or inventory maintenance. In the Permission presets tab, administrators can:
- search presets,
- create a named preset with selected permissions,
- edit an existing preset,
- delete an obsolete preset after confirmation.
Presets can be applied quickly when inviting users. A preset is not a separate account status; it helps set the contained permissions. After changing a preset, check whether existing accounts also need adjustment.
Recommended permission process
Common reasons for missing access
If someone cannot see or perform a function, check:
- Is the required global permission active?
- Does the role allow the action, or does the area impose another limit?
- Is the person assigned to the project, team, craft, or funding source?
- Do they have read access only, or write/delete access as well?
- Is the system-wide function enabled in Tool Settings?
Remove access
Do not immediately delete the entire account. Removing a role, individual permission, team membership, or project-specific access is often enough. For sensitive roles, record internally who requested the change and who took over the responsibility.