ArchestraDocs
Get Started
  • Connect Your Agents
  • See It Work
  • Migrate Your Agents
Agents
  • GuardrailsAlpha
  • Agent RuntimeBeta
  • Skills
  • PluginsBeta
  • Subagents
  • HooksBeta
  • Triggers & Channels
MCP
  • MCP Servers
  • MCP Gateway
  • Authentication
LLM Proxy
  • Authentication
  • Model Providers
  • Costs & Limits
  • Model Router
Knowledge (RAG)
  • Connectors
  • Files
  • Settings
Chat
  • Projects
  • MCP Apps
Admin
  • Deployment
  • Access Control
  • Environments
  • Identity Providers
  • Logs and Auditing
  • Observability
  • Data Security
Integrations
Contributing
Reference
  • API Reference
  • Configuration
  • Apps SDK Reference
  • Archestra MCP Server
  • Permissions
SlackGitHub
Get Started
  • Connect Your Agents
  • See It Work
  • Migrate Your Agents
Agents
  • GuardrailsAlpha
  • Agent RuntimeBeta
  • Skills
  • PluginsBeta
  • Subagents
  • HooksBeta
  • Triggers & Channels
MCP
  • MCP Servers
  • MCP Gateway
  • Authentication
LLM Proxy
  • Authentication
  • Model Providers
  • Costs & Limits
  • Model Router
Knowledge (RAG)
  • Connectors
  • Files
  • Settings
Chat
  • Projects
  • MCP Apps
Admin
  • Deployment
  • Access Control
  • Environments
  • Identity Providers
  • Logs and Auditing
  • Observability
  • Data Security
Integrations
Contributing
Reference
  • API Reference
  • Configuration
  • Apps SDK Reference
  • Archestra MCP Server
  • Permissions
Docs/Admin

Admin

Administrators operate an Archestra instance and manage who can use its resources. Start with Deployment to install the platform and connect a database.

For organization access, assign roles and resource grants, then connect an identity provider for sign-in and team membership. Use environments to separate resource access, deployment permissions, and network policies.

Protect stored credentials with Data Security. Observability covers logs, metrics, and traces for checking platform health and investigating requests. Settings available to operators are listed in Configuration.

Explore

Deployment
Install Archestra with Docker or Helm and configure production access
Access Control
Assign roles and share resources with users, teams, and service accounts
Environments
Isolate tools, knowledge, skills, subagents, runtimes, and cost limits across deployment environments
Identity Providers
Connect Okta, Microsoft Entra ID, Google, GitHub, GitLab, or any OIDC or SAML provider for sign-in and per-user tool access
Logs and Auditing
See every model request, tool call, and admin change, and choose who can read them and how long they stay
Observability
Export Archestra metrics, traces, logs, and usage events to the monitoring stack you already run
Data Security
Protect stored credentials and content, and manage encryption keys
Edit this page on GitHub

On this page

OverviewExplore