Organizations and projects
Tenancy, membership roles, projects, and entitlements.
Organizations and projects
Organization
An organization is the boundary for:
- Membership and RBAC
- Billing / entitlements
- Rights operations and Systems
Create one organization for your company (or a sandbox). Multi-project under one org is the normal model.
Membership roles
| Role | Capability |
|---|---|
| Owner | Full access including billing, publishable key create/revoke, secret rotation |
| Admin | Read + write across projects, consent, rights, systems, maps |
| Viewer | Read only |
Non-members receive 404 on org data (no existence leak). Wrong role receives 403.
Project
A project is an Accord surface: consent config, publishable keys, receipts, project webhooks. Rights Systems and cases are org-level (see product UI for exact navigation).
Entitlements
Plans grant limits, not feature flags named after marketing tiers:
| Typical gates | Meaning |
|---|---|
| Projects max | How many projects an org can create |
| Systems (connectors) max | How many Systems |
| Rights cases / month | Case create / intake volume |
Numeric limits are enforced in the application. Marketing pricing describes the public matrix; the app is source of truth for live entitlements.
Access model (closed beta)
Hosted Erasure is invite-only. Self-hosting uses your own deploy and auth configuration. See Access & setup.