Multi-tenant surface. Relevant when one Relayer box serves multiple isolated
workspaces (tenants); a single-operator install can ignore it.
Purpose
Create and manage tenants on this box. Each tenant gets its own isolated workspace.
Controls
- Create Tenant — opens a modal with a single Tenant Name field (e.g. “Acme
Corp”; at least two characters). Confirm with Create. - Refresh — re-query the tenant list.
- Tenants card with a live count. Empty state reads “No tenants yet.” with the
hint “Create your first tenant to get started.”
Once tenants exist, the card becomes a table with four columns:
- Name — the tenant’s display name (falls back to its alias, then a dash).
- Cost Center — the internal identifier every tenant action is keyed on.
- Status — a pill reading Active, Suspended, or Unknown.
- Actions — four per-row icon buttons:
- Suspend / Reactivate — toggles the tenant between active and suspended. The
icon and tooltip flip to match the current state; it is disabled for a tenant
whose status is neither active nor suspended. - Set Quota — opens a modal with a Quota Ceiling in decimal GB (sent to the
gateway as bytes) and an Object Count Limit. A note explains that usage
figures read zero until data accounting is live. - Rate Limit — opens a modal with a Requests Per Minute field. A warning
states the value is persisted but only takes effect on gateway restart until a
future update. - Restore — opens a modal showing Cost Center, Restore With Cost Center, and
Default Contract Years. The whole form is currently disabled; restore is not yet
available and will be enabled in a future platform update.
- Suspend / Reactivate — toggles the tenant between active and suspended. The
Gotchas
- Set Quota, Rate Limit, and Restore only appear once at least one tenant exists —
they are per-row actions, not page-level buttons. - Restore is a placeholder: its fields and Restore button are disabled by design.
- The session badge (top-right) shows which workspace your current session belongs
to. - Deeper tenant workflows (delegating bucket access, self-service keys/usage/audit) happen in the Tenant Portal, not this operator console — see the Tenant Portal section below.
Tenant Portal (self-service)
Separate from this operator console: tenants sign in through their own portal at /tenant/signin to manage their own workspace directly.
| Page | Route | What it covers |
|---|---|---|
| Sign In | /tenant/signin | Tenant email/password sign-in. This is the link to give testers/tenants directly — not the operator console. |
| Activate Account | /tenant/activate | First-time account activation via an activation code. |
| Dashboard | /tenant | Scoped landing console: quota, usage, and profile summary. |
| Keys | /tenant/keys | Self-service access-key management. |
| Usage | /tenant/usage | Tenant-scoped usage visibility. |
| Audit | /tenant/audit | Tenant-scoped audit log. |
| Connect | /tenant/connect | Connection instructions for the tenant’s own S3 endpoint/credentials. |
| Help | /tenant/help | Tenant-facing help page. |
Page-by-page coverage (controls, gotchas, screenshots) for each of these is tracked as a follow-up — this table exists so the portal’s entry point and routes aren’t undocumented in the meantime.
Screenshots
2023 SCP Corp