Create, suspend and end a tenant from the tenant management console

Until now a tenant could only be found and read in the console — bringing one into existence happened elsewhere, and there was no way to pause or close one at all. The whole life of a tenant now happens here.

Creating one takes a name and an email address for its first administrator. The workspace and the invitation are made together, and nobody else can get in until someone with access invites them. Both audiences can create: the Sustentus team, and a partner provisioning a workspace for their own client. A partner’s new tenant is assigned to them as it is created, so it appears in their directory straight away.

Suspending closes a workspace to its people without removing anything. The tenant stays in the directory, badged as suspended, and its users are turned away from the platform with a page that tells them their workspace is unavailable and points them at whoever set the organisation up — it never says why, because that is a conversation between Sustentus and the account, not a notice on a screen. Reactivating is one click, and everything is where it was.

Ending a tenant is two steps, on purpose. Deleting it removes it from the directory and turns its people away, but destroys nothing: it moves to a Sustentus-only list of deleted tenants showing how many of its 30 days are left, and recovering it inside that window brings back its workspace, its people and all of its data exactly as they were. After 30 days it is still there — nothing is ever removed unattended — the list simply stops offering to recover it.

Permanent removal is the only irreversible step, and it asks you to type the tenant’s name before it will proceed. Afterwards the workspace, its people and every piece of its data are gone.

Suspending, deleting, recovering and permanently removing are the Sustentus team’s alone. Partners administer the tenants assigned to them; whether a client still has a workspace is not their decision.