Onboarding a batch of people usually means clicking through the Add User form once per person, then going back to fix everyone’s role and profile fields. By the tenth row you have lost the thread. This hands the typing to the agent and keeps every account it opens under your eye.
I'm going to paste a spreadsheet of people who need accounts on this site.Change nothing until I approve the plan.
First, parse what I paste into a clean table: one row per person, with thename, email, the role I asked for in the [Role] column, and any extra fieldsI mapped like [company] or [job title]. Show me that table and flag anythingthat looks off, a missing email or a duplicate, before you create anyone.
Once I say go, create the accounts a few at a time. Every new account startson the site's default role, so nobody lands with more access than that. Forthe people I marked for a higher role, raise them in a separate step that Iapprove, and never touch the last administrator. Then write the extra profilefields as user meta.
When you're done, give me back the full list: who you created, their finalrole, and anything you skipped.Why this is safe to run
The first pass is all parsing and shows you a table, so you see exactly who would be created before a single account exists. Then the creating and the role-raising are two different abilities with two different switches. Creating a user always uses the site default role, so even if your spreadsheet says “administrator” in a column, the account does not come out as one. Promoting someone to a higher role is a second, promote-gated step you approve per person, and the plugin will not let it demote the last administrator. Every account and every role change is checked against the capability of the user you bound the agent to, and each one lands in the Activity Log.
Already connected? You do not have to paste this at all. Ask your agent for the “import users from a spreadsheet” recipe, hand it your sheet, and it runs the same approve-first flow on your own site.