Workspaces & access

A separate balance and operating space for every project.

Create and switch

Your personal workspace is always available. Create a shared workspace from Workspaces, then switch to it before funding it or creating keys. Each workspace has separate balances, keys, offers, receipts, traces, webhooks, and request history. Switching never transfers funds. API keys remain attached to the workspace that created them.

Invite your team

The owner creates a single-use invitation code for an admin or viewer. Share it privately with the intended person. They register or sign in, open Workspaces, and paste the code. Codes expire after seven days and can be revoked before acceptance. A workspace can have up to 50 members.

Roles

• Owner: all operations plus membership and invitation management. Only the owner can request payouts or change the payout address.
• Admin: manage keys, run inference, spend the shared balance, configure webhooks, and operate provider capacity.
• Viewer: inspect workspace data and download exports; cannot mutate it or run inference.

Removing a member or demoting an admin revokes keys they created in the workspace and disables webhook endpoints they configured. Owners cannot be removed or demoted. Keys have their own routing policies and daily/monthly spending limits; their creator is shown in API keys.

Ownership and audit history

The owner can transfer ownership to an existing administrator after confirming their current password. The previous owner becomes an administrator, and unused invitations are revoked. The new owner immediately controls membership. The audit log shows the latest 200 authenticated dashboard operations with person, time, action and result; request bodies and secrets are excluded.

Personal account security

Password and session controls always apply to your own sign-in account, even while using a shared workspace. Changing your password signs out other sessions. Revoke old sessions in Settings. API keys are managed separately. If you forget your password, the operator can issue a one-time reset link. Shared workspaces have no password of their own.