Access Control
Access control on Salus covers two separate questions: who on the internet can reach your running application, and who in your organization can act on your resources.
Deployment exposure
Each deployment is either public or private, set by the public network toggle on its release configuration:
- Public — the service is reachable from the internet on a public URL. Use this for anything users or external systems need to call.
- Private — the service is only reachable internally, within its workspace. Nothing on the public internet can connect to it.
Leave a deployment private unless it genuinely needs to be exposed. See Deployments for the domains a public deployment is served on.
Database network access
Managed databases have their own network controls, separate from your app’s exposure — a public-access toggle, a CIDR allow-list, and an allowed-IP list. See Databases.
Team roles
Access to your organization’s resources is governed by roles. Each member holds a role, and roles range from full control to read-only:
| Role | Typical access |
|---|---|
| Owner | Full control of the organization, including members and billing. |
| Maintainer | Manage workspaces, projects, and configuration. |
| Developer | Work day to day on projects and deployments. |
| Viewer | Read-only access. |
A fifth role, Guest, is assigned automatically rather than chosen — see Organizations & Teams.
Permissions are scoped to the level they apply at — organization, workspace, or project — so a member can be given broad access in one workspace and none in another. Managing members and their roles is covered under Organizations & Teams.