Appearance
Roles
Menu: Settings -> Roles (advanced menu)
Deep link:/_Admin/system/roles?SiteId={siteGuid}
Roles defines which admin features and actions (view / edit / delete, etc.) each site role may use. After assigning roles on Site Users, menu visibility, buttons, and API calls follow this configuration.
Permissions
| Action | Permission |
|---|---|
| View role list | role |
| Add role, edit permissions, Save | role·edit |
| Multi-select Delete custom roles | role·delete |
Advanced menu
Route advanced: true; besides enabling Settings, Roles must appear in Edit Menu (or use master / full-access roles).
How to Open
- In Edit Menu, enable Settings -> Roles.
- Open Settings -> Roles in the left sidebar.
Toolbar
| Control | Description |
|---|---|
| Add role | Opens add role dialog for custom role and permissions |
Role List
| Column | Description |
|---|---|
| Role name | name as tag |
| Edit | Pencil opens permission dialog |
List includes built-in and custom roles, newest first. Built-ins master, developer, contentmanager cannot be multi-selected for delete, but Edit and save to site RolePermission store still work.
Built-in Roles (Overview)
| Role | Description |
|---|---|
| master | All registered features by default (full selection) |
| developer | Dev features: pages, Code, database, integrations, Hooks, etc. |
| contentmanager | Content and commerce ops: content, media, products, etc. |
Exact feature sets per Kooboo version PermissionService.EmbeddedRoles; Edit in admin to view or adjust.
Delete Restrictions
- Built-in roles cannot be deleted.
- Custom roles referenced by Site Users
SiteRolefail delete (The role is in use and cannot be deleted).
Add or Edit Role
Editing shows Edit role; Role name is disabled (no rename). New roles need unique name (1–50 chars, not conflicting with built-ins).
Permission Panel
| Area | Description |
|---|---|
| Select all | Toggle all permissions for role |
| Feature column | Each feature (e.g. pages, content, domain); labels from admin i18n |
| Single checkbox | Features with one action |
| Dropdown features | Label opens View / Edit / Delete (and debug, etc.); per-feature select all |
Checking Edit, Delete, or debug auto-checks View for that feature; View cannot be unchecked while sub-items remain selected.
Save: Role/post → RolePermissionRepository.
Features and Admin Menus
Permissions from PermissionService.GetList() aggregating API [Permission] attributes; new versions may add features. Examples:
| Feature (partial) | Admin capability |
|---|---|
pages | Page design and routing |
content / contentType | Content and content types |
database | Database menu |
config | Integrations |
domain | Domains |
siteUser / role | Site Users, this page |
frontEvents / backendEvents | Request Hooks, Action Hooks |
commerce* series | Commerce submenus |
Left menu also filtered by front-end role presets (ops/designer/developer); API and buttons follow Permissions here.
Relationship to Site Users
| Roles (this page) | Site Users | |
|---|---|---|
| Answers | What a role can do | Who has the role |
| Order | Usually define roles first | Then add members and assign roles |
Typical Workflow
- Review built-in
developer/contentmanager; Edit if needed. - If no preset fits, Add role (e.g.
content-editor), check features, Save. - On Site Users, add collaborators and assign roles.
- Have them log in; adjust permissions here if blocked.
- Before deleting a role, reassign or remove all Site Users references.
Related
| Doc | Description |
|---|---|
| Settings overview | Menu overview |
| Site Users | Members and role binding |
| Edit Menu | Menu visibility and advanced items |