A secure Snyk deployment rests on a clear Group and Organisation structure, a small set of tightly scoped service accounts, source code integrations that do not depend on one person's token, and policies that decide how findings are prioritised and ignored. Snyk connects to your repositories, CI pipelines and registries, so the tokens and integrations it uses are non-human identities with read access to much of your source code and, in some cases, the right to open pull requests. This guide walks through how to set up the Snyk hierarchy, roles, service accounts, SCM integrations, Snyk Broker and policies so that the platform improves your security without becoming a weak point itself.
It is aimed at application security engineers and platform teams who administer Snyk, and at identity teams who need to account for the tokens Snyk holds. Several features covered here, including service accounts, Snyk Broker and policies, are available only on Snyk Enterprise plans according to Snyk's documentation.
This is an independent guide from NHI Mgmt Group, based on Snyk's public documentation as of November 2026. It is not sponsored or reviewed by Snyk. Product features change, so confirm settings against Snyk's current documentation.
Key takeaways
- Snyk's hierarchy runs Tenant, Group, Organisation, Target and Project. Organisations are where most access control, integrations and service accounts live, so design them around teams and trust boundaries.
- Group Admins are automatically Organisation Admins in every Organisation in the Group. Keep that role to a few named people.
- Use service accounts, not personal tokens, for CI/CD and integrations. Snyk shows a service account token only once, and deleting the account revokes the token immediately.
- Pick the narrowest service account scope that works: an Organisation-level account for one team's pipeline, a Group Viewer account for read-only reporting.
- The GitHub Cloud App links access to the app rather than to a user account, supports repository-level access, and opens fix pull requests directly instead of through a service account.
- Snyk Broker keeps SCM tokens inside your network and connects outbound only, with access limited to an approved data list.
- Only Organisation Admins can approve or reject ignores. Use that to separate the people who suppress findings from the people who sign off on them.
Why Snyk's tokens are non-human identities worth governing
Snyk works by reading code and manifests from your source control system, scanning them, and in many setups opening pull requests to fix dependencies. To do that it holds credentials: SCM tokens or app installations on the source control side, and Snyk API tokens on the pipeline side. Each one is a non-human identity. Each one can be stolen and reused, and each one tends to outlive the person who created it.
The risk shows up in two directions. A Snyk API token with broad Group scope lets whoever holds it read findings, change projects or alter integrations across many teams. An SCM token held by Snyk or by a Broker client gives read access to private repositories. The CI/CD Pipeline Identity Security Guide covers the wider pattern of pipeline credentials; this guide focuses on the settings Snyk gives you to keep these identities narrow.
Designing the Group and Organisation structure
Snyk's documentation describes an Enterprise hierarchy with these levels:
- Tenant: one per company, spanning Groups, Organisations, Targets, Projects and related features such as Tags and Collections.
- Group: covers your Snyk user base. Every customer has at least one, and large companies may have several, each with multiple Organisations.
- Organisation: represents an area of the business, such as a team, and contains Projects.
- Target: the external resource Snyk scans, such as a repository. One Target can relate to several Projects.
- Project: created from the item Snyk scans, such as a manifest file, with its own results and settings.
Because integrations, Organisation service accounts and most roles are set per Organisation, the Organisation boundary is your main access control boundary. NHI Mgmt Group recommends:
- Create Organisations around teams or products that own their own repositories, rather than one large Organisation for everyone. That keeps each team's tokens and integrations separate.
- Use separate Groups only where business units are genuinely independent, for example after an acquisition, since Group Admins have power over every Organisation in their Group.
- Name Organisations consistently so that reporting, audit log queries and automation can find them reliably.
- Use Project attributes and tags from the start. Snyk policies can be assigned through Project attributes, so consistent tagging makes policy assignment practical.
Snyk's documentation also notes that audit logs of user-initiated activity can be retrieved by Organisation or Group through the Snyk REST API, and that session length can be configured for a Group. Both are worth setting up on day one.
Roles and least privilege
Snyk ships predefined roles at Group and Organisation level. According to Snyk's documentation:
| Role | Level | What it means in practice |
|---|---|---|
| Group Admin | Group | Full permissions at Group and Organisation level, and automatically an Organisation Admin for every Organisation in the Group. |
| Group Viewer | Group | Needs Organisation-level permissions to take actions; typically a starting point during onboarding. |
| Group Member | Group | Described as a non-functional role; at Group level it can view Groups, Organisations, Tags and users. |
| Organisation Admin | Organisation | The team lead role: can add and delete Projects, override Snyk checks and provision Group members. |
| Organisation Collaborator | Organisation | The developer role. |
The permission tables show some splits that matter for non-human identity governance. Editing integrations is limited to Organisation Admin and Group Admin. Creating, editing and removing Organisation service accounts is limited to the same two roles, and Group-level service account permissions belong to Group Admin only. Predefined roles cannot be customised, so Snyk recommends creating custom roles where you need a different set of permissions.
Recommended practice
- Give most developers Organisation Collaborator in their own team's Organisation.
- Limit Organisation Admin to team leads who own integrations and service accounts for that team.
- Keep Group Admin to a small platform or security group, and review its membership regularly.
- Build custom roles for specialist needs, such as a reporting role that can view but not edit integrations.
Service accounts for automation
Snyk's documentation states that service accounts are available only for Enterprise plans; Free, Team and Trial users rely on a personal user token instead. For anyone on an Enterprise plan, service accounts should replace personal tokens in every pipeline and integration. Snyk lists automation, CI/CD and integrations such as GitHub Enterprise as their intended use, and advises against using a service account token to authenticate with an IDE.
Scope
There are two scopes. A Group-level service account token can call Group and Organisation API endpoints and run the CLI for all Organisations in the Group. An Organisation-level token manages integrations for a single Organisation, and Group Admins can also see and manage it from the Group level.
Group service accounts can take Group Viewer, Group Admin or Group Member, and Snyk recommends Viewer or Admin. Organisation service accounts can take Organisation Admin, Organisation Collaborator or a custom role. Snyk notes that you cannot create a service account with a higher privilege role than your own.
Who can create them
A Group service account needs a Group Admin to create it. An Organisation service account needs a Group member who is also an Organisation Admin, or a Group Admin. Snyk states that Group Viewers cannot create service accounts, whatever their Organisation role.
Token handling
Snyk generates a service account token only once: copy it immediately, because you will not see it again. Deleting a service account invalidates its token immediately, and Snyk treats deleting as the same as revoking. You cannot regenerate the same token, so replacing a token means creating a new service account. Names are unique within an Organisation or Group and cannot be reused.
Recommended practice
- One service account per pipeline or integration, so each can be revoked without breaking others.
- Prefer Organisation-level accounts. Use a Group-level account only for jobs that truly span Organisations, and use Group Viewer when the job only reads.
- Put the token straight into a secrets manager or the CI platform's secret store when it is shown, and never into source code.
- Rotate by creating a replacement account, switching consumers to it, then deleting the old account. Because names cannot be reused, include a date or sequence in each name.
- Keep an inventory: account name, scope, role, owner, consumer, creation date.
- Use the audit log API to watch for service account creation and deletion.
For general API token lifecycle practice, see the API Key Management Guide.
SCM integrations and the GitHub Cloud App
Snyk's source control integrations are configured at Organisation level, and only Organisation Admins and Group Admins can edit them. For GitHub, Snyk offers the GitHub Cloud App. Snyk's documentation says it decouples access control from user accounts by linking it to the app, and lists role-based access control, granular repository-level access and a higher rate limit as its advantages.
Two further points from the documentation matter for identity governance. First, the app performs Snyk-initiated pull requests directly rather than going through a service account. Second, when you install it you choose whether it covers all repositories or only some. The GitHub Apps vs Personal Access Tokens vs OAuth Apps guide explains why app-based access is generally easier to govern than a token tied to one person.
Setup notes
- Setup needs both a Snyk Organisation Admin and a GitHub Organisation Admin.
- A GitHub organisation can connect to one Snyk Organisation or to several, but Snyk notes it cannot do both at once.
- Snyk warns that the app loses access if it is uninstalled from the GitHub organisation, and that editing the app's accessible repositories has the same effect. Put app installation changes under change control.
- The app has no preconfigured IP addresses; Snyk says to contact your account team for them. On GitHub Enterprise Cloud they must be added at both Organisation and Enterprise level if you use IP allow lists.
- Enterprise customers can move existing Targets to the app with the
snyk-migrate-to-github-apptool.
Recommended practice
- Install the app only on the repositories each Snyk Organisation needs, rather than all repositories by default.
- Where an older integration uses a personal token, plan a migration and then revoke the old token at the source control side.
- Record who installed each app instance and which Snyk Organisation it serves.
Snyk Broker for private networks
Snyk describes Snyk Broker as an open-source tool that acts as a proxy between Snyk and source integrations, so that Snyk can scan private resources while credentials stay inside your network. It is available only on Enterprise plans.
The Broker Server runs on Snyk's backend. The Broker Client runs in your infrastructure and, in Snyk's words, keeps sensitive data such as SCM tokens within the network perimeter. Snyk states that there is no need to open incoming ports, because communication is initiated outbound, after which the WebSocket connection is bidirectional. Access is limited to requests on an approved data list, and credentials are stored locally with the client for both Classic and Universal Broker.
Snyk says its aim is for Universal Broker to replace Classic Broker entirely. Universal Broker supports multiple connection types, configuration tooling (snyk-broker-config) or an API, and Organisation-to-connection mapping, and adds support for the GitHub Cloud app and GitHub Server app.
Recommended practice
- Treat the Broker Client host as a secrets holder: harden it, restrict who can log in, and monitor it.
- Give the SCM token used by the Broker the narrowest repository access and permissions your SCM allows.
- Keep the approved data list as tight as possible and review any change to it.
- Rotate the SCM token held by the Broker on a schedule, and know which Snyk Organisations each connection serves.
Policies, ignores and the .snyk file
Snyk policies define how Snyk behaves for specific types of Open Source issues: you set a condition, such as no exploit available, and an action, such as changing the severity. Snyk states that policies are available only on Enterprise plans and apply only to Snyk Open Source scans. There are two categories: security policies, covering how vulnerabilities are treated, and license policies, covering which licence types are allowed. Policies are managed in the Snyk Policy Manager and can be assigned to Organisations in a Group, or to Projects through Project attributes.
Separately, the .snyk file in a repository defines analysis behaviour for Open Source, Snyk Code and Snyk IaC, and specifies patches for the CLI and CI/CD plugins. Because it lives in the repository, anyone who can merge to the repository can change it.
Ignores are where risk acceptance happens. According to Snyk's role tables, Organisation Admins, Organisation Collaborators and Group Admins can create, edit and remove ignores, while approving or rejecting ignores is listed for Organisation Admin only.
Recommended practice
- Set security and licence policies centrally and assign them to Organisations, so teams start from the same baseline.
- Require a reason and an expiry for every ignore, and use the approval step so that an Organisation Admin signs off.
- Protect
.snykfiles with code owner review so that changes to analysis behaviour are seen by the security team. - Report regularly on open ignores and expire those whose reason no longer applies.
Monitoring and audit
Snyk's audit logs of user-initiated activity are available by Organisation or Group through the REST API. NHI Mgmt Group recommends pulling them into your central logging platform and alerting on:
- Creation or deletion of service accounts, especially at Group level.
- Changes to integrations, Broker connections and GitHub app installations.
- Role changes that add Group Admin or Organisation Admin rights.
- Bulk ignore activity and policy edits.
On the source control side, monitor the Snyk app and any Broker token for activity outside normal scanning patterns. The Software Supply Chain Security Guide covers how scanning fits the wider supply chain control set.
Common failure patterns
- Personal tokens in pipelines. A developer's token runs CI scans and stops working, or keeps working, after they leave.
- One giant Organisation. Every team shares integrations and admins, so any admin can change any team's setup.
- Group Admin sprawl. Many people hold a role that is admin everywhere.
- Group Admin service accounts by default. A read-only reporting job runs with full Group rights.
- App installed on all repositories. The GitHub app can see repositories no Snyk Organisation needs.
- Unreviewed ignores. Findings are ignored without approval or expiry, and dashboards look cleaner than reality.
- Unprotected .snyk files. Analysis behaviour changes in a routine merge without security review.
Practitioner checklist
- Map Organisations to teams and products, and tag Projects consistently.
- Keep Group Admin small and use Organisation Collaborator for most developers.
- Replace every personal token in CI and integrations with a dedicated service account.
- Use Organisation-level service accounts by default and Group Viewer for read-only jobs.
- Store tokens in a secrets manager, rotate by replacement, and keep an inventory.
- Use the GitHub Cloud App with repository-level selection where GitHub is your SCM.
- Use Snyk Broker for private SCMs and harden the client host.
- Assign central policies, require ignore approval and expiry, and protect
.snykfiles. - Stream audit logs to central logging with alerts on service account, integration and role changes.
Standards and references
- Snyk: Service accounts
- Snyk: Groups and Organizations
- Snyk: Pre-defined roles
- Snyk: GitHub Cloud App
- Snyk: Snyk Broker
- Snyk: Policies
- NIST: SP 800-218 Secure Software Development Framework (SSDF) Version 1.1
- NIST: SP 800-53 Rev. 5 (IA-5 Authenticator Management, AC-6 Least Privilege, SA-11 Developer Testing and Evaluation)
Related NHI Mgmt Group resources: CI/CD Pipeline Identity Security Guide · GitHub Apps vs Personal Access Tokens vs OAuth Apps · Software Supply Chain Security Guide · API Key Management Guide