Finding your way
Finding your way
The environment console (/admin on your environment's host) is grouped by task, in the
words other identity platforms use.
Which console am I in? Every page says, in one line above it: Environment:
Production · Environment on acme.cboxid.com, Workspace: Acme, or Platform admin. On the
root host (cboxid.com) the console without /admin is your workspace: projects,
team, keys, billing, settings and your team's own sign-in to Cbox ID. How people sign in to
your apps is set in an environment's console. Opening Social login, Branding or Sign-in
methods on the root host shows a link to that page in each of your environments. Platform
operators also have the platform's own environment at cboxid.com/admin, the same
console for the environment everybody signs in to Cbox ID with, and platform admin is
its first area, Platform
(Administering the platform's own environment). If you have used WorkOS, Clerk or Auth0, most things
are where you would look first. This page shows the map, then walks the common tasks
click by click.
Three ways to get anywhere:
- The rail on the left: one icon per area. Clicking an area opens its first page, and its other pages are listed beside it.
- ⌘K (Ctrl+K on Windows and Linux): type a page's name, or the word you would use for it elsewhere. SAML, OIDC, SCIM, HR system, Google login, tenant, RBAC, passkeys, MCP and logo all find the right page. It also finds a user by email, an organization or app by name, and any record by a pasted id. To open another environment, type its name and choose Open ….
- Breadcrumbs on every detail page, such as Authentication / Enterprise SSO above a connection. They lead back to the list the page belongs to.
The map
| Area | Pages | What it is for |
|---|---|---|
| Home | Overview, Get started | What is set up, and the next step |
| Users & orgs | Users, Organizations | The people who sign in, and the customer organizations they belong to |
| Authentication | Sign-in methods, Authentication policy, Social login, Enterprise SSO, Domains, Directory Sync, Radar | How people get in |
| Authorization | Roles, Permissions, Fine-grained authorization, Access reviews, Role conflicts | What people may do once they are in |
| Developers | Applications, APIs, API keys, Webhooks, Hooks, Feature flags, Pipes | What your code talks to |
| AI agents | Agents, Approvals, Connect | Software that acts on this environment, and the MCP server |
| Branding | Branding | How the hosted sign-in page looks, the logo and favicon, and the name your mail is sent under |
| Monitoring | Audit log, App audit logs, Log streams, Usage | What happened |
| Advanced | Admins & support, Token vault, Outbound provisioning, SAML apps, Legacy login | Set up once and rarely revisited |
| Settings | Settings | The environment's id, issuer and discovery URL |
On the root host, platform operators have one more area, first on the rail:
| Area | Pages | What it is for |
|---|---|---|
| Platform | Workspaces, Environments, Organization tree, Operators, Usage, Queues, Search | The whole deployment: every workspace and environment, the operators, and support sessions. Every page says Platform admin: the whole deployment above it. |
Modules add pages to these areas when they are switched on. Examples are Sign-in activity, Risk events and Trusted devices.
Connectors, between Developers and AI agents, is the one place to see and start every integration. Each integration still lives on its own page in the areas above; Connectors leads to it:
- Catalog has a card for every kind: Enterprise SSO, Social login, Directory Sync, HR systems, outbound SCIM provisioning, SAML apps, webhooks, hooks, log streams and Pipes. Each card shows how many are live and how many are failing. Set up opens that kind's setup form, Manage opens its list, and Guide opens the guide. A provider on a card, such as Workday or Datadog, opens the setup form with that provider already chosen.
- Connections lists every live connection of every kind. Each row shows its type, organization, status and last activity, and links to the connection's own page. Failing connections are listed first. Narrow the list by status, type or organization. New connection opens the catalog.
One organization's page
Open an organization from Users & orgs › Organizations. Its page has the Admin Portal link button in the header and nine tabs:
Overview · Members · SSO · Directory Sync · Domains · Roles · Authentication policy · Audit log · Settings
Some tabs hold more than one page. Those pages appear as a second, smaller row:
- Members: Members, Invitations.
- Audit log: Audit log, App audit logs.
- Settings: General, Branding, API keys, Support access.
Enterprise SSO, Domains, Directory Sync, Roles and the Audit log each appear in two places:
- On the organization's tab, showing only that organization's rows.
- In the rail, showing every organization's rows, with an Organization filter.
What changed
The console used to file these pages differently. Every URL still works, so bookmarks and links in older notes keep working.
| Before | Now |
|---|---|
| Users & orgs held Roles, Permissions and Fine-grained authorization | They are in a new Authorization area, beside Authentication |
| Access reviews and Role conflicts were under Advanced | They are under Authorization, beside the roles they govern |
| Password rules, two-factor, SMS, social and SSO were on separate pages, and passkeys, magic links and sessions were on none | Authentication › Sign-in methods shows every way in, whether it is on, and where it is changed |
| Social login was set up per organization, so turning on Google meant doing it for each one | A provider is set up once for the environment and every organization inherits it; an organization can still use its own |
| Passkeys, magic links and session lifetime were decided by the deployment only | They are on Authentication policy, for the environment, within the deployment's limits |
| An organization's domains were only on its own page | Authentication › Domains lists every organization's domains as well |
| An organization had 14 tabs in one row, and the last ones were cut off on a laptop | 9 tabs, with related pages grouped under one tab |
| Detail pages had a bare "‹ Back" link | A breadcrumb shows the area and the list |
| ⌘K matched only page names, so "SAML" found SAML apps (the outbound direction) and "SCIM" found nothing | ⌘K also matches the words people use elsewhere |
Platform admin was a separate console at /platform, with its own rail and an amber strip |
It is the Platform area of cboxid.com/admin; every /platform address redirects there |
Task by task
The clicks below start from the environment's home page. tests/Feature/Crawl/FindingYourWayTest.php
checks that each task stays within these limits.
Turn on Google or GitHub login
- Authentication › Social login.
- Google (or GitHub) under Add a provider. Who is it for? is already The whole environment.
- Copy the redirect URI it shows into your own Google or GitHub OAuth app, paste the client ID and secret back, and press Turn on Google for everyone.
That is three clicks from the environment's home page. Every organization's sign-in page now offers it. To give one organization its own credentials instead, choose it under Who is it for?; to take the button off one organization's page, open Social login filtered to that organization and use Turn off here. Social login.
Set up enterprise SSO for a customer, verify their domain, and hand over the setup
- Users & orgs › Organizations, then open the organization, for example Acme Corp.
- SSO tab, then New connection. Choose SAML 2.0 or OpenID Connect, and paste the identity provider's metadata.
- Domains tab: add
acme.com, publish the TXT record it shows, then Verify. Turn on Capture to send everyone on that domain to Acme's SSO. - If Acme's IT administrator should do steps 2 and 3 themselves, use Admin Portal link in the organization's header instead. Pick what the link sets up and send it.
Every connection and every claimed domain across all organizations is also listed under Authentication › Enterprise SSO and Authentication › Domains. Enterprise SSO, Admin Portal.
Turn on Directory Sync (SCIM or an HR system)
On the organization's page, open the Directory Sync tab, then New directory. Alternatively, use Authentication › Directory Sync › New directory. Choose one of:
- SCIM, if the identity provider pushes changes to Cbox ID;
- Google Workspace or Entra, which Cbox ID pulls from;
- an HR system: Workday, BambooHR, Rippling, HiBob or Personio.
Directory Sync, HR system sync.
Set up an integration, or find the one that is failing
- Connectors. The catalog lists every kind of integration.
- Set up on a card, such as Outbound SCIM provisioning, opens its setup form. For an HR system or a log stream, choose the provider on the card instead, such as Workday or Splunk HEC, and the form opens with it chosen.
When something is failing, the catalog says so at the top. Review failing lists every failing connection with its last error. Open one, such as a webhook, to see its deliveries and fix it. That is three clicks from the environment's home page.
Find a user: their organizations, sessions and two-factor, and why a sign-in was challenged
Users & orgs › Users, then search by name or email. Or press ⌘K and type the email. The user's page shows:
- their organizations and roles;
- their active sessions, with Revoke and Revoke all;
- their two-factor status, with Reset 2FA.
Sign-in decisions opens Radar filtered to that user's address. Each decision shows the rule that fired and the signals it read. Radar.
Create an organization, invite someone, change a member's role
- Users & orgs › Organizations › New organization.
- On its page, open Members, then Invite by email. Add on the same page is for people who already have an account in this environment.
- To change someone's role, use Edit roles on their row in Members. That covers the one built-in role and any app or custom roles.
Create a custom role, and know when you need something else
Authorization › Roles › New role. Name it, choose which apps it applies to, and pick its permissions. Assign it from an organization's Members tab. Every Authorization page ends with the same short comparison of four things that are easy to mix up:
| You want to say | Use |
|---|---|
"An Accountant may invoices:write" |
Roles & permissions: what a person may do in an organization |
| "Ada may edit the Q3 folder" | Fine-grained authorization: who may do what to which record |
| "The new dashboard is on for Acme" | Feature flags: a rollout, not access control |
| "Acme's plan includes SSO" | Entitlements: set by billing, read from the token, nothing to manage here |
Roles, Permissions, Fine-grained authorization, Feature flags, Entitlements.
Register an app, set its redirect URIs, get its keys, and connect an AI agent
- Developers › Applications › New app. Answer what kind of app it is, and enter the redirect URIs. Its client ID and secret are on the next screen.
- You can change the redirect URIs later on the app's Settings tab.
- Browser-side keys are under Developers › API keys.
- AI agents › Connect gives the MCP server URL and setup for Claude Code, Claude Desktop, Cursor or VS Code. Create a key for this agent issues the key it uses.
Integrate your app, Agents and MCP.
See where every sign-in method is configured
Open Authentication. Its first page, Sign-in methods, lists each method with whether it is on and where it is changed:
- password
- passkeys
- magic link
- social login
- enterprise SSO
- two-factor
- text-message codes
- self-service sign-up
- Radar
- bot challenge
- session lifetime
Three kinds of setting appear there:
- Set for this environment: changed on Authentication policy or Social login. This now includes passkeys, magic links, the bot challenge and session lifetime, which used to be the deployment's alone.
- Set per organization: SSO connections, and an organization's stricter password and two-factor rules.
- Set by the deployment: a method the deployment switched off (for example
CBOX_ID_PASSKEYS_ENABLED=false) stays off whatever the environment says, and the row names the variable. Rows with a deployment limit, such as the longest session, show it.
On a single-tenant install there is no environment console: the same page is under
Sign-in › Sign-in methods in the organization console. Platform operators and owners of
the install's own organization (php artisan cbox-id:installation-organization) change the
environment's settings there too — passkeys, magic links, sessions and text-message
codes on Authentication policy, and the environment's providers on Social login. Authentication policy and sign-in methods.
Run the deployment (platform operators)
From cboxid.com/admin, Platform is one click away; from any Platform page, the
platform environment's own areas are one click away. The same test checks both.
- Suspend a workspace: Platform (1) lists every workspace with Suspend on its row; its own page (2) has the same control. Reactivate undoes it.
- Open an environment's console as an operator: Home (1) from any Platform page is the platform environment's console. On Platform › Environments (2), Open console on the Platform root row does the same.
- Start a support session: Platform › Organization tree (2), an organization (3), then Impersonate on a member, with a reason.
- Add or suspend an operator: Platform › Operators (2).
Brand the sign-in page
Branding. Choose a preset, set the colours, corners and typeface, upload the logo and favicon, and check the live preview; the product name and email sender are further down the same page. The page has one Save: a bar appears at the bottom of the screen with your first change and saves everything on the page at once, and leaving with changes unsaved asks first. To give one organization its own look, open its page, then its Branding tab.