States
The four states of a screen; the states of a capability, an install step, an invite and a tenant.
For: Platform administrator, Builder, Account administrator, Tenant administrator, Operator, Auditor, Member
The four states of a screen
| On screen | Meaning |
|---|---|
| You don't have access to this surface | You don't hold the key needed in this scope. |
| This capability is not open in this tenant | The thing exists; it has not been opened or published in this tenant yet. |
| Not applicable in this scope | This work doesn't exist in this scope. |
| A change is pending | A requested change has not completed yet. |
A capability's state in a tenant
| State | Meaning |
|---|---|
| Requested, not installed | The tenant requested the capability with Open; the install has not been started. |
| Installing | The install was left half-finished; a daily scheduled job resumes it. It has not failed. Because Install normally finishes the install right away, this state is short. |
| Installed | The install is finished: the transition pointer that makes the capability active in this tenant has been written and verified. |
| Install failed | A step failed; Install can be tried again. |
Install steps
The steps run in this order; each one waits for the previous one to finish.
| Step | What it does |
|---|---|
validate-config | Confirms that the version is still published and visible to this tenant. |
resolve-dependency | Confirms that the resolution lock is locked and that every required dependency is installed in this tenant. A version with no dependencies passes. |
prepare-runtime | “Skipped” today: no capability declares a runtime; the reason is written next to the step. |
apply-binding | “Skipped” today: no capability declares a binding; the reason is written next to the step. |
publish-capability | Writes the transition pointer that makes the capability active in this tenant; if there is a previous one, it replaces it. |
verify-activation | Reads the pointer and the resolution lock again, compares their fingerprints and writes the result as a verification record. |
A step's state can be “planned”, “queued”, “running”, “done”, “failed”, “skipped” or “rolled back”. Steps that never ran because of a failed step are shown as “did not run because a step failed”. Install runs the steps right away; when the screen returns, the steps of the last run are visible.
A capability version
| State | Meaning |
|---|---|
| Draft | Not visible to any tenant and not served. |
| Published | Visible on the tenants' Capabilities screen: the platform's in every tenant, an account's only in that account's tenants. |
In Account Studio, a version also shows “dependencies declared” or “no dependencies declared — can't be installed” next to it.
An invite
| State | Meaning |
|---|---|
| Pending | Sent, not accepted yet. It is valid for seven days. |
| Accepted | The person joined the tenant; the link can no longer be used. |
| Revoked | The tenant administrator withdrew the invite. |
| Expired | Seven days have passed; the invite can no longer be accepted. |
A tenant
On the Account Administration screen, a tenant can be active, suspended or closed. A suspended tenant can be reactivated; a closed tenant cannot be reopened.