Set up tenant context before you operate anything.
This guide explains how to connect the console to the right tenant, what each field means, and how to confirm you are looking at live tenant data instead of a stale local session.
Who this is for
Operators, tenant admins, and implementation teams performing first-time setup or rotating tenant credentials.
When to use it
Use this before opening protected admin routes, after rotating a tenant token, or when the console looks disconnected from the API.
Required setup
Required inputs: API base URL, tenant ID, and tenant token. Recommended validation: check posture summary on /console/ after saving settings.
How to use
1. Open tenant settings
Start at /console/settings/ and review the connection panel before touching any operational page.
2. Enter connection values
Set API base URL, tenant ID, and tenant token. Use the tenant-scoped token only; do not reuse tokens across tenants.
3. Save and test
Run the connection test. A healthy response should confirm the API is reachable and the tenant is recognized.
4. Verify posture
Open /console/ and confirm posture summary, health signals, and timestamps reflect the tenant you just configured.
5. Persist tenant context
If you plan to use admin routes, keep the same tenant ID in context so protected links redirect correctly into the admin session flow.
What success looks like
Related console surfaces
/console/settings/ - connection configuration/console/ - posture and health confirmation