Org Admin
Org Admin
Organization settings sit above projects and govern everything shared across them: membership and roles, billing, domains, telemetry configuration, and identity. The org home itself is a projects dashboard, with search, favorites, per-project audit activity, and admin shortcuts to create projects, invite members, and define roles.
Members with organization read access can view most of these pages; configuration is reserved for organization admins. Each page below states its exact requirements.
Sections
Section titled “Sections”Reusable groups of MCP servers and skills, installable into multiple projects in one go.
Organization membership: members, roles, and pending invites.
Usage against the plan’s allowances, and payment management for self-serve tiers.
Scoped keys for programmatic access: consumer, producer, chat, hooks, and device-agent enrollment.
Serve MCP servers from a branded domain, with DNS verification and an optional IP allowlist.
The switches that power Observe: tool-call logging, tool I/O capture, session capture, fail-open behavior, and OTEL forwarding.
Optional provider compliance and admin APIs (Cursor, Anthropic, OpenAI) that enrich usage, spend, and review data.
Webhook delivery for platform events (preview).
The organization-wide audit feed of who changed what, with expandable diffs.
The on-device agent that enforces required plugins and MCP configuration across every assistant (beta).
Role definitions, scope grants, member assignments, and authorization challenges.
Active OAuth connections agents hold into MCP servers, with bulk revocation.
Single Sign-On and Directory Sync with the organization’s identity provider.
Upstream OAuth issuers that authenticate MCP clients, organizational or project-scoped.