Skip to content
plugboard.appRequest a demo

Running the desk

Account recovery

When somebody is locked out, has forgotten their password or has lost their phone, the desk can put it right without opening the provider’s own console. Account recovery works on Microsoft Entra ID, Active Directory, Google Workspace, Okta, JumpCloud and Cisco Duo accounts.

There are two places to start:

  • The person page. On the Account & groups tab, each connected account has an Account recovery group with Unlock, Reset password and Reset MFA (Issue bypass codes for Duo).
  • A ticket. The requester card has Help with their account, which lists the requester’s linked accounts with the same actions, and asks how you checked it is them.
ProviderUnlockReset passwordReset MFA
Microsoft Entra IDNot offered: Entra clears its own lockoutsA temporary password, changed at next sign-inClears their registered methods
Active DirectoryClears the lockoutA temporary password, changed at next sign-inNot offered: Active Directory has no MFA
Google WorkspaceNot offered: Google does not lock accountsA temporary password, changed at next sign-inTurns 2-Step Verification off, or issues a fresh set of backup codes
OktaClears the lockoutOkta chooses a temporary password, and their current sessions endResets every factor
JumpCloudClears the lockoutExpires the password, and the person sets a new one through JumpCloudStarts their authenticator enrolment again
Cisco DuoOnly for a user Duo reports as locked outNot offeredOne to three single-use bypass codes, valid for up to eight hours

A temporary password Plugboard makes follows Student account or Staff account in Settings, Passwords & links. Unlock is unavailable while the provider says the account is not locked.

Each Active Directory, Google Workspace, Okta, JumpCloud and Duo connection has Allow account recovery, off until it is turned on in the connection’s settings in Settings, Connectors. While it is off, the person page says “Account recovery is turned off for this connection” and the provider is never asked. Turning it off again takes effect on the next request.

Turning it on needs a whole-school administrator: a role holding every permission, with no campus or desk limit, and confirming it is you. A connector administrator limited to one campus cannot switch it on, because a reset reaches every account in the directory, whichever campus the connection serves.

Entra uses Allow account changes on the Microsoft 365 connection instead.

ActionNeeds
Unlockidentity.account.enable
Reset passwordidentity.password.reset
Reset MFA, issue backup or bypass codesidentity.mfa.reset
Issue a Temporary Access Passidentity.tap.issue

The Account & groups tab and Help with their account also need the Directory module and identity.view. A button appears only for somebody who holds its permission.

Every action asks for the person’s name or sign-in address typed out, a reason of at least 10 characters for the audit log, and confirming it is you.

From the person page, you chose the person, so no check is asked for.

From a ticket, you record how you checked and what you checked it against:

MethodWhen it counts
In personAlways offered
Called back on the number on fileOnly when the requester has a mobile on their record. The dialog shows its last three digits to compare
Vouched for by a colleagueAlways offered
Their signed-in portal request or Their signed-in Teams requestOnly when the requester signed in to the portal (by password, card or single sign-on) or Teams to raise this ticket, and is still this account

Whatever the method, the ticket’s requester must be the person this account is linked to. A ticket typed in at the desk, raised with a typed username, or moved to another requester has no signed-in request. Email, phone and API tickets need one of the other methods.

These are refused on every provider, and each attempt is recorded in the audit log:

  • An account that holds a directory role, such as an Entra role, a Google administrator, an Active Directory administrator group or an Okta, JumpCloud or Duo administrator. When the roles cannot be read, the account is refused too. Reset it in the provider’s own console.
  • Plugboard’s own Active Directory service account.
  • An account that signs in to Plugboard with permissions you do not hold. Staff sign in to Plugboard through the same directory, so resetting that account would be a way to become them. Somebody who holds those permissions can do it.

After an unlock or reset, the person the account is linked to gets an email and a text to their mobile. A staff member’s manager gets an email where the directory names one, which Entra and Google Workspace do; when nobody is told, the audit log says so. A student’s manager is never told. These notices cannot be switched off and are sent straight away, even in quiet hours. None of them carries the password, the codes or your reason.

The mobile comes from Notices on the person’s page, which no roster sync fills in. Somebody with Opted out of texts ticked there gets the email only. When two people share the account’s sign-in name, or the person’s mobile or text setting changed in the week before, the audit log says so and the desk is alerted. A notice that fails to send is recorded in the audit log and never undoes the reset.

A temporary password, Google backup codes and Duo bypass codes are shown once, in the dialog, with Copy and, for somebody with secret.share.create, Make a one-time link. They are not stored anywhere: not in the audit log, the browser or a flow. Closing the dialog clears them, and Done waits until you confirm you have handed them over. JumpCloud shows no password, because the person sets their own.

Each technician can make, in any hour:

Password resets10
MFA resets and code issues, together10
Unlocks20
Temporary Access Passes10

The next one is refused until the hour is out, and an administrator is alerted.

A Temporary Access Pass is a Microsoft Entra sign-in that works once, for eight hours, so a joiner whose account has just been made can sign in and set up their own methods.

A joiner plan issues one only for an account that same plan created, and only to the person’s manager, from the directory, or to the ICT lead for a student. It is shown on screen when the person running the step is that recipient, and emailed to them otherwise. It is never sent to the joiner or written to a ticket.

Issuing one needs identity.tap.issue. No built-in role other than Owner holds it, so grant it to the roles that should issue passes; without it the plan’s pass step is refused. A pass is never issued for an account with a directory role, or for one whose Plugboard user holds permissions you do not.

Unlock their account is a flow step. It runs only after a go-ahead from somebody who holds identity.account.enable, with the same refusals, limits and notices. A flow cannot reset a password or MFA or see a code: those steps hand the work to a technician.

SymptomCause
No Account recovery group on the person pageYou hold none of the three permissions, or the provider offers none of them for this account
“Account recovery is turned off for this connection”Allow account recovery is off for that connection. A connector administrator turns it on
Switching Allow account recovery on is refusedIt needs a whole-school administrator, with no campus or desk limit
“This account holds an administrator role”The account has a directory role or, on Active Directory, is Plugboard’s own service account. Use the provider’s console
“Directory roles could not be checked”Plugboard could not read the account’s roles, so it changes nothing. Restore the connection’s directory read permissions
“This account signs in to Plugboard with permissions you do not hold”Its Plugboard user can do more than you. Ask somebody who holds those permissions
No signed-in request option on a ticketThe requester did not sign in to raise this ticket, or the ticket came by email, phone or the API
Called back says “no mobile on file” and cannot be chosenThe requester has no mobile under Notices
“This ticket was not raised by this account’s owner”The ticket’s requester is not linked to this account. Work from their person page, or a ticket they raised
A reset is refused after several in a rowThe hourly limit. It clears when the hour is out
A joiner’s pass step is refusedThe person running it lacks identity.tap.issue, or the account was not created by that plan