Operator workflows
Review authority, tools, spend, and evidence across teams.
Use the operator console to decide what each agent may do and inspect what happened on calls routed through Oxagen.
Review authority
Open Organization → Roles to inspect permissions and their enforcement status. Open an agent's mandate to review its authority and equipment. Agent roles explains how an agent's role narrows its requests.
For membership changes, use the organization page or change_member_role and remove_org_member. Query membership events with query_audit_log. The former Access Reviews screen is not part of the current app.
Separate teams
Create a workspace for each operating scope, then assign membership and register its agents. Each workspace has its own context and equipment. Tenant isolation explains what the database and store clients enforce.
Manage equipment
Use the Agents page to review MCP servers, toolbelts, policies, runtimes, and off switches, and Mandates to review each agent's authority. Use Steering for instructions and rules and Skills for skills. A credential held for a mediated connection stays in Oxagen. The agent requests an action through the governed path.
Metered spend
Inspect a workspace's Spend page, then open a run for its recorded cost. Use oxagen budget show to read organization and workspace ceilings. Set a ceiling with oxagen budget set as an authorized billing manager.
Model funding distinguishes your provider key from Oxagen-funded tokens. Billing explains credits and admission checks. A pre-call or pre-turn check does not promise that concurrent work cannot cross a limit.
Assemble review evidence
Use Organization → Audit or query_audit_log to inspect security events. Read the audit logging limits before treating the records as complete evidence. The two stores record different events, and failed asynchronous writes do not fail the governed action.
A SOC 2 controls mapping helps an auditor locate implementation evidence. It is not an auditor's report.