Back to changelog
v0.0.2Jul 18, 2026Improvement
v0.0.2 — Workspace Roles
Access to a project, scan or report is decided by current workspace membership and role, across four roles that build on each other.
Built around the team
A workspace is shared property, and this is the rule that decides who sees what inside it.
Access Follows Membership
Whether you can see a project, its scans, its reports and its background jobs is decided by one thing: whether you are a member of the workspace that owns it, and what your role is there. Roles run viewer → member → admin → owner, each adding to the one below it. Because access is evaluated against current membership on every request, removing someone from a workspace revokes all of their access to it immediately.
Features updated
Context & analysis
Want to shape what we build next?
Check out our roadmap and vote on upcoming features.
