Detailed guide. An unofficial adaptation of User Guide 7.1. Source updated April 14, 2025; reviewed November 5, 2026. No running-Drupal procedure test has been performed.
Official source ↗ · Chapter 7 overview · Next: 7.2 The User 1 Account
Goal
Understand the connection between an account, its roles and the permissions that allow actions. The guide’s market-site example separates vendors, content editors, account managers and site administrators.
Users
Visitors include anonymous users and authenticated users. The guide also describes the first account created during installation, user 1. Its exceptional privileges need the qualification in 7.2 .
Permissions
Permissions govern actions such as viewing, editing and configuration. Modules define them. Editing one’s own content is distinct from editing another person’s content, and permissions can be specific to a content type.
Roles
Group permissions into roles, then assign roles to accounts. Authenticated accounts fall under Authenticated user and may have additional roles. Anonymous user governs permissions for visitors who are not signed in. The presence of an Administrator role depends on the installation configuration.
| Role in the source example | Responsibility |
|---|---|
| Vendor | Edit their own vendor listing |
| Content editor | Edit general market pages |
| User manager | Manage vendor accounts |
| Administrator | Manage configuration as an experienced administrator |
Our verification example
Choose one test account and trace account → assigned roles → permissions. Review permissions granted broadly to authenticated users, as well as the account’s extra roles. Test required actions and unwanted administrative access separately.
Common points of confusion
Our explanation: creating an account, creating a role, granting permissions to a role and assigning a role are separate operations. A newly created role is not evidence that publishing permissions are ready. Continue with 7.3 , 7.5 and 7.6 .
Connection to changes
The source’s description of user 1 needs a configuration-dependent qualification introduced in Drupal 10.3; see the official change record ↗ and 7.2 . Permissions introduced by optional modules are addressed separately in the Simple OAuth note .
Sources, credits and changes
Source: Drupal User Guide 7.1 ↗ . Contributors and source links listed in its Attributions: Mark LaCroix ↗ · Boris Doesborg ↗ · Jennifer Hodgdon ↗ · “User Roles” ↗ · Drupal Community Documentation ↗ . Refer to the original for writing, editing and adaptation roles, and to the guide-wide credits ↗ .
Copyright remains with the individual contributors; the official copyright page ↗ states © 2015–2025. Changes include reorganization, our preparation and verification examples, troubleshooting notes and links to relevant changes. Original screenshots and videos are not reproduced. This adapted text is shared under CC BY-SA 2.0 . It is not an official edition or endorsement. This notice does not license unrelated articles or the site design.