Note: If these Terms, Policies, or Agreements are available in multiple languages, and any discrepancies exist between translations, the English version shall prevail.
1. Account structure
BabySea supports both personal accounts and team accounts.- A personal account is the default account created for an individual user.
- A team account is a shared workspace used by multiple members inside the same organization or project.
- The API and dashboard operate at the account level, which means API keys, webhooks, billing, logs, credits, and domains are attached to the relevant account. API key configuration and webhook setup are described further in API and inference.
2. Role model
BabySea uses a three-level role model in the team account experience.| Role | Customer-facing meaning | Access pattern |
|---|---|---|
| Primary Owner | The account owner-of-record for the workspace | Full access, including billing purchases and primary account settings |
| Owner | Operational admin for the workspace | Full operational management except billing purchases reserved to the Primary Owner |
| Member | Standard collaborator | View access to shared workspace data, with limited or no management actions |
owner or member. The Primary Owner role is a customer-facing designation derived from the current owner-of-record for the account.
3. Workspace management areas
The role model affects how customers use the dashboard.- API keys, Webhook, and Domains are operational management areas. Owners and the Primary Owner can manage them. Members can view the page contents in the current product but do not receive the same write actions.
- Members is the team management area used to invite and administer collaborators.
- Billing is visible to all team roles in the current product, but purchasing plan changes, payment method changes, and credit-pack purchases are reserved to the Primary Owner. Plan and credit details are described further in Billing and credit.
- Settings holds workspace configuration such as team name, picture, and account settings. Higher-sensitivity actions are limited to the Primary Owner.
- Activity, Logs, Credits, and Metrics are shared operational views available to the account.
4. Customer responsibilities for workspace administration
If you act as a workspace administrator, you are responsible for:- assigning appropriate roles inside your organization;
- controlling access to API keys, webhook destinations, and custom domains;
- removing access for users who no longer require access;
- ensuring that customer-side systems consuming BabySea events and outputs are operated securely; and
- monitoring billing, credits, and account activity for your own compliance needs.