Authentication and access

How to set Snyk roles and access at the Organization level using role-based access control

Set pre-defined user roles

Determine if Snyk pre-defined roles meet your requirements or if you must create custom roles. Snyk uses role-based access control (RBAC) to manage permissions across the Organization level.

Review Organization-level roles

Key decision: Determine if your team leads can operate with the fixed permissions of an Organization Admin or if they require a restricted custom role.

Pre-defined roles at these levels have fixed permissions that cannot be modified.

• Organization Admin: Allows users to add or delete Projects, override Snyk checks, and provision users. Assign this role to Team Leads.

• Organization Collaborator: Grants standard developer access. Use this for small teams or a developer-first rollout.

Align roles with your Organization structure

Key decision: Decide who is responsible for provisioning new users as your Snyk footprint grows.

Your choice of roles depends on how you structured your Snyk Organizations in the previous steps.

Structure	Typical role assignment
Team-based	Assign Organization Admin to the specific Team Lead for that Organization.
Product-based	Assign developers as Collaborators across multiple product Orgs.
SCM integration-based	Use custom roles and the Snyk API to automate role assignment during SCM import.

Setting up roles and permissions video guide