Skip to content

Managing users, roles, site access

Roles and site memberships are global by default — a role change doesn't reach an already-signed-in user until their access token refreshes.

A user has one role, and it holds across the whole install — a siteAdmin on one site is a siteAdmin on all of them. What you configure per user is narrower than a role: an optional list of the sites they belong to, layered on top of the role they already have. The ladder those roles sit on, and what each rung can reach, is covered on Roles and the capability matrix; this page is about who can act on whom, and when it takes effect.

Nothing narrows a role until you tell it to

A user with no site memberships set — the default for everyone on a single-site install, and the default for anyone you haven't explicitly scoped — is unrestricted: their one role applies to every site. Give that user real memberships and their access narrows to exactly those sites, with nothing else to turn on. A separate setting changes only what a zero-membership user gets: left off, no memberships means unrestricted everywhere; switched on, no memberships means denied everywhere until you add one. A super admin passes either way, memberships or not.

Who can promote or reset whom

Every grant here is capped by what the acting admin already holds. Creating a user, or raising someone's role on a save, requires the admin to already be at least that role — a site admin can create users and set roles up through site admin, never higher; only a super admin can make another super admin. Directly setting someone else's password takes one rank above theirs, not merely equal, so a site admin can reset an author's or an editor's password but not a fellow site admin's. What a site admin can still do to a peer is force the reset flag rather than the password itself — that's an equal-rank action, and only the peer clears it by changing their own password. See Passwords: change, admin reset, forced-reset lock for what the flag actually does to the account.

Editors can pick users without listing them

Groups are a second, independent lever on top of role and site access — see Managing groups for what a group actually changes about what someone can do.