Multi-workspace

One workspace is the default. Run a second when you need different branding, billing, or a hard data boundary.

The 30-second version

Each workspace has its own custom agents, export profile, billing, member list, and credit balance. Most agencies run a single workspace. You'd run a second when you have a sub-brand with a distinct identity, a separate billing entity, or a hard requirement to keep data isolated. Multi-workspace setup today happens through invitations and account provisioning rather than a one-click "create another workspace" UI.

Why this matters

A workspace is a hard boundary in AtelyaOS — agents, samples, exports, and the credit pool live inside it. That's what makes per-client custom agents safe to share with the team, and what keeps your Aurora Coffee samples from accidentally seeding the Northwind agent's Style Memory.

When that boundary needs to be drawn around a sub-brand or a separate business unit, you need a separate workspace. Trying to fit two distinct brands into one workspace causes export profile conflicts and Style Memory cross-contamination.

How it works

What a workspace contains

Per-workspace, isolated:

• Custom agents and their Style Memory profiles.
• Export profile (letterhead, accent colour, contact block).
• Member list and roles.
• Subscription, plan, and credit balance.
• Workrooms and deliverables.
• Tool integrations (OAuth tokens scoped to this workspace).

A user belongs to one workspace at a time today (each user row carries a single workspace_id). To work across two workspaces, you typically use two accounts or accept invitations from the secondary workspace.

When to run two workspaces

Reasons that justify a second workspace:

• Sub-brand with separate identity. Your white-label arm uses a different name, font, and accent colour. One workspace can only have one export profile, so this needs a second workspace.
• Separate billing. A distinct legal entity with its own card on file.
• Hard data isolation. A confidentiality requirement that means client A and client B should not share an agent pool or credit ledger.
• Pilot vs. production. A staging workspace for trying new agents before you let them touch real client work.

Reasons that don't:

• Different clients. Different clients are handled by different custom agents inside the same workspace.
• Different writers on your team. Different writers are workspace members with different roles.

Creating a second workspace

The cleanest path today:

1. From a different email address, sign up for a new account at atelyaos.com.
2. The signup provisions a fresh workspace with its own Free Trial credits.
3. Configure the second workspace independently — export profile, agents, members.

Switching between workspaces means signing out and back in with the other account.

A first-class "create another workspace from this account" UI is on the roadmap. The Agency tier marketing copy advertises multi-workspace support; until the dedicated UI ships, the manual two-account setup above is the supported path.

Billing across workspaces

Each workspace has its own subscription and its own credit pool. A monthly allowance on workspace A doesn't help workspace B. Top-up packs are also per-workspace. See pricing for what each tier costs.

Common pitfalls

• Splitting clients across workspaces. Don't. Use custom agents in one workspace. Splitting causes pointless billing and Style Memory duplication.
• Forgetting which workspace you're in. The workspace name is shown in the sidebar header. If you're working across two, double-check before exporting.
• Sharing agent prompts across workspaces by hand. Copying a system prompt from one workspace to another isn't sync. Edits in one don't propagate.
• Assuming credits roll over between workspaces. They don't. Each workspace's credit pool is independent.

What's next

• Pricing plans — costs per workspace.
• Team collaboration — adding members within one workspace.
• Letterhead and branding — per-workspace branding.