Skip to content
plugboard.appRequest a demo

Running the desk

Directory accounts

Searching accounts across every directory connection is the Directory accounts tab of People, at /people?view=accounts, and a person’s live account is on the Account & groups tab of their page. /directory links, including those on tickets, open the Directory accounts tab with their search and ticket. This page is the reference for what each provider supports and what each action needs.

The Account & groups tab on a person’s page needs module.directory, identity.view and an enabled, configured directory connector. Provider data is fetched live and is not saved as an identity inventory in Plugboard. Unavailable data is labelled; the pane does not substitute demonstration records. See Microsoft app registrations for background authentication and customer consent; Plugboard SSO is a separate setup.

Select the named directory instance before searching or opening an account. The person identity pane also offers a source selector, and confirmations name the selected source. Switching sources clears the previous account and actions.

For campus-scoped access, a district administrator with directory.manage must confirm the provider account against the local person. The current campus coverage and linked provider ID are checked again when the account is used; an email address alone does not establish access. Account links do not merge people or configure sign-in. Unlinking and reconciliation remain separate work.

When multiple directories are configured, a provider sign-out does not infer which local Plugboard login to revoke by email. The result identifies when local session revocation was skipped. Handle local sessions separately.

These source controls do not change the live and demonstration boundaries below. See multiple instances.

CapabilityMicrosoft EntraGoogle WorkspaceActive Directory
Account state, sign-in history, authentication postureSupported, subject to API permissionsSupported, with Google-specific detailAccount state only: enabled, locked out, last password change, direct groups and administrator roles
Conditional Access policiesSupportedUnsupportedUnsupported
Licence assignments and waste reportsSupportedSupported, subject to available licensing APIsUnsupported
Reset registered MFA methodsSupportedWith account recovery on: 2-Step Verification off, or backup codesUnsupported
Enable / disable accountSupportedSupportedSupported
Revoke sessionsSupportedSupportedUnsupported
Assign / remove licenceSupportedUnsupportedUnsupported
Reset passwordSupportedWith account recovery onWith account recovery on
UnlockNot offeredNot offeredWith account recovery on
Direct Full Access / delegation revocationOpt-in; live Send As grants blockedUnsupportedUnsupported

Okta, JumpCloud and Cisco Duo connections offer unlock and resets too. See account recovery for what each provider does and the checks every reset makes.

Google authentication posture is not an Entra-style list of registered methods, and Google licence assignment counts are not purchased-seat entitlements. See software contracts for the commercial register.

Live identity writes ask for a typed account confirmation, a reason and step-up authentication. Each action requires its own permission, and its intent is audited before the provider call. A timeout can leave the external outcome uncertain: verify the provider before retrying. These privileged writes are not available through Ask, MCP or the public REST action catalogue.

PermissionAllows
identity.viewAccount state and authentication posture
identity.signins.view / identity.policy.viewSign-in history / Conditional Access policies
identity.mfa.resetReset registered MFA methods
identity.account.manage / identity.account.enableDisable accounts / additional permission to re-enable
identity.session.revokeRevoke sessions
identity.license.manageAssign or remove a licence
identity.password.resetReset a password
identity.mailbox.delegateRevoke Full Access or Send As; Send As grants are blocked for everyone
identity.mailbox.fullaccessAdditional permission to grant Full Access
identity.tap.issueIssue a Temporary Access Pass

The Exchange guide describes the five-command role, corrected Full Access pilot and two failed Send As boundary tests. Full Access grants and revocations are off until delegation is enabled on the connector, after the environment checks that guide describes; Send As grants remain blocked.

In the Directory accounts tab of People, a live Entra account’s sign-in, password reset and licence changes use the guarded identity.* actions above: typed confirmation, a reason and fresh authentication. Every other account uses the older directory.* operations, governed by directory.view and directory.manage. Those operations are demo fixtures only. They refuse when demo mode is off, and configuring live credentials does not make them live.

Inbox delegation in the Directory accounts tab works only on the demo directory. For a live account the delegates are listed read-only; manage delegation from the person’s Account & groups tab.

An action in the Directory accounts tab is recorded to a ticket, drafted from Ticket for these changes or linked automatically when you arrived from a ticket. A demo action logged to a ticket is marked as demo and must not be taken as evidence of a live provider change. Live actions record the confirmed target, technician and reason in the audit log.

demoMode defaults to false. Enabling it permits the demo fixture workflow and makes the live identity pane and writes refuse. It never fabricates live identity data. directory.view and directory.manage govern the Directory accounts tab and its fixture operations; they do not grant the live identity permissions listed above. A demo directory says so at the top of the Directory accounts tab.

The person-page reset is live on Entra, and on Active Directory, Google Workspace, Okta and JumpCloud once Allow account recovery is on for the connection. See account recovery. The separate LDAP kiosk flow can reset a person’s own directory password after its verification workflow. Neither makes the legacy directory.resetPassword operation in the Directory accounts tab live.

Identity reads remain live, while action audit metadata persists: who requested the action, its target, reason and recorded outcome. Passwords and certificate material are not included in that audit record.