If you manage infrastructure for more than one client — an agency, a consultancy, an MSP — the Customer level exists for you. Every server belongs to a customer, and access can be scoped by it.

Organization
  └── Customer      "Acme Corp", "Beta Inc"
       └── Server   tagged demo | dev | staging | prod

1. Create a customer per client

See Customers. Name them the way your team talks about them.

2. Bring servers in under the right customer

Add servers by hand, by bulk import, or from a cloud connector when a client has their own cloud account.

3. Scope people by customer

Use groups and access policies so that engineers on the Acme account see and request only Acme's servers.

4. Report per client

Filter the audit log by server or date range and export it — a ready answer when a client asks who touched their production systems last quarter.

Customers are not tenants

Customers divide one organisation's inventory. They share one certificate authority, one user directory and one audit log. If two clients must never share a CA, run a separate Shellius for each.

Next steps

CustomersCreate and manage them.GroupsScope what people can see.