Skip to main content

Organizations

Every Celeris account belongs to an organization, created automatically when you sign up and named from the "Organization" field during Account Setup. If you work alone, you may never need to think about it: your organization holds your one workspace and your billing details, and everything you do day-to-day happens at the workspace level. Organizations matter once you add teammates, run several workspaces, or want to set org-wide policy.

Organizations and workspaces​

An organization contains one or more workspaces. The first workspace initially takes the organization's name; you can rename either independently.

  • Workspaces own the day-to-day resources: API keys, credit balances, and usage. See Organizations and workspaces for how switching between them works.
  • The organization owns membership and the billing customer identity: the saved card and billing email. An organization admin can use the same payment method across all of its workspaces, while each workspace keeps its own credit balance and spend. Billing is under Settings → Billing, reached from the account menu in the bottom-left of the Console; see Console & billing.

Roles​

Teammates join at the organization level, in one of two roles:

  • Admin - manages members, org-wide settings and policies, billing, and workspace admin actions.
  • Developer - a regular member with access to the workspaces they've been added to.

Invitations and role changes live on the Team page; see Team and Workspace invites.

Settings → Organization​

Settings → Organization shows every member:

  • the organization name (admins can rename it);
  • the member roster: name, email, role, and active/invited status;
  • the organization's policies (read-only unless you are an admin).

Organization admins additionally see:

  • a workspace directory listing each workspace's name, status, member count, and balance, with a delete action;
  • aggregate stats: active members and pending invites, the combined credit balance across all workspaces, and the request count and credit spend over a selectable 24-hour, 7-day, or 30-day window.

The current workspace itself - switching it, renaming it, and its funding and API-access status - is managed in Settings → Workspace.

Deleting a workspace​

Organization admins can delete a workspace from the workspace directory. Deleting a workspace cannot be undone:

  • every member loses access to it;
  • its API keys stop working within about a minute;
  • any remaining credit is forfeited.

The organization's last workspace cannot be deleted, and a suspended workspace cannot be deleted from the Console - only support can restore a suspended workspace.

Removing a member​

Organization admins can remove a member from Settings → Organization or the Team page. Removal takes effect across the whole organization: the member loses access to every workspace, and the private API keys they created are revoked. Workspace-shared keys they created keep working - rotate them as part of offboarding.

Organization policies​

Admins can set two org-wide policies from Settings → Organization:

  • Require multi-factor authentication. Every member who hasn't enrolled authenticator-app MFA sees a persistent Console prompt to set it up. It is a prompt, not a lockout: members can keep working while unenrolled. Accounts that sign in through SSO handle MFA with their identity provider and are not prompted.
  • Allow workspace-shared API keys. When turned off, no one - admins included - can create new workspace-shared keys in any workspace of the organization. Existing shared keys keep working until rotated or revoked and remain manageable.