INTEREST JOURNAL DRUPAL & WEB

Drupal Guide in Detail: Assigning Permissions to a Role (7.5)

About 800 words 4 min read

Japanese ↗
On this page

Previous: 7.4 Creating a User Account · Chapter 7 overview · Next: 7.6 Changing a User’s Roles

Detailed guide. This is an unofficial adaptation of User Guide 7.5. The source displays an update date of April 14, 2025; reviewed here on November 5, 2026. The procedure has not been tested in a running Drupal installation.

Goal

Work through the official Vendor-role example, then use the additional checks below to assess the result. Recipe and Vendor are content types in the guide’s example site; use the types and responsibilities appropriate to your own project.

Official User Guide 7.5 ↗ · Chapter summary

Before you begin

The source expects an existing Vendor role and familiarity with users, roles and permissions ↗ . See Creating a Role ↗ if needed.

Our preparation notes: Try this on a test site, using an account allowed to manage permissions. Prepare an ordinary Vendor user and sample content owned by that user for the checks below.

Adapted procedure

  1. Open People → Roles, at /admin/people/roles.
  2. Choose Edit permissions from the Vendor role’s operations menu.
  3. Review the example permissions below. Available entries depend on the enabled modules and content types.
  4. Choose Save permissions and check the confirmation message.
Module Permission in the official example
Contact Use users’ personal contact forms
Filter Use the Restricted HTML text format
Node Recipe: Create new content
Node Recipe: Edit own content
Node Recipe: Delete own content
Node Vendor: Edit own content

This is a teaching example, not a recommended permission set for every site. The source cautions that permissions can have security implications. It also recommends signing in as a created user to check the result.

Checks to try after saving

The following test plan is our addition. Use a separate browser profile for the ordinary user. These are checks to perform, not guaranteed results: other roles, publication state and access-control modules can affect access.

Action What to check
Create a Recipe Can the user open the form and save?
Edit their own Recipe Can the user save a change?
Edit someone else’s Recipe Does the configuration prevent access that the job does not require?
Edit their own Vendor content Can the user complete the intended task?
Access role administration Has an unrelated administrative capability been granted?

Use disposable content on a test site for deletion checks. Record both permitted actions and actions that should remain unavailable so later permission changes can be compared.

Troubleshooting notes

These are our practical suggestions, separate from the adapted procedure.

  • A content-type entry is missing: Check the actual types configured on your site. Do not add broad permissions merely to make your screen resemble the example.
  • Editing owned content fails: Check its author and the permission for that particular content type. See the authorship summary .
  • The user can do too much: Review all roles assigned to the account and any additional access-control modules. Testing only as an administrator can hide this problem.
  • The Contact entry is absent: Check whether Contact is installed and whether personal contact forms are needed; see the release note below.

Notes from releases and security advisories

These notes supplement the original procedure.

If you use Contact

Drupal 11.4.0 ↗ lists Contact among deprecated core modules. Treat the Contact permission as dependent on the actual installation and feature requirements, rather than a universal checklist item.

Existing Contact note · Weekly release summary

If you use Simple OAuth

Sites allowing Consumer creation or editing through Simple OAuth should review SA-CONTRIB-2026-296 ↗ . This is separate from the ordinary publishing-role example.

Fixed releases are 5.2.6, 6.0.10 and 6.1.4. Update the relevant branch, review assignment of Administer consumer access settings, and inspect existing Consumers: updating does not automatically change their configuration. Follow the advisory’s guidance on revoking tokens for Consumers whose legitimacy is uncertain. These actions are conditional on using the affected module.

Module-specific security summary · Existing Consumer note

For Download Count, review view, export and reset permissions by role after updating. SA-CONTRIB-2026-331 ↗ · 2026-11-12

Sources, credits and changes

Source: Drupal User Guide 7.5 ↗ . Its credits name Boris Doesborg, Brian Emery, Jojy Alphonso at Red Crackle, and Joe Shindelar at Drupalize.Me, adapting material from User Roles ↗ by Drupal Community Documentation contributors. Refer to the source’s Attributions statement for contributor links and roles, and to the guide-wide credits ↗ .

The copyright page ↗ states © 2015–2025, individual contributors. Changes here include reorganizing the procedure, adding our test plan and troubleshooting suggestions, and connecting release and advisory notes. This adapted text is available under the same CC BY-SA 2.0 . It is not an official edition or an endorsement. This license notice does not apply to the site design or unrelated articles.

Continue

Chapter · All chapters · Search official information

Back to chapter contents ↗