Access levels
Every user carries an access level. Each level unlocks one more area than the one below it, so a higher number is a superset of the lower ones.
| Level | Label | Can do |
|---|---|---|
| 10 | Basic | Read content (fields), read-only. |
| 20 | Content manager | Edit content in existing collections. |
| 30 | Data manager | Also create and change schemas (collections and fields). |
| 40 | Project manager | Also create and configure projects. |
| 50 | Company manager | Also manage the company and its users. |
| 60 | Agency manager | Full scope across the agency and its client companies. |
Invite client editors at level 20 so they can edit their site’s content without touching the schema; give a technical lead 30+ so they can model data; reserve 50–60 for people who run the account.
Company scope
Section titled “Company scope”Access is always scoped to a company. A client company’s users see only their own company and its projects. An agency (a company that owns sub-companies) sees its whole portfolio — see Agencies and client projects.
The admin panel
Section titled “The admin panel”The internal control panel (projects, companies, users and tokens across the whole platform) is separate from the dashboard and is limited to staff accounts. Signing in there with a non-staff account is refused, regardless of access level — that panel is for the platform operator, not for agencies or clients.