Skip to content

Roles & Data Groups

Settings

Control who can see and do what in your organization with custom roles and data groups.

Roles

Settings → Roles & Data Groups lets you create custom roles beyond the default Organization Admin and Auditor roles.

Why custom roles?

Not everyone needs full admin access. Custom roles let you grant module-specific permissions:

Permission example Who might need it
View findings only Junior security analyst
Manage integrations DevOps lead
View compliance only External auditor
Manage members HR / IT admin

Creating a role

  1. Go to Settings → Roles & Data Groups
  2. Click Create Role
  3. Name the role and select module permissions (view, create, edit, delete per module)
  4. Assign the role to members

Data Groups

Data groups provide repository-scoped access control — limiting which integrations, repositories, or assets a user can see.

Why data groups?

In large organizations, not every team member should see every repository or cloud account. Data groups restrict visibility to assigned resources.

Example Data group scope
Frontend team GitHub repos: frontend-* only
Cloud team AWS accounts: production only
Auditor All repos, read-only

Creating a data group

  1. Go to Settings → Roles & Data Groups → Data Groups
  2. Create a data group with a name and description
  3. Assign repositories, cloud accounts, or other resources
  4. Link the data group to a role or member