Users & permissions
For ready-made user types and a step-by-step setup see Who can do what.
Keel uses Pimcore's own users, roles and permissions – there is nothing extra to set up.
What users see and may do
| Pimcore setting | Effect in Keel |
|---|---|
| Workspaces (objects, assets, documents) | Which items appear in lists, search and counts |
| list / view | Whether an item shows and opens; list also decides who can be assigned to it |
| create | New …, upload |
| save | Save, bulk Set field… / Move to…, assigning the item (assignments) |
| publish / unpublish | The Published switch, bulk publish. In the content editor, users who may not publish save drafts. |
| rename | File name and folder of assets, page name in the URL |
| delete | Delete |
| versions | The item's saved versions (History, or Saved versions in the Activity tab) |
| documents permission | The Documents area (pages) |
| objects permission | The Data model page |
| Custom layout, view and edit languages of a workspace | Which fields and languages a role sees and changes: Field access |
| Admin | Customize, Adjust fields |
Markets
When the project has a market switcher, each market shows only the content in its folder. All shows everything the user may see.
Safety
- Every change is checked on the server against the user's permissions, whatever the screen shows.
- Saves never overwrite someone else's newer save – Keel asks the user to reload instead.
- Every save is a Pimcore version, so changes can be undone in History or in Pimcore.
- Keel's write requests are protected against cross-site requests (Pimcore's CSRF check in the classic admin, a request header in Studio).
Settings are per environment
Customize and field tweaks are stored in the database (Pimcore settings store, scope keel). Staging and production
each keep their own – set them up once per environment.