Organizations and teams
Separate teams into workspaces and review agent authority, equipment, and spend.
Give each team a workspace for its agents, context, and tools. The organization owns membership and billing. Workspace scope keeps operational records apart.
Organize the work
Open Organization at /{org} to manage workspaces and members. Creating a workspace also creates its private steering repo, oxagen-<slug>, in your GitHub organization or GitLab group.
Use Organization → Roles to inspect permissions. Owners and Admins can create custom roles and edit or delete custom roles. Built-in roles are read-only. The page shows whether the organization's tier enforces the displayed grants.
RBAC and roles explains the authorization limits. Tenant isolation describes the data boundary.
Fund and inspect agent work
Use Organization → Model funding to configure who pays for model calls. Use Billing for subscription and credits, and a workspace's Spend page for recorded cost. Spend budgets documents the organization and workspace ceilings.
Review evidence
Use Organization → Audit for security events. Open a run from Runs to inspect its recorded work and enforcement tier. Observe-mode activity is recorded, not enforced. A hook-based record is vouched for only by the machine that sends it.
Security and the SOC 2 controls mapping describe implementation controls. These pages are not an auditor's report, a contractual SLA, or a data-processing agreement. Contact hello@oxagen.sh for the current commercial terms and available review materials.