Detailed guide. An unofficial adaptation of User Guide 7.2. Source updated April 14, 2025; reviewed November 5, 2026. No running-Drupal procedure test has been performed.
Official source ↗ · Previous: 7.1 Users, Roles and Permissions · Chapter 7 overview · Next: 7.3 Creating a Role
Goal
Distinguish the first installation account from individual administrator accounts. Read 7.1 first.
The source’s explanation
Accounts have numeric internal IDs. The first account is called user 1 because its ID is one. The original describes exceptional authority independent of assigned roles, including content, accounts, configuration, modules and update scripts. Read this together with the configuration qualification below.
Why use individual accounts?
The source prefers separate administrator accounts over sharing user 1: actions and authorship can be attributed to people, responsibilities can be reflected in roles, and permissions can be designed for safer administration. It also explains that user 1 cannot be deleted through the administrative interface and advises against deleting it directly from the database. This page performs no deletion.
Our verification example
List the people responsible for administration, their individual accounts and their assigned roles. Use ordinary test accounts to assess permissions rather than relying solely on user 1.
A useful distinction
Our explanation: user 1 is an account identity; Administrator is a role. Review the account ID, role assignments and special-access configuration separately. Disabling the exceptional policy does not itself remove permissions granted by a powerful assigned role.
Update note: configuration since 10.3
The official change record ↗
explains that, since Drupal 10.3.0, setting security.enable_super_user to false in services.yml can disable the special user 1 access policy. Assigned roles and other applicable access policies still matter. This predates 2026.
This qualifies the original explanation; it is not an instruction to change the setting. Anyone planning that change should review the complete official procedure, including administrative access and rebuilding the container.
Sources, credits and changes
Source: Drupal User Guide 7.2 ↗ . Contributors and source links listed in its Attributions: Mark LaCroix ↗ · Jennifer Hodgdon ↗ . 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.
Chapter navigation
Previous: 7.1 Users, Roles and Permissions · Chapter 7 overview · Next: 7.3 Creating a Role