# Managing users, roles, site access

URL: https://kywi-docs-production.up.railway.app/governing/managing-users-roles-site-access
Type: docPage

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](/governing/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](/governing/passwords-change-admin-reset-forced-reset-lock/) for what the flag actually does to the account.

## Group roles count, and only users on a shared site are in reach

A user whose own role is reader takes the highest default role among their groups, up to site admin. The Users list shows that effective role — for example “editor (from group Editors)” — and giving the user any own role but reader overrides it. The rank rules above compare against the effective role, not the stored one. Editing, resetting or deleting another user also needs the admin to share a site with them, by the membership rules above; with strict membership on, a user with no memberships is out of reach of everyone but a super admin. Setting a group’s default role is covered on [Managing groups](/governing/managing-groups/).

## A role change doesn't reach an open session right away

Role, group and site-membership all get baked into a user's access token when they sign in, not read fresh on every request (API-key requests are the exception: they read the owner's role and memberships each time). Promoting, demoting or reassigning someone doesn't take effect for them until that token refreshes — on the order of fifteen minutes, not your next click. Expect a short window where whoever you just changed is still operating under their old role, if they're already signed in.

## Editors can pick users without listing them

## A narrower user list for editors

The users list itself is for site admins. An editor who needs to choose people — the Expiration Notify picker on a page's Publishing tab is the one place today — gets a narrower view: `GET /users/options` returns only each person's id, name and email, for the active users with access to the site in question, and only to editors and above with access to that site. Anyone without access to the site is neither offered nor accepted as a new recipient.

Groups are a second, independent lever on top of role and site access — see [Managing groups](/governing/managing-groups/) for what a group actually changes about what someone can do.
