OXYGENOxygen/ Docs
Workspace

Organizations

An organization is one workspace boundary for data, context, integrations, runs, members, and credits.

An organization is the top-level container for everything in Oxygen. Tables, workflows, integrations, context, runs, members, and credits are scoped to one org.

What belongs to an org

AreaWhat it means
Workspace contextCompany profile, ICP, positioning, assets, and prompts
DataTables, rows, columns, cells, and imports
ExecutionTool calls, column runs, workflow runs, events, and retries
IntegrationsConnected CRM, outbound, enrichment, and data-provider accounts
BillingCredit balance, usage, and subscription state
TeamMembers who can operate or inspect the workspace

User data is isolated by organization. You do not need to manage databases or infrastructure to use Oxygen.

Projects

Within an org, tables and workflows can be grouped into projects. The default project is general.

oxygen projects list --json
oxygen projects create --name "Outbound Q1" --json

A project is a soft grouping for organization and navigation, not a separate billing or permission boundary.

Switching orgs

oxygen orgs list --json
oxygen orgs use <slug>
oxygen whoami --json

oxygen whoami returns the active org plus an onboarding block — see Context.

Multi-org users

Agencies typically use one org per client. Org switching is per CLI profile or MCP session, so check the active org before importing client data or running paid work.

If an MCP client returns organization_selection_required, ask it to call oxygen_orgs_list and then oxygen_orgs_select for the intended workspace.

Billing ownership

Each org has its own credit balance by default. Agencies can link client workspaces to a billing owner when that account structure is enabled:

oxygen orgs billing-link --owner <billing-owner-org-id> --json
oxygen orgs billing-unlink --json

Only use shared billing for workspaces you intentionally manage together.

On this page