Admin
Admin is the configuration plane — members, teams, providers, API keys, connectors, branding, governance. The pages here are what an Admin or Owner clicks through to set up an org and keep it running.
2 min read
Admin is the configuration plane of Tale. It covers the people who can sign in, the teams that group them, the AI providers behind every reply, the API keys that let external code talk to the org, the third-party connectors agents reach through, and the branding the rest of the org sees. Only Admins and Owners see the full Admin menu; Developers see a subset, and other roles do not see it at all.
These pages describe what each setting does and what it changes about the running product. Most are read once during setup and revisited when something changes — a new hire, a rotated key, a new provider. The role-and-permission story behind the whole menu lives in Members and roles; start there, because every other Admin page references the role names it defines.
Prefer to watch first? Episode 9 tours the whole control room — providers, guardrails, audit, cost — in three minutes, captions included.
Configuration areas
Members and roles
The six roles and the resource-level matrix that says who can read, write, configure, and govern.
Teams
Group members into teams that share agents, skills, and connectors.
Agents
Every agent the org has, and where an Admin steps in when one needs governance.
AI providers
Store the credentials behind every reply and pick which models the org may call.
Connectors
Store and replace the credentials behind Slack, Gmail, Outlook, Google Drive, GitHub, Shopify, and more.
Enterprise SSO
Wire sign-in to your identity provider with SAML or OIDC.
API keys
Mint and scope the keys external code uses to reach Tale's REST API.
Branding
The name, logo, and colors the rest of the org sees.
Two-factor authentication
Require a second factor for sign-in and manage enrolment across the org.
Changelog
The in-product record of what shipped and when.
Governance
Audit logs, policies and limits, guardrails, analytics, retention, and legal hold.
Where this fits
Admin is the surface every other tab assumes. Chat resolves a model through the providers configured here; agents call tools through the connectors configured here; the skill library and the inbox respect the team boundaries configured here. The natural first read is Members and roles — every other Admin page references the role names it defines.