# Accounts and workspaces

## Account ownership

An account contains your verified email, name, phone, language and workspace creation limit. A workspace contains the business profile, website, products, tags, collections, members and credit wallet. Integrations belong to the **account**, so a single connection can manage multiple owned workspaces.

The default maximum is one active owned workspace. Admin can change an individual user's maximum from 1 through 1000. The API checks this policy, and database triggers enforce it against concurrent creation or ownership assignment. Reducing a limit does not remove existing workspaces. It prevents additional ownership until the user is below their limit.

Workspace members can be owners, staff or billing users. Delegated integrations currently require an active **owner** membership for every workspace operation. Being invited as staff does not grant an agent ownership privileges.

## Profiles

Use the dashboard Profile section or the account API to edit your name, phone and language. Email changes require the existing verification-code flow; agents cannot bypass it. Account APIs cannot change your role, verification status or maximum workspaces.

Workspace profile changes use workspace-specific operations and existing validation. Changing a workspace billing email requires verification. Website template selection, domain rules and subdomain cooldowns continue to apply.

## Select a workspace explicitly

For MCP, call `list_workspaces` and include the selected workspace ID at the top level of each workspace tool call:

```json
{"workspaceId":"YOUR_WORKSPACE_ID","query":{"page":1,"pageSize":25}}
```

For REST, use `/v1/workspaces/YOUR_WORKSPACE_ID/products` and related resource paths. Never use another account's workspace ID. A browser's currently selected workspace does not select the workspace for an external integration.

## Workspace creation

The `create_workspace` tool and `POST /v1/workspaces` require `workspaces:write` and the same creation data as the dashboard. Obtain template keys from `list_templates` or `GET /v1/templates` with `website:read`. Agents do not create or impersonate a browser session.

New workspaces have separate zero-credit wallets. A customized website requires a phone number and notifies the team. Workspace deletion and destructive account lifecycle actions remain in the verified dashboard flow.