Skip to main content
Keel Docs Showcase

Who can do what

Keel has no user system of its own. What a person may do comes from Pimcore's users, roles and permissions. This page proposes five user types and the exact Pimcore settings for each.

Tip: build each type as a role, and give people only roles. The role then decides, and nothing is left in the user's own rows.

How Keel follows Pimcore

  • Buttons you may not use are hidden or disabled. No Save without save, no Delete without delete, no New … without create, and a bulk bar only offers what you may do on at least one of the list's folders. The server checks every action again.
  • Saving a published item without the publish right saves a new version. The live item does not change. A notice says so.
  • A new item without the publish right is saved as a draft: Created as a draft – publishing needs the publish right.
  • Assets are hidden unless the user has the global Assets permission. Keel follows Pimcore here: tick Assets on the role.
  • Pages: the SEO and navigation fields need settings on the page, the "noindex" fix needs properties (besides save).
  • Bulk actions: an item you may not see is listed as #id, not by name.
  • Relation dropdowns only offer items you may see.
  • History records the real user, so versions and the recycle bin show who did it.

The types

"Content folders" are the folders of your Keel lists (data objects), the asset folders and the documents you want the person to work on.

Admin – runs the place

Publisher – decides what goes live

  • Global permissions: Data objects, Assets, Documents; optional Notifications, Notes & events, Recyclebin.
  • Workspaces (Data objects, Assets, Documents; on the content folders): list, view, save, publish, unpublish, delete, rename, create, settings, versions, properties.
  • Can: create, edit, publish and unpublish, delete, bulk actions, assign, change status, history and restore, page SEO and fixes, upload and replace files.
  • Can't: Customize, Data model edits, Scripts & tracking.

Editor – writes, someone else publishes

  • Global permissions: Data objects, Assets, Documents, optional Notifications.
  • Workspaces: list, view, save, create, rename, versions; add settings and properties on pages if they do SEO. Leave out publish, unpublish, delete.
  • Can: create items (as drafts), edit drafts, edit live items as new versions, assign, upload files.
  • Can't: publish or unpublish, delete, change the status of a live item, bulk publish.

Worker – works on what is given to them

  • Global permissions: Data objects, Notifications, Notes & events.
  • Workspace on the work folder (for example the enquiries): list, view, save. Add publish if they must move live items between statuses.
  • Can: see the number of items assigned to them, open the list's Assigned to me filter, assign and reassign, write internal notes, change status (with publish), see activity. Turn assignments on for the class in Customize.
  • Note: Pimcore has no "only items assigned to me" permission. Assigned to me is a filter, not a limit: a worker can open every item in the folder.

Viewer – looks, doesn't touch

  • Global permissions: Data objects, plus Assets and Documents if they should see those.
  • Workspaces: list, view; add versions to let them read the history.
  • Can: browse, search, open items, preview, read history, see the overview, write internal notes (viewing is enough), run the Keel page check.
  • Can't: save, create, delete, publish, assign, change status. The editor opens read-only and the buttons are missing.

Translator

Translates, and sees only what that takes.

  • Global permissions: Data objects.
  • Workspaces: list, view, save; add versions to let them read the history.
  • Limits: in Field access, press Translator and choose the languages they can see and edit.
  • Can: change the fields per language, in the languages they may edit. Read the rest.
  • Can't: change other fields, see languages or fields left out, publish unless given the right.

How to give a team access

  1. In Pimcore open Settings → Users / Roles and add a Role (for example "Editors").
  2. Permissions tab: tick the global permissions of the type (see above). For anything with files, tick Assets.
  3. Workspaces tab: add your content folders under Data objects, Assets and Documents and tick the rights of the type. A right applies to the folder and everything below it; a deeper row overrides a higher one.
  4. Open each user, add the role under Roles, and leave the user's own permissions and workspaces empty.
  5. Ask the person to sign in again. Check with a test user: the buttons should match the type.

The object folders are the ones your lists use. Nothing here needs keel.yaml.