Skip to main content

Companies and workspaces

Celeris keeps API keys, credit, and usage inside workspaces. Each workspace also has a company context for team membership and billing. Signing up creates the first company context and Workspace; the Workspace initially uses the company name and can be renamed independently.

One login can have Workspace access across several companies. The account menu's Change workspace list stays flat: each row shows the Workspace name with the company name beneath it. Choosing a row changes both the active Workspace and its company context; there is no separate company selector.

Workspace access and roles​

Admins invite teammates from Team and select the Workspaces to include. Every invitation starts with the Developer role. After acceptance, the Developer:

  • appears in the Team roster;
  • can use only the Workspaces included in accepted invitations;
  • cannot see sibling Workspaces or create another Workspace.

An Admin can promote an active member explicitly from Team. Admins can manage membership, billing, and Workspace actions throughout the company context.

Settings​

Settings → Organization contains the company-name field. It does not show a company directory, sibling Workspaces, aggregate usage, policies, or a company delete action.

Manage the active Workspace's name and deletion under Settings → Workspace. Switch to another Workspace from Change workspace in the account menu. Workspace credit, usage, and API keys stay separate even when two Workspaces share the same company context.