User management — every person AccessPoint knows, directory status, role assignment, deactivation and reassigning the work of people who have left; in Hosted AccessPoint, Members — invitations, Ask to join and signing out
Last updated: November 14, 2026 by Steve
Manage Users
The Manage Users screen lets administrators add users from the organization's Microsoft Entra ID directory, assign them roles in AccessPoint, and look after people who have left. No separate usernames or passwords are needed — users sign in with their existing Microsoft 365 accounts. It requires the permission to manage users.
Hosted AccessPoint. The panel is called Members (Settings → Users & access → Members) and has no directory to search: people join by invitation. See Members (Hosted AccessPoint) below. Directory reconciliation and group-based roles are AccessPoint for Microsoft 365 features.

Who Is in the List
Manage Users lists every person AccessPoint knows — everyone who has ever signed in and everyone provisioned by a role grant — not only people holding a standing role. A custodian with three open assignments and no role is in the list. Each row shows:
- the person's name and a directory status pill: Active, Disabled, Deleted, Not found, or Unknown when the directory has not been checked for them yet (hover it for when the check ran);
- their email, their standing role chips (or No standing roles), and their last sign-in.
Search filters by name or email. Show inactive users adds deactivated accounts to the list; they are hidden by default. The row menu offers Manage roles, Deactivate or Reactivate, and Reassign or release work….
Adding a User
- Click Add user. This grants a first role to someone who has not signed in yet, which is what provisions them.
- Search for the person by name or email address. The search queries your organization's Entra ID directory.
- Select the user from the results.
- Assign one or more roles (see role descriptions below).
- Click Save.

Changing Roles
To change a user's roles, find them in the user list, open the row menu and choose Manage roles, adjust their role assignments, and save. Manage roles also shows roles the person holds via group membership — each role via the group, with any binding expiry — headed by the state of the last check. That is the answer to "why can this person see that?". See Roles and Permissions.
Roles
The roles you assign here are your tenant's standing roles. Administrator is the only built-in role — it always resolves to every permission and can never be removed from the last active administrator. Every other standing role is tenant-defined, typically seeded from a jurisdiction pack — the pack-shipped Request Coordinator, for example, is the de-facto access-and-privacy-officer role — and shaped on the Roles and Permissions page. Most offices define roles matching these archetypes:
| Role | Description | Sees PII |
|---|---|---|
| Administrator (built-in) | Configure system settings, manage users, and access all administrative functions | Yes |
| Request Coordinator (pack-seeded tenant role) | Manage the full request lifecycle — create, assign, extend, close, and respond to requests | Yes |
| Custodian | Collect and submit documents for assigned work. Cannot see requestor personal information | No |
| Contributor | Complete tasks within assignments. Cannot see requestor personal information | No |
| Reviewer | Review requests and flag/resolve redaction concerns. Cannot see requestor personal information | No |
| Reader | Read-only access to associated requests and shared documents. Cannot see requestor personal information | No |
Custodian, Contributor, Reviewer, Reader, and Advisor are relationship roles. They are conferred automatically by the work you assign — a custodian assignment, a contributor task, a review, an advisor/reader membership — scoped to that specific record, and they cannot be assigned on this screen. You don't hand these out here; they follow the work. See Roles and Permissions for the full assigned-versus-relationship split.
Privacy Officer
The Universal baseline pack also ships a Privacy Officer role. It can view and manage the privacy program and follow assessments, audits, risks, incidents and complaints. Attesting the privacy program is deliberately left out of it; grant that to the accountable senior official.
PII Visibility
Requestor personally identifiable information (PII) is visible only to roles holding the view-requestor-PII permission (Administrator and coordinator-style roles). Custodians, Contributors, Reviewers, Readers, and Advisors never see it — the server strips it from every response.
Multiple Roles and Expiry
A user can hold more than one role. Permissions are additive — a user with two roles receives the combined permissions of both. A role assignment can also carry an optional expiry date: once it passes, the role confers nothing. That is useful for temporary coverage, and for contractors and client users whose access should lapse on a known date.
When Someone Leaves
People leave. In government their Microsoft Entra ID account is often disabled for months before it is deleted, and from inside an application a disabled account looks exactly like a live one unless the application asks. AccessPoint asks, stops offering departed people, and helps you move the work they still hold.
Deactivating a user
Deactivate marks the person inactive in AccessPoint. They disappear from every AccessPoint-sourced picker and list (the Assigned-to and senior-official dropdowns, approver pickers, person-type custom fields, reassignment targets), so nobody can hand them new work, and they appear in the Departed users report. You may record a reason; the row then shows the date and the reason.
Deactivation is deliberately not an access block. Microsoft Entra ID authenticates and AccessPoint authorizes, so an inactive person whose account still exists and who still holds a role can still open the app, and a successful sign-in reactivates them automatically. If someone must genuinely lose access, disable or delete their account in Entra ID and remove their roles here. Deactivation keeps everything: history, comments, audit entries and the work they hold are untouched, and nothing is ever deleted.
Two guards apply: you cannot deactivate your own account, and you cannot deactivate the only active Administrator (a group-derived Administrator does not count). Reactivate reverses a deactivation.
How departed users are detected
The Directory reconciliation strip above the list shows what AccessPoint can see, when it last checked, and how many accounts are disabled, deleted, not found and inactive, plus users with open work and no sign-in for 90 days. Three feeds keep it current:
- The nightly service check. The service asks Entra ID about every AccessPoint user using its own identity. Accounts in the directory recycle bin become Deleted, accounts Entra ID no longer resolves become Not found, accounts with sign-in blocked become Disabled, and everyone else is Active. Disabled accounts need the
User.Read.Allpermission, which the Finish Setup page grants by default with an opt-out. - The in-app check. Run directory check now performs the same check from your own session. On tenants that opted out of
User.Read.All, it also runs automatically once a day the first time someone holding user.manage opens the app. - Sign-in. Every successful sign-in records the account as Active.
When a check finds an account Disabled, Deleted or Not found, the person is deactivated automatically with that reason recorded. If the account comes back, the next check reactivates them, but only when the directory caused the deactivation; a deactivation an administrator made by hand is never undone by the directory. A partner-organization guest whose home account is disabled still looks enabled in your directory, so the no recent sign-in with open work count is the signal that catches them.
The whole mechanism sits behind Settings > Features > Users and directory > Reconcile users with the directory (on by default). Turning it off stops the nightly and automatic daily checks; Run directory check now still works.
Reassign or release work
When someone has left, their open work needs a new owner. Reassign or release work… (the row menu, or Reassign or release on a Departed users report row) opens a dialog listing everything the person still holds, grouped by kind, with a count per group and Show items to expand the rows. You cannot run it on your own account; another administrator must.
- Pick a default target — an active user who receives every group you set to Reassign or Transfer without naming a target of its own.
- Choose one action per group. Where a column can be blank, Clear is pre-selected. Where it cannot — the access officer of a request, custodian assignments, contributor tasks and similar — Reassign is pre-selected and you must supply a target. Work items may instead be Cancelled; a request can never be cancelled this way. Leave as is skips a group. The person who takes over senior official on cases, or the letters awaiting sign-off, must hold Act as senior official — a held letter can only be signed by the case's senior official or someone who holds that permission. Otherwise the dialog says so and nothing runs: choose someone else, Clear (the letters then wait for anyone who can act as senior official) or Leave as is.
- Decide about personal items. Saved views can be shared with everyone, transferred, deleted or kept; saved reports can be transferred, deleted or kept.
- Note the Processed automatically section: standing roles expire, case access grants are revoked, delegations given and received end, document check-outs are released, and subscriptions and followed threads are removed. These are listed for transparency, not choice.
- Tick Also deactivate this user (pre-selected for an active user), optionally record a reason, and choose Review and run. The confirmation lists exactly what will happen.
- Read the results. A table shows, per group, the action applied, how many rows were processed, skipped (and why) and failed. Each group runs in its own transaction, so a failure in one never undoes the others; fix the cause and run the dialog again for what remains. If the person is the only active Administrator, their Administrator grant is kept and the deactivation is refused; grant Administrator to someone else first.
Every changed record gets an audit entry with the reason Offboarding, mirrored into the audit ledger. The leaver's history is never rewritten and their user record is never deleted.
A daily notice
After the nightly check, if anyone the report would list still holds open work, every holder of user.manage receives one Departed users notice that day, which opens Manage users. There is none when there is nothing to do.
Members (Hosted AccessPoint)
In Hosted AccessPoint, Settings → Users & access → Members replaces the directory's Add user. Members are unlimited on every plan. None of this is available in Lab mode.
Inviting people
- Select Invite people and enter one or more e-mail addresses.
- Optionally choose the roles they get on joining.
- Send. Each address receives an e-mail with a link to join the organization. The link is valid for 14 days, and only for the address it was sent to.
Pending invitations lists who has not joined yet — address, roles, expiry and who invited them — with Resend (a fresh link) and Revoke (the link stops working; you are asked first). Invitations count toward the organization's e-mail limit.
Removing a member
Each member's row offers Remove from organization: the person can no longer open the organization, their work and history stay, and they can be invited again. Their roles, their access to individual cases and any delegations to or from them end with the removal, and so does their open case work: the case roles they hold are cleared and their open assignments and tasks are cancelled — cancelling an assignment also cancels every open task under it, including tasks assigned to other contributors — and the requests where they are the access officer pass to you. If they are invited again, they hold only the roles the new invitation (or the approved request to join) gives them. You cannot remove yourself, and the organization's last administrator cannot be removed until someone else holds the Administrator role. The Departed members report lists members removed from the organization and members who have not signed in for 90 days while holding open work.
Colleagues from your Microsoft organization (Ask to join)
When someone signs up with a work account of your organization's Microsoft organization, the Create organization page tells them People from your organization already use AccessPoint: . with Ask to join — showing only your organization's name, only to people of that Microsoft organization, and only when your Who can join setting would admit them. Colleagues can find this organization (on by default) turns this off.
- Each request appears under Requests to join — name, address and when they asked — and the administrators get a notice in AccessPoint and an e-mail.
- Approve sends them the usual invitation (choose the role it gives, or none yet); Decline closes the request.
- A request not decided in 30 days expires.
An organization created with a personal Microsoft account has no Microsoft organization, so nobody can find it this way.
Signing out
For security, Hosted AccessPoint signs a member out after a time without activity, and after a set time whatever they are doing. On the Members panel, administrators choose both, within what the service allows:
- Sign out after inactivity — 15, 30, 60, 120 or 240 minutes.
- Sign out after at most — 1, 2, 4, 8, 12 or 24 hours.
Each list offers only the values the service allows, so you can make either limit shorter, never longer; Use the service default (…) names what the service allows and applies until you choose. Select Save. A change applies to everyone in the organization within a minute and is recorded in the audit ledger. Someone who belongs to several organizations has one sign-in, held to the limits of the organization they are working in — so switching to an organization with a shorter limit after a long break signs them out. What members see before they are signed out is described in Getting Started.
In AccessPoint for Microsoft 365, signing in and out is Microsoft 365's, and these settings are not offered.
Related Pages
- Roles and Permissions — building roles, case-matched roles and binding roles to Entra groups.
- Departed Users report — who has left, or looks like it, and what they still hold.
- Features — the directory reconciliation and group-based roles toggles.
- Subscription — plans and allowances in Hosted AccessPoint.
- Your First Day — the welcome a new member sees, and its Invite your team start.