For site administrators
Everything here can also be done in the administration. The console is faster when you work on many accounts, when you are on the server anyway, or when the administration is out of reach.
What you'll have at the end
A clear idea of when to use the console, and the handful of commands you need every week.
When the console helps
| Situation | Command |
|---|---|
| Nobody can sign in to the administration | Recover a locked-out administrator |
| Someone leaves today | Offboard someone who leaves |
| Hundreds of registrations wait | Approve a backlog of registrations |
| A list of new members arrives as a spreadsheet | Bulk-import members from CSV |
| You need to know who has which role | exp:user:roles list <user> (Groups and roles) |
| Someone asks what happened to their account | exp:user:audit <user> (Audit and hygiene) |
The rules that keep you safe
- Nothing changes without
--apply. Run every command once without it, read the output, then add--apply. - Protected accounts are refused: the anonymous user, the
UserCreatorIDuser,admin, yourself and the last enabled administrator. - A bulk change needs
--confirmwith the count of its dry run. - Every change is in the user audit log, with your name when you pass
--as=<your login>.
Note: Pass --as=<your login> for changes you make yourself. Without it, the audit records the user of
[UserSettings] UserCreatorID.
A weekly routine
- Run
./console exp:user:hygiene. - Run
./console exp:user:pendingand decide each waiting registration. - Run
./console exp:user:list --state=lockedand unlock the people you know. - Disable the accounts that have not signed in for a year, after a dry run:
./console exp:user:bulk disable --state=inactive --days=365.
Related pages
- User management from the console
- Check user accounts: the same review in the administration.