Organizations, members and roles
An organization is the unit that owns everything in NamiDB Cloud: its databases, API keys, management tokens, members, plan and invoices, audit log and alerts. Each organization has its own storage and its own isolated engine, and is billed separately.
You can belong to several organizations and switch between them with the
organization switcher in the console. Each one has a name and a URL slug
(app.namidb.com/console/<slug>).
Roles
Every member has one role. The same rules apply in the console, the management API and SCIM.
| Owner | Admin | Developer | Billing | Member | Viewer | |
|---|---|---|---|---|---|---|
| See the organization, databases, usage and settings | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Read-only queries in the console | ✓ | ✓ | ✓ | ✓ | ||
| Read-write queries, databases, backups, restores, clones | ✓ | ✓ | ✓ | |||
| See API keys | ✓ | ✓ | ✓ | ✓ | ✓ | |
| Create, rotate and revoke API keys | ✓ | ✓ | ✓ | |||
| Plan, spend cap, invoices, billing emails | ✓ | ✓ | ✓ | |||
| Members, invitations and roles | ✓ | ✓ | ||||
| Settings, two-factor requirement, key policy, SSO, SCIM, audit log, the organization’s IP allowlist, exports, management tokens | ✓ | ✓ | ||||
| Delete the organization, transfer ownership | ✓ |
- Only owners grant, change or remove the owner role. SSO, SCIM and management tokens never grant it.
- An organization always keeps at least one owner.
- A key’s own IP allowlist can be changed by anyone who manages API keys (owners, admins and developers).
- API keys are not people: a key’s own role (read-write or read-only) decides what it can do on the data API, whoever created it.
Inviting people
Owners and admins invite from Settings → Members (or
POST /invitations), choosing a role. The invitee gets an email with a link
that:
- works once, for 7 days, and only for the invited address;
- leads through sign-in or sign-up, then into the organization;
- is replaced by a fresh link when you press Resend, and stops working when you revoke it.
No plan limits the number of members today. Organizations with SSO can also add people automatically at their first SSO sign-in, or provision them with SCIM.
Leaving, removing and transferring
- Anyone can leave an organization with Settings → Members → Leave organization. Owners and admins remove others; only an owner removes an owner.
- Ownership moves with Transfer ownership (owners only).
- Removed members lose access at once. API keys and management tokens they created behave as described in API keys and management tokens.
- Every change is in the audit log, and the person concerned gets an email.
Requiring two-factor authentication
Owners and admins can require two-factor authentication for the organization (Settings → Members). Members without a second factor then don’t see the organization until they set one up. See Two-factor authentication.
Deleting an organization
An owner deletes an organization from Settings → Danger zone by typing its slug (and confirming with the second factor when enabled). Then:
- the subscription is cancelled at once, with a final invoice for usage so far;
- every request to its databases is refused, and pending invitations are revoked;
- owners are emailed, and the organization disappears from the console.
For 30 days the data is still recoverable: contact support to restore it, or export it from your account page (Exports). After that, its storage, databases and backups are permanently deleted and the owners are emailed again.
Deleting your account is under Delete account on your account page. It is refused while you are the only owner of an organization that has other members: transfer ownership first.
Paused and suspended organizations
| State | Why | What works | How it ends |
|---|---|---|---|
| Paused | A Free organization had no activity for 7 days (warned a day ahead) | Console; queries answer org_paused | An owner or admin presses Resume, or upgrades |
| Suspended | NamiDB suspended it; the reason is shown in the console and in the error message | Viewing the console, data exports; queries answer org_suspended | Contact support |