w6w docs

Console

The Console is the operator’s view across every tenant on the installation. It appears in the settings list under Console, with three pages: Tenants, Audit and System.

Who sees this: operators only. For everyone else the section is hidden, and opening one of its pages directly shows a “not available” notice.

Tenants

Tenants lists every tenant with its Slug, Domain, Status and Usage (last 30 days).

Create a tenant

  1. Click New tenant.
  2. Enter a Name. Optionally set the Slug, a Domain and a Tenant admin subject, the user who’ll administer it.
  3. Click Create tenant.
  4. Copy the Client id and Client secret shown. The secret isn’t shown again. The tenant’s backend uses them to exchange its own users’ sign-ins for W6W sessions.

How you know it worked: the tenant is listed as active.

Manage a tenant

  • Rename slug changes the tenant’s short name.
  • Disable turns the tenant off; Enable turns it back on.
  • A tenant’s Status shows its schema: shared schema, provisioning, schema ready or schema failed, plus detached for a disabled tenant whose schema is kept.
  • Retry schema appears when a tenant’s schema failed to set up. Click it, then check the badge once the list refreshes: a retry that fails again still shows schema failed.
  • Open a tenant whose schema is ready and click Export schema to download a dump of it. If the host refuses (for example its PostgreSQL client is too old, or a key rotation is running), the reason is shown and nothing is downloaded.
  • Open a tenant for three tabs:
    • Access: its backend credentials (Rotate client secret), the identity providers it accepts (Register IdP, with JWKS URI, Audience, Subject claim and Account claim), a Custom authorizer, and its OAuth clients. When you register an OAuth client, the form shows the app’s Callback URL once you have entered the app id and auth key; register that URL with the provider.
    • Apps policy: which apps the tenant can see. Switch between allowing everything and an allow list, Add an app, pin a version, and Block or Hide an app.
    • Usage: the tenant’s usage events, in total and for the last 30 days. This is an operator ledger, not billing.

Audit

Audit lists who did what: Time, Action, Actor, Target, Tenant, Outcome and Detail.

  1. Narrow it with Action, Actor kind, Actor id, Tenant, Outcome and a date range.
  2. Click Apply filters. Clear resets them.
  3. Click Export NDJSON to download the matching events.

System

System shows the server’s own CPU, memory and load, live.

Troubleshooting

SymptomCauseWhat to do
No Console sectionYou aren’t an operator.Sign in as an operator.
Resource monitoring is not available on this server.The server doesn’t expose resource figures.None.
No audit events match these filters.The filters exclude everything.Click Clear.

Where to next

  • Installation: the server’s licence and nodes.
  • Tenant: what a tenant admin manages themselves.