Problem/Motivation

As per documentation here and here, Content Administrator should be more privileged user role then Content Editor, but what we noticed at the moment is that Content Editors have the permission to 'administer menu' when Content Administrator don't.

Proposed resolution

  1. Review permissions list on both roles
  2. Remove permissions provided by not bundled modules, like 'Use PHP input for field settings (dangerous - grant with care)' & 'use PHP for label patterns'
  3. Add administrative permissions to Content Administrator, like 'administer menu', 'access toolbar' & 'access administration pages'
  4. Remove administrative permissions from Content Editor
  5. Remove unrelated to content editing permissions from both roles, like 'access user profiles' - this might be intended but then both roles should have it
  6. Update documentation page https://www.sector.nz/documentation/preconfigured-user-roles-user-profil... to point https://www.drupal.org/docs/user_guide/en/user-concept.html instead of outdated https://www.drupal.org/docs/7/understanding-drupal/users-permissions-and...

Remaining tasks

  1. Confirm/update proposed approach
  2. Create a task list based on the outcome of the above

Comments

RoSk0 created an issue. See original summary.

rosk0’s picture

Issue summary: View changes
danielveza’s picture

Status: Active » Postponed (maintainer needs more info)

This is likely a documentation issue.

but what we noticed at the moment is that Content Editors have the permission to 'administer menu' when Content Administrator don't.

This is by design at the moment. In Sector we made the decision that rolls should be additive. So Content editor is a base role, and other roles should be built on top of this role.

So Content Admins should have the Content Editor and Content Admin roles. This can be seen in our sample user setup https://git.drupalcode.org/project/sector/-/blob/9.1.x/sector.install#L115.

With that in mind, would you be able to adjust your list to remove what isn't relevant?

dieuwe’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)