Organizations & Teams

Your organization is your top-level account on Salus. It holds your members and their roles, your connected Git providers, your billing and credits, and your managed databases. Everything else — workspaces, projects, and environments — lives inside it.

Create an organization

Create an organization and give it a name (letters and numbers only). Once it exists, you can invite your team, connect a Git provider, and start creating projects.

Members and roles

Every person in your organization is a member with a role that determines what they can do. There are four roles you can assign, from full control to read-only:

• Owner — full control, including members and billing.
• Maintainer — manage workspaces, projects, and configuration.
• Developer — work day to day on projects and deployments.
• Viewer — read-only access.

You may also see a fifth, Guest. You don’t assign it: Salus adds it automatically when someone accepts an invitation to a single workspace or project, so they hold a place in the organization without any organization-wide access.

Roles are scoped — a member can have one level of access across the organization and a different level in a specific workspace or project. For the full picture of what roles govern, see Access Control.

Invite your team

Invite someone by email from your organization settings and assign the role they should have. An invitation moves through a clear set of states — pending until they accept, then accepted, or expired if it lapses (you can also see rejected invites). If the person isn’t a Salus user yet, they’ll be prompted to create an account when they accept.

Connect your Git providers

Your organization is where you connect the Git providers your projects import from — GitHub, GitLab, and Azure DevOps. See Git Management.

Billing and credits

Your plan, credit balance, payments, and usage are all managed at the organization level. See the Billing Dashboard and Salus Credits.