A customer is a client or a project inside your organisation — "Acme Corp", or "Internal platform". Every server belongs to exactly one customer, so a customer is the natural unit for writing policies and for deciding who can see what.

If you run one company's infrastructure, a handful of customers named after teams or products is enough. If you are a service provider, create one per client and use customer scope so an engineer assigned to one client never sees another client's hosts.

Customers are not tenants

The hard boundary in Shellius is the organisation, with its own users, CA, Keystore and policies. A customer is a grouping inside one organisation.

Required permissions

Permission	Lets you
customers.view	See customers and their server counts.
customers.create	Add customers.
customers.update	Rename a customer, edit its description, activate or deactivate it.
customers.delete	Permanently delete a customer.

Add a customer

1. Open Customers and select Add Customer.
2. Enter a Name.
3. Optionally set the Slug and a Description.
4. Save.

Field	Notes
Name	Required.
Slug	3–30 characters: lowercase letters, numbers and hyphens. Generated from the name if you leave it empty. Unique within the organisation.
Description	Optional.

The slug is how a customer is referred to in a bulk import, so pick something stable. It is set when the customer is created.

If your own access is limited to selected customers, a customer you create is added to your scope automatically. Otherwise it would vanish from your view the moment you saved it.

What the customer page shows

Opening a customer shows its details, a health summary for its servers (Healthy, Unhealthy, Unknown), a Security posture summary by severity, the number of active sessions, and its server list. From here you can Add server or Bootstrap host with the customer already selected.

Deactivate a customer

Edit the customer and turn Active off. An inactive customer stays in the list, marked inactive. Nothing is deleted.

Delete a customer

Deleting needs customers.delete, which only the Super admin role holds by default. The dialog first shows what depends on the customer, and makes you choose what happens to its servers:

• Reassign them to another customer you pick, or
• Delete the servers too, along with their sessions and access requests.

Shellius never picks for you. If a customer has servers and you have not chosen, the delete is refused.

Policies scoped to the customer are switched off

A policy limited to the deleted customer would otherwise lose that limit and start matching every server in the organisation. Unless you reassign those policies to another customer, Shellius deactivates them as part of the delete. Review them afterwards under Policies.

Next steps

ServersAdd the machines that belong to this customer.Access policiesWrite a policy that applies to one customer only.Groups and customer scopeLimit which customers a team can see.Bulk importCreate customers and their servers from a file.