RBAC on space and project level

RBAC, now at a space and project level

Until today, every member of your Salus organisation had access to every space and project in it. That made onboarding fast, but made the principle of least privilege impossible to apply. Starting in this release, access is scoped — you can grant a teammate the ability to deploy a single project without exposing the rest of your infrastructure.

What’s new

• Space-level roles — Owner, Admin, Developer, and Viewer per space, independent of organisation membership.
• Project-level roles — the same role set, scoped to individual projects within a space.

Why this matters

If you’re running production workloads alongside experimental projects, you no longer need to choose between speed and access hygiene. Contractors, ML researchers, and on-call rotations can be granted scoped access to exactly the projects they touch — without exposing the rest of your workloads.

How to use it

From the dashboard:

1. Open the space or project you want to scope access on.
2. Go to Settings → Members.
3. Choose Add member, pick a role, and Salus will email an invite.

Migration notes

Existing organisation-level roles continue to work — every current member retains the access they had before this release. There is no required action.

If you want to tighten access, open Project Settings → Members or Workspace Settings → Members and provide members with the exact role required per workspace or per project. Anyone removed from a space will lose access to every project in it.