Plans and access
Baseline distinguishes plans. The plan decides whether you work locally, use an account with extended features, or organize teams in the cloud.
Overview
Section titled “Overview”| Plan | Account | Organizations and cloud bases | Typical use |
|---|---|---|---|
| Single | no | no | Local in the browser, no sign-in |
| Professional | yes | no | Extended features locally |
| Cloud | yes | yes | Teams, shared bases, push, review |
| Enterprise | by agreement | by agreement | Custom / on-premise; cloud features such as Review per contract |
Single
Section titled “Single”You start without an account. Data stays on your device. Export and import via .baseline files remain available. There are no organization roles.
Professional
Section titled “Professional”After signing in you use extended features (for example advanced diagrams) locally. There is no cloud access: you do not create an organization and do not open cloud bases. Review is not included. Organization roles do not apply here.
In “Continue work”, the Cloud tab for Professional shows that you are signed in and what the plan includes — without organization setup.
With the Cloud plan you can:
- create an organization or accept an invite,
- use cloud bases together,
- save a draft and push it for the team,
- run a content review of visible entries and produce an immutable report,
- set block permissions in the schema panel (read, edit data, model, review, publish).
Organization roles
Section titled “Organization roles”Organization roles apply only on the Cloud plan.
| Role | Meaning |
|---|---|
| Org admin | Manage the organization: invites, members, purpose databases; full access to all bases. At least one org admin must remain. |
| Org member | Sees all organization bases (name/existence); works on bases according to base rights. |
| Guest | Sees the organization; bases only when assigned (then according to base role). |
Email invite: an org admin chooses guest or org member and optionally a base with a base role. Existing users are notified and become members only after accepting (including optional base assignment). New users register via the invite link. Each person counts once toward seat limits by organization role.
Base roles
Section titled “Base roles”Base roles apply only on the Cloud plan and only for opened cloud bases.
| Role | Meaning |
|---|---|
| Creator | Model schema, edit data, manage base members; at least one creator per base. |
| Editor | Edit and read data; no schema modeling. |
| Member | Read content; no write access. |
Org admins have full access to all bases even without a base-role row. Org members see all base names; content only with a base role. Guests see only assigned bases (rights follow the base role). Creators add only known org members/guests — new externals are invited by an org admin.
In settings: Members (organization, including optional base assignment).
System rules (Cloud)
Section titled “System rules (Cloud)”- At least one org admin per organization.
- At least one creator per base.
- Leaving the organization clears all of that person’s base rights.
- Org admins have full access to all bases (no base-role row required).
- Only an org admin invites new externals (as org member or guest, optionally with a base); creators add only known org members/guests to a base.
- Creating a base makes the creator the Creator.
- Seat limits count each person once by organization role; base roles do not add seats.
Enterprise
Section titled “Enterprise”Enterprise is a custom agreement (often on-premise). Whether cloud features such as Review and block permissions are available depends on the contract.