Workspace Billing, Access, and Collaboration

Where you see this in the app

These controls also live in the post-level Workspace config & automations panel under the Config tab.

They decide who can open or edit the workspace, who is billed for AI usage, and how collaborators are granted access.

Workspace and artifact billing modes

The most important billing choices are:

The user-facing meanings are:

The main decision is economic, not technical. Choose the mode based on whether the creator is sponsoring usage or expects each collaborator/viewer to cover their own AI activity.

Organization bill-to selector

When you belong to an organization with permission to spend team credits, the post workspace UI can show a Bill workspace to selector.

The selector starts on personal/default billing. Choosing an organization means future workspace starts for that post request an organization payer. If the server accepts it, the workspace session stores the organization billing account and AI usage is charged to that organization wallet.

The selector only shows organizations where the current user is allowed to spend under that organization's spend policy.

If an org-billed workspace cannot start, check:

• whether the organization wallet has enough available credits,
• whether your organization role is allowed to spend,
• whether the organization is active,
• whether you are trying to use organization billing on a workspace you are otherwise allowed to launch.

Organization billing does not make the organization the owner of the post or workspace. The post author, profile, custom domains, PATs, webhooks, and Stripe Connect payout identity remain user-scoped in V1.

Purchase requirements

The workspace and artifact purchase requirements are separate controls.

This separation matters because a creator may want:

• the artifact site to be publicly viewable while the deeper workspace stays paid,
• the workspace to be available for preview but the final artifact to stay purchase-gated,
• both surfaces to require purchase.

Do not treat workspace access and artifact-site access as the same switch.

Shared edit sessions and view-mode CLI

Two settings strongly affect collaboration behavior:

View-mode CLI in Disabled (preview only) means the viewer only gets the preview layer.

Read-only terminal/Codex means the viewer can inspect through a read-only workspace terminal experience, but that does not make them an editor.

The UI also warns that in read-only collaborator mode, only the post owner can start edit sessions. That warning should be taken literally.

Edit collaborators by tags and email

Edit access can be granted in two main ways:

The audience tags version supports custom membership tags and the special __signed_in__ tag.

That means a creator can choose between:

• broad signed-in access,
• tag-based collaborator groups,
• a short allowlist of specific users.

If collaboration is unexpectedly unavailable, check these access controls before assuming the workspace itself is broken.

Related docs

• Notifications, usage, and AI credits
• Workspace start errors, capacity, and credits