Users pending suspension
Users pending suspension
When a user is no longer found in your MIS import, they are flagged for suspension rather than suspended straight away. The dashboard shows these users in a Users pending suspension panel so you can review them — it's a scheduled administrative event, not an error.
The panel is collapsed by default, showing the count and when the first is due; click the header to expand it. Once open you can search by name or username (in MAT overview, also by school) and page through a long list. In MAT overview the panel spans every school you administer, with the school shown per row.
When they're suspended
A flagged user is suspended automatically after a 24-hour grace period, at the next scheduled run (weekdays at 15:00). The list shows, per user:
- when it will happen — both as a relative time ("in about 18 hours") and an approximate time ("around Tue 2 Jul, 15:00").
The time is shown as around / at the next scheduled run because suspension happens on a schedule, not at an exact minute.
The list shows exactly the users the scheduled job will suspend (flagged, and not already protected or suspended).
Suspend a user immediately
To override the wait:
- On the dashboard, find the user in Users pending suspension.
- Select Suspend now and confirm.
This suspends the user immediately — the same outcome as the scheduled run, just now: their status becomes Suspended, they're removed from groups, and the suspension is pushed to connected platforms (Google / Entra) on the priority queue. The user then drops off the pending list.
Track the platform outcome in the Logs area. The action is recorded against the user, attributed to you.
Suspend several — or everyone — at once
Expand the panel and use the checkboxes:
- Tick individual users, or use Select all on this page. When more match than fit on one page, a banner offers Select all N matching — this selects every pending user across all pages (respecting any search you've typed).
- Suspend selected (n) suspends just the ones you ticked. When you've selected everyone matching, the button becomes Suspend all N now and asks you to type SUSPEND to confirm — because it cuts access for the whole list at once. In MAT overview the confirmation tells you how many schools it spans; if a search is active, it confirms you're suspending only the users that match your search, not every pending user.
Suspension is immediate and pushed to connected platforms on the priority queue, exactly like Suspend now. If some can't be suspended (already suspended, protected, or changed since the page loaded) they're skipped and named in the result — nothing fails silently. Suspended users can be made active again later from Users.
Troubleshooting: a user was suspended and I don't know why
- Check Recent activity and Logs first, not the Admin audit trail. A suspension — whether triggered by Suspend now, a bulk suspend from this panel, or the scheduled job — is recorded in the Recent activity feed and the Logs area, attributed to the admin who did it (or told as a two-step story — "marked for suspension, then suspended by the end-of-term process" — when it happened automatically). The Admin audit trail is scoped to settings changes, not individual user actions like this, so it won't show the suspension itself.
- Check whether they dropped out of the MIS import. This is the automatic path described above: a user no longer listed in your MIS is flagged pending, then suspended after the grace period at the next scheduled run. Recent activity shows this as the "marked for suspension, then suspended" story with both dates.
- Check bulk-action history. If several users were suspended together, look in Logs/Recent activity for a bulk suspension entry — it names the acting admin and how many users were included.
- Check the Admin audit trail for a setting change that could explain it indirectly — for example, if MIS sync was turned off and back on, or the provisioning window/final provision date changed, that can produce a wave of leavers. The audit trail records exactly who changed which setting and when.