Split 'administer permissions' into a new administer roles permissions

Created on 12 June 2007, over 17 years ago
Updated 21 August 2024, 3 months ago

Problem/Motivation

On busy websites with many users, it becomes essential to be able to delegate some tasks, for example the management of the user's roles. As it is, you can give the 'administer permissions' to the users who will be in charge of managing the user's roles, but this also allows them to access the Roles and Permissions admin pages!

The RoleAssign module creates this permission, but I believe this feature would be useful in the core, as opposed to having to use an extra module for such a basic feature. (see the desription of the module for more information).
Here is a statement of the access control page.

Permissions also allow trusted users to share the administrative burden of running a busy site.

No doubt this extra permission would extand the flexibility of sharing the administration of busy sites.

Proposed resolution

As suggested in #7 create two new permissions:

  • 'administer roles' to give access to admin/people/roles
  • 'assign roles' to show the role selector in user edit form (and show the role-related bulk operations on user admin view)

(and keep 'administer permissions' to give access to admin/people/permissions)

Remaining tasks

<!-- See https://drupal.org/core-mentoring/novice-tasks for tips on identifying novice tasks. Delete or add "Novice" from the Novice? column in the table below as appropriate. Uncomment tasks as the issue advances. Update the Complete? column to indicate when they are done, and maybe reference the comment number where they were done. -->

User interface changes

Two new permissions

API changes

None.

Data model changes

None.

✨ Feature request
Status

Needs work

Version

11.0 πŸ”₯

Component
User moduleΒ  β†’

Last updated about 12 hours ago

Created by

πŸ‡¨πŸ‡¦Canada scor Toronto

Live updates comments and jobs are added and updated live.
  • Security improvements

    It makes Drupal less vulnerable to abuse or misuse. Note, this is the preferred tag, though the Security tag has a large body of issues tagged to it. Do NOT publicly disclose security vulnerabilities; contact the security team instead. Anyone (whether security team or not) can apply this tag to security improvements that do not directly present a vulnerability e.g. hardening an API to add filtering to reduce a common mistake in contributed modules.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Just ran into this in a large project and was wondering why "Administer user roles" is still combined with administering permission.
    So +1 on finishing this, where Drupal is today!

Production build 0.71.5 2024