Admin Dashboard: Access
The Admin Dashboard is the control surface for schemas, agents, models, knowledge, integrations, security, and operations. It does not present its own username-and-password form.
When to use it
Section titled “When to use it”Use Admin for interactive configuration, testing, inspection, and incident response. Use scoped API keys, MCP, or configuration as code for automation.
How access works
Section titled “How access works”- SyntheticBrew Cloud: sign in on
syntheticbrew.ai, then open the dashboard. Cloud creates a short-lived signed Admin session. - SyntheticBrew Enterprise: the configured authentication mode controls access. Local mode creates a short-lived local Admin session; external mode accepts tokens from the identity integration configured by your Enterprise administrator.
Opening an Admin deep link preserves the destination after authentication. OAuth consent for coding agents also uses the active Admin identity so approval is bound to the correct subject and deployment.
Open the dashboard
Section titled “Open the dashboard”- In Cloud, sign in and choose Dashboard. In Enterprise, open the
/admin/URL supplied by your administrator. - Wait for the Authenticating… screen to complete.
- Confirm that Overview loads and the sidebar shows your expected resources.
The expected result is an authenticated dashboard session. The access token is kept in browser storage and is not shown in the UI.
Expired-session recovery
Section titled “Expired-session recovery”The dashboard checks token expiry before mounting protected pages. If an OAuth consent request discovers a missing or expired session, it starts authentication again rather than leaving an unusable Allow button on screen.
If access still loops, return to the Cloud sign-in page or your Enterprise identity provider and start again from the original Admin URL. Enterprise administrators should also verify the public URL, issuer, signing keys, audience, and system time.
Security cautions
Section titled “Security cautions”- Do not copy browser access tokens into tickets, chat, or coding-agent prompts.
- Use API Keys for non-browser automation and grant the smallest scope set.
- In Enterprise, expose Admin only on the networks and through the identity controls approved for administrators.