Manage a user and inspect their access

Change a plan, grant site admin and see what the access evaluator says for one person.

In short

Users lists every account: its plan, what it holds and who administers the site. "Open" shows what the access evaluator says for one person, and the support actions handle an account's standing - suspend, restore, sign out or reset two-step sign-in.

Before you start

• Who: only a site admin. The Admin console is in the avatar menu of a site admin and nowhere else. You cannot remove your own site-admin role or suspend your own account.
• Plan: none.
• First: inspect first when someone cannot open something.

Find a user and change their plan

1. Open "Admin console" › "Users".
2. Search by name or email, filter by "Plan", "Status", "Site admins only" and "Signed in", or sort by "Name", "Newest first" or "Last sign-in".
3. Change the plan from the row's dropdown. It saves at once.
4. To make someone a site admin, turn on their "Site admin" switch, write "Why" and press "Make site admin". When another site admin exists, they approve it first.

Approve or decline a site-admin request

1. Open "Admin console" › "Users". Requests show above the list, under "Waiting for a second administrator"; nothing shows while none waits.
2. Read who asks to make whom a site administrator, the reason given and "Open until". A request waits 48 hours.
3. Press "Approve" or "Decline". The request asks first in its place; press "Approve" or "Decline" again. Approving can ask for your password again ("Confirm it is you").

Result: "{name} is now a site administrator.", or "Declined. {name} stays as they are." The reason is kept with the change under your name.

• The one who asked and the person it is for see the request but cannot decide it: "Another administrator decides this - not the one who asked, and not the person it is for."
• Declining changes nothing for them. Whoever asked can ask again.
• "This request was already decided, or its time ran out.": someone decided it first or its 48 hours passed. Ask again if it is still needed.

Inspect one user

1. Press "Open" on the row.
2. Read their plan and roles at the top. Every part below starts closed and says what it holds, such as "3 near, 0 reached".
3. Open Limits for what is near or at its end, with the plan's value, any temporary limit or override, what applies and what is used. "Find a limit" searches all of them.
4. Add, change or remove Overrides - limits raised for this person's workspace alone.
5. Open Effective feature access for what is Blocked, with the code that explains why, and what is allowed folded under one line. Resource permissions is the last part.

Use it before changing anything When someone cannot open something, inspect them first. The Blocked code tells you whether to change the feature's audience, the plan or a resource grant.

Account standing and support

• Suspend: they cannot sign in, every session ends, their scheduled work stops and their public listings are hidden - until you restore the account or an appeal succeeds. They are told why and can appeal.
• Restore: they can sign in again, their work runs again, and they get an email.
• Sign out everywhere, Reset two-step sign-in (emails them a reset link) and Send a new confirmation link.
• Support history lists what was done to the account.

Good to know

• The site-admin switch asks you first, and you cannot remove your own.
• Deciding what someone else may see never uses your site-admin role: inspect shows what they are allowed, not what you are.

If something goes wrong

• "You cannot suspend your own account."
• "This account is already suspended." / "This account is not suspended.": refresh the row.
• "Two-step sign-in is not on for this account, so there is nothing to reset."
• "The account's email address is not confirmed, so a link there proves nothing. Ask the person to confirm it first."

Related

• /help/settings/admin-console
• /help/settings/admin-organizations
• /help/settings/admin-feature-access
• /help/settings/admin-plan-limits