Organization-scoped access in Evo
Evo data access is now limited to the Snyk Organizations a user can read, leveraging existing Organization hierarchy without requiring migration. Tenant Viewer now grants scoped read access, Tenant Member no longer grants Evo access, and Organization names appear alongside repositories to distinguish duplicates across Organizations.
Starting August 18, 2026, a user's Evo data is limited to the Snyk Organizations they can read.
Until now, everyone with access to Evo saw every repository, asset, and issue in the Tenant. Evo now reuses your existing Snyk Organization hierarchy, so there is nothing new to model and no migration to run. Nobody loses access until an administrator changes their role.
What's new:
Tenant Viewer now grants read access to the assets and issues in the Organizations the user belongs to, and to nothing outside them
Tenant Member grants no Evo access, letting administrators withhold Evo without removing Snyk platform access
Full-Tenant access continues for Tenant Admin and for the two roles ending in "with Evo access"
Organization names appear alongside repositories, distinguishing the same repository imported into more than one Organization
Note for administrators:
Existing users keep their access, and Tenant Viewers gain scoped read access for the first time. New users join as Tenant Member, which carries no Evo access, so each one needs a role change. Scoped users are read only, and assets without an Organization stay hidden, which today means all Agent Supply Chain Security and Continuous Offensive Security data.
Documentation: Access and authentication
Source: original entry ↗
More from Snyk
Follow Snyk to get its new changes in your feed and email digest.
Snyk CLI v1.1308.1 released
HTML report output is now available by default without preview features, and project names are consistently displayed in test summaries. This release also patches multiple security vulnerabilities.
Pending ignore requests now visible on Project's Issues page
Issues with pending ignore requests now display a clear "Pending Ignore Request" status on the Issues page and in issue details, with filtering support. The issues API now reports pending as part of an issue's ignore status for programmatic distinction of open, pending, and ignored findings.
Snyk Code October update: improved analysis and more findings
Snyk Code now analyzes projects more deeply and accurately across Java, Kotlin, Go, TypeScript, JavaScript, Python, C#, PHP and Ruby, with significantly more findings reported. Improvements include better import resolution via config files, corrected PHP typing, expanded library coverage, new vulnerability detection rules, and enhanced template and serverless application analysis.