Permissions, roles, and tokens in AI Security

To control the features users are allowed to access, AI Security provides a permissions functionality, integrated with user roles and authorization tokens.

Roles

A role is a collection of permissions. The actions you are allowed to do in AI Security depend on the permissions applied to your role.

We provide the following roles out of the box:

• Org owner: The creator of the AI Security instance.
  Only one user can have this role.
• Org admin: Has access to all AI Security features and functionalities.
• User: Basic user role.
  The User role has almost no permissions and is limited to basic tasks, for example, sending prompts.

In addition to the provided roles, you can also create and customize your own custom roles, choosing only the permissions relevant to your specific role requirements.

• Learn more about permissions

Tokens

To communicate with our API and access our API endpoints, you must use a token. A token is a unique identifier used for authenticating and authorizing requests, making sure the user or application has the necessary permissions for a specific action.

• Learn how to get an authorization token

Each token has one of three scopes:

• Personal: Belongs to you and is tied to your account.
  The permissions applied to a personal token correspond to the permissions set by your role.
• Organization: An organization-level token.
  Organization tokens have the highest permission level, as set by the org admin role, and give access to all AI Security features. Organization tokens are not linked to just one user.
• Project: Can access only the selected project.
  Project tokens have the project admin role permissions applied, allowing you to manage whole projects.

The scopes you can create and view depend on your role. Org admins can view every token in the organization.