-
Notifications
You must be signed in to change notification settings - Fork 0
Users and Permissions
Admin users are managed under System → Users in the admin panel.
| Property | Description |
|---|---|
| Name | Display name |
| Login email | |
| Password | Hashed login password |
| User Group | Determines permissions |
| Language | Preferred admin interface language |
| Root Item | Personal tree root — overrides the group's entry item |
Groups control what actions users can perform. Manage them under System → User Groups.
| Permission | Description |
|---|---|
| Create/Edit/Delete/List Users | Manage admin user accounts |
| Create/Edit/Delete/List Blueprints | Manage content type definitions |
| Create/Edit/Delete/List Groups | Manage user groups |
Each group has an Entry Item — the root of the content tree that members of this group can see and edit. Use this to scope editors to specific subtrees (e.g. a marketing team that only sees the Blog branch).
Per blueprint, you can grant a group CRUD permissions:
| Permission | Description |
|---|---|
| Create | Can create new items of this blueprint |
| Read | Can view items |
| Update | Can edit items |
| Delete | Can delete items |
Set Allow All Blueprints to grant access to all blueprints without listing them individually.
Individual workflow steps can be restricted to specific groups. Only members of the allowed groups can advance an item past that step. Leave empty to allow anyone.
Example: blog editor who can only manage blog posts.
- Create a User Group named "Blog Editors"
- Set Entry Item to the Blog container item
- Under Blueprint Permissions, add
blog_postwith Create + Read + Update (no Delete) - Assign users to this group
A user with full access (no entry item restriction, allow all blueprints, all global permissions) acts as a superadmin. The default admin@admin account seeded by the demo app has this configuration.