Assign security roles
The Security Roles area is where you define roles at all three levels, and where you assign the server and repository ones. Item roles are the exception: you assign those on each item's Permissions tab.
Prerequisites
- Editing role definitions requires Manage Server Roles, Manage Repository Roles, or Manage Item Roles, depending on the tab.
- Assigning requires Assign Server Roles (server level) or the per-repository Assign Repository Roles permission.
Steps
Define or adjust a role
- Open Admin → Security Roles. The first three tabs — Server Roles, Repository Roles, Item Roles — hold the role definitions per level.
- Select a role to expand it, or click Add server role (or the tab's equivalent) for a new one. Each permission has a Grant and a Veto checkbox; leave both empty to stay neutral. The permissions reference explains the entries.

A role can't both grant and veto the same permission. Veto beats grant across roles — see how rights combine.
Assign server and repository roles
- Open the Server Role Assignments or Repository Role Assignments tab. Switch the View between Users / Groups and Roles to read the assignments from either direction.
- Click Assign Role to User / Group, then pick the user or group and the role — and for repository roles, the repository, or all repositories.
Prefer assigning to groups: membership then controls access — see Use groups to manage permissions.
Assign item roles
Assign item roles on the item itself: open the item's Permissions tab and use Assign Role to User / Group. The assignment inherits down the tree until something closer overrides it. Requires Administer on the item, or the repository's Set Any Item Permissions.
Verify
Check a user's combined result with the effective permissions view on an item — Show why names the role behind each grant. The Edit User page also lists each user's server and repository roles with the group that carries them.