Organizations and Workspaces

Orqio uses a two-level structure to keep your automations organized and your environments separated.

What is an organization?

An organization is your company's account in Orqio. It's the top-level boundary for everything you do:

• All your team members belong to the organization
• All your workspaces live inside it
• Billing, governance, and access policies are managed here

Most teams have one organization. If you work with multiple companies or clients, you might have more than one.

What is a workspace?

A workspace is an isolated environment inside your organization. Think of it as a separate "room" where everything -- workflows, credentials, API keys, contacts, and execution history -- is kept separate.

Why separate workspaces? So you can test safely without affecting live operations.

Recommended setup

Workspace	Purpose	Who uses it
staging	Build, test, and experiment	Product, Engineering
prod	Run live automations	Operations, Engineering

You can also create additional workspaces (like sandbox) for experiments or demos.

How they work together

Organization (your company)
├── staging workspace
│   ├── workflows, credentials, API keys, contacts
│   └── execution history
└── prod workspace
    ├── workflows, credentials, API keys, contacts
    └── execution history

Everything is workspace-scoped. A credential created in staging doesn't exist in prod, and vice versa. This isolation is intentional -- it prevents test data from leaking into production.

Why this matters

• Safe testing. Build and break things in staging without affecting real users.
• Separate credentials. Use test API keys in staging and real ones in prod.
• Clear boundaries. Everyone knows which environment they're working in.
• Controlled releases. Build in staging, validate, then recreate in prod.

Moving from staging to production

Orqio doesn't have a one-click "promote" button. Instead, follow this process:

1. Build and test your blueprint in staging
2. Verify execution reports show the expected results
3. Recreate the blueprint in prod with production credentials
4. Publish and monitor the first few production runs

This deliberate process ensures you review everything before it goes live.

Finding your IDs

When working with the API, you'll need your orgId and workspaceId (both are UUIDs).

You can find them through the API:

• List organizations: GET /api/v1/orgs
• List workspaces: GET /api/v1/orgs/{orgId}/workspaces

Inviting your team

You can invite team members to your organization and control which workspaces they can access. See Inviting Users for details.