Detailed guide. An unofficial adaptation of User Guide 7.4. Source updated April 14, 2025; reviewed November 5, 2026. No running-Drupal procedure test has been performed.
Official source ↗ · Previous: 7.3 Creating a Role · Chapter 7 overview · Next: Assigning Permissions to a Role (7.5)
Goal
Create the Sweet Honey and Happy Farm vendor accounts. Read 7.1 , 7.2 and 7.3 , and ensure the Vendor role exists.
Preparation notes
Our addition: decide whether notifications should be sent. The source’s honey@example.com is an example, not a mailbox for delivery testing. Substitute a test address you control when checking email.
Adapted procedure
- Open People (
/admin/people) and choose Add user. - Complete the fields below.
- Choose Create new account and check the confirmation.
- Repeat for Happy Farm.
| Field | Source example or explanation |
|---|---|
| Email address | A valid notification address; example: honey@example.com |
| Username | Sweet Honey; spaces allowed, punctuation limited to periods, hyphens, apostrophes and underscores |
| Password / Confirm password | Enter a secure matching password; review strength feedback |
| Status | Active; blocked accounts cannot sign in |
| Roles | Vendor |
| Notify user of new account | Checked in the source example |
| Picture | Select a photo, respecting upload limits |
| Contact settings | Enabled in the source example; availability depends on Contact |
Our checks after saving
Review the account’s name, status and roles in the user list. If notification was requested, check the intended test mailbox. Sign in separately as the ordinary user and try the 7.5 verification examples .
Troubleshooting notes
Our addition: distinguish a sign-in problem from a notification-delivery problem. Check account state, username and the installed authentication method. If Contact settings are absent, consult the Contact note rather than granting unrelated permissions.
Update notes: optional password features
These advisories concern contributed modules, not the core account-creation form itself.
| Module | Advisory and condition | Fixed version |
|---|---|---|
| Reset Password Email/SMS OTP | SA-CONTRIB-2026-305 ↗ : blocked-account resets; someone with appropriate permissions must unblock the account before the new password can be used | 1.0.5 |
| Password Separate Form | SA-CONTRIB-2026-307 ↗ : attacker already has access to the victim’s authenticated session | 2.0.3 |
See the weekly security article and existing chapter note . The source’s contact-setting example also needs the Contact qualification .
Sources, credits and changes
Source: Drupal User Guide 7.4 ↗ . Contributors and source links listed in its Attributions: Diána Lakatos ↗ · Pronovix . 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.3 Creating a Role · Chapter 7 overview · Next: Assigning Permissions to a Role (7.5)