What the page shows
The page header is a green Add User button (top-left), then User List in bold, then a control strip with “Show / entries” pagination, Select all, Deselect all, Columns (a column-visibility toggle), and a red Delete selected button (for bulk deletes), plus a Search field on the right. Below the controls, a single table:| Column | What it shows |
|---|---|
| ID | The integer DryRunPro user ID. Sortable. |
| Name | The user’s display name. |
| The user’s email address (used for sign-in and invites). | |
| Email verified at | A checkbox tick for verified, blank for not yet verified. |
| Approved | A checkbox tick for approved, blank for pending approval. |
| Roles | A coloured chip showing the assigned role, e.g. blue “Admin”, purple “Team Leader”, green “Developer”, orange “Tester”. |
| Action | Three buttons per row: green View, blue Edit, red Delete. |
| ID | Name | Verified | Approved | Roles | Action | |
|---|---|---|---|---|---|---|
| 39 | Alex S | alexsafcencu@247commerce.co.uk | tick | tick | Team Leader | View / Edit / Delete |
| 16 | jugnu | jugnu@247commerce.co.uk | tick | tick | Admin | View / Edit / Delete |
| 1 | DryrunPro admin | monitor@247commerce.co.uk | tick | tick | Admin | View / Edit / Delete |
Two scopes: tenancy users vs project-scoped Cloud users
DryRunPro has two distinct user rosters and they often confuse new admins:- Project Users (this page). The tenancy-wide roster. Anyone listed here has a DryRunPro login. Their access to specific projects is determined by Teams and direct project assignments.
- Cloud Users (on the Project Overview page, Cloud Users tab). The Adobe-side roster for one Adobe Commerce Cloud project, mirrored read-only from
accounts.magento.cloud. These are not DryRunPro logins until you click the Add to Dryrunpro button on a row, which provisions them as a Project User.
- The engineer is already a user on the customer’s Adobe Commerce Cloud project (the customer has added them on the Adobe side).
- Open Project Overview, Cloud Users tab.
- Find the engineer’s row and click Add. DryRunPro provisions them as a Project User and sends a magic-link invite to their email.
- They click the invite, set a password, and land on the Projects tab.
Adding a user manually
To add a user who is not on the Adobe-side roster (e.g. an internal QA engineer who only needs DryRunPro access), use the green Add User button on this page.- Click Add User. A dialog opens.
- Fill in: Name, Email, Role.
- Optionally pre-assign teams.
- Click Save.
Editing a user
Click the blue Edit action on a row. The Edit dialog lets you change:- Name, Email.
- Role, picked from the four roles: Admin, Team Leader, Developer, Tester.
- Teams, multi-select against the team list.
- Approved, the checkbox.
- Direct project access, the per-project assignment (rarely used; teams are the preferred grant mechanism).
Deleting a user
Click the red Delete action on a row, confirm in the dialog, and the user is removed. What happens on delete:- The user can no longer sign in to DryRunPro.
- Their direct project assignments are dropped.
- Their team memberships are dropped (the teams remain).
- Any dryrun environments owned by the user are reassigned to the deleting admin (so they are not orphaned).
- Audit log entries authored by the user remain (deletion does not nuke history).
Role chips
The Roles column uses coloured chips for at-a-glance role identification. The colour scheme matches the Roles page:- Admin (blue) has every permission. Manages projects, teams, users, billing, and tenancy settings.
- Team Leader (purple) can manage projects assigned to their teams and invite users into those teams.
- Developer (green) can spin up dryruns, install Magento extensions, and download Docker packages.
- Tester (orange) is read-only on most surfaces but can run SWAT reports and view dryrun status.
User Alerts cross-reference
The left-rail User Alerts menu item (separate from this page) is the per-user notification settings surface. Each user controls their own User Alerts: which dryrun events trigger an email, whether they want a daily digest, whether to receive Slack pings on SWAT report ready, and so on. User Alerts are scoped to the viewing user (they cannot be edited by an admin on someone else’s behalf). The Project Users page is the right place to grant access; User Alerts is the right place for the user themselves to tune notifications.Audit logs
Every user-management action is recorded in the platform-level audit log:- User created (by, when, role granted).
- Role changed (from, to, by, when).
- User deleted (by, when).
- Approval toggled.
- Team membership changed.
Cross-links
- Roles, the four roles and their default permissions.
- Permissions, the granular permission grid.
- Teams, the team model that gates project access.
- Project Overview, Cloud Users tab, how to mirror Adobe-side users into DryRunPro.
- Add Project, where you encounter the deploy-bot user (a special “user” that DryRunPro itself uses).
Frequently asked questions
What is the difference between a Project User and a Cloud User? A Project User is a DryRunPro tenancy user with their own DryRunPro login. A Cloud User is a user on the Adobe-side of an Adobe Commerce Cloud project, mirrored read-only into the Project Overview. Cloud Users become Project Users only when you explicitly click Add on their row. The user verified their email but cannot sign in. Check the Approved checkbox in their Edit dialog. Some tenancies require admin approval as a second step. If Approved is off, the user is verified but not yet allowed to sign in. Can I invite a user with multiple roles? DryRunPro uses single-role assignment per user. The role determines the baseline permissions. To grant additional capabilities, use Permissions to add per-permission overrides on top of the role. What happens to dryruns owned by a deleted user? They are reassigned to the deleting admin. The dryruns themselves keep running. Reassignment changes the Created by field on subsequent audit entries. Can I bulk import users from CSV? Not from this UI. The DryRunPro API supports a bulk-create endpoint; ask your tenancy admin or your DryRunPro account manager to script a bulk import for you. A user shows verified but Approved is unticked. They want to sign in. What is the right next step? Click Edit on their row, tick Approved, click Save. The user can sign in immediately. If you want to require approval on every new user, leave the tenancy default (off) for the Auto-approve setting. Can a Tester role spin up dryruns? By default, no. Testers are read-only. To grant a tester the right to spin up dryruns, add theadobe_staging_create permission to their user via Permissions, or change their role to Developer.
How do I bulk-delete inactive users?
Sort the table by Email verified at descending, untick Select all, hand-pick the rows, then click Delete selected. There is no automatic “delete users with no activity in 90 days” sweep yet.