LokAkrt workspace accounts use two roles managed under Users (Admin only):
| Role | Meaning |
|---|---|
| User | Everyday authoring: pages, media, data, templates, jobs |
| Admin | Everything a User can do, plus Users, Server status, Usage, Insights, global page edit, and admin Settings tabs |
This is separate from client app users authenticated via plugins such as Password Auth (dataset-backed). See Project Settings for Auth secret and Client key.
| Area | User | Admin |
|---|---|---|
| Home, Pages, Blocks, Media, Projects, Templates | Yes | Yes |
| Datasets, Data Sources, Email Templates, Jobs | Yes | Yes |
| Settings → General (debug) | Yes | Yes |
| Settings → AI / Store / Server / Security / Contact / Pages | — | Yes |
| Edit global pages | — | Yes |
| Users CRUD | — | Yes |
| Server status | — | Yes |
| Usage | — | Yes |
| Insights | — | Yes |
| Plugins / Store / Tools (manage project) | Yes (own project) | Yes |
| Super-user / recovery login | — | Operators recover as an Admin; see Super-user login |
| Page-level access (public / sign-in / roles) | Configure on pages | Configure on pages |
Page access roles (who may open a screen in the Ionic app) are configured on each page under Page → Properties, independent of whether the editor is User or Admin.
Wiki navigation uses four documentation audiences (not CMS checkboxes):
| Docs audience | Meaning |
|---|---|
| User | Authors sites with existing plugins/pages; may release the mobile app |
| Admin | Operators of workspace/project core config (Settings, Users, plugins, Auth secret / Client key, Store URL). Includes many CMS User project owners |
| Developer | Creates plugins, apps, and templates for LokAkrt |
| Contributor | Changes LokAkrt core |
Start at the home audience doors: User · Admin · Developer · Contributor.