Tenancy journeys
Table of Contents
The tenant is the boundary everything else lives inside: its accounts, its reference data and its results are invisible to every other tenant. This group holds the journeys that maintain the tenant's own details, that end its life, and that keep the reference lookups which classify accounts and tenants.
The lookups are the only place in these journeys where a plain list of reference rows is the right screen. They have no goal of their own, which is exactly why they belong here rather than in a journey about a person.
Creating a tenant is not here. Provisioning one is a setup journey, because it does work that takes time and can fail half way — see Setup journeys.
1. Journeys
| Journey | Actor | Gist |
|---|---|---|
| See the tenants | system administrator | The tenants the deployment holds: their code, name, hostname, type and status |
| See one tenant | system administrator | One tenant opened from the roster: its details, its setup run and its parties |
| Act inside a tenant | system administrator | Enter one tenant on purpose, read its data through the ordinary reads, and leave |
| Tune the tenant | tenant administrator | Maintain tenant details and the reference lookups |
| Retire or reset a tenant | system administrator | Suspend, terminate or reset a tenant, and clear what it leaves behind |