| UPN | Display Name | Status | Risk (click for reasons) | Contract End | AD Expiry | Manager (click to edit) | Last Attested | Actions | |
|---|---|---|---|---|---|---|---|---|---|
| Loading… | |||||||||
The Contractor Module tracks active contractors, monitors their access through continuous manager check-ins, and triggers the standard offboarding pipeline the moment a departure is confirmed. No contractor account is offboarded without explicit manager confirmation.
The module keeps a live roster of active contractors and emails each contractor's manager on a recurring cadence to confirm whether their access is still needed. No contractor is offboarded without explicit manager confirmation (unless a tenant opts into auto-offboard at the contract end date).
How often notices go out. A monthly manager check-in, plus reminders 30 and 7 days before the anchor date (and at the date itself). At most one email per contractor per month.
What factors into risk. The risk score is computed in code (never by AI) from contract timing, the AD account expiry, how recently the manager last attested, the contractor's access footprint (privileged group membership and sign-in dormancy), and any operator-defined AD-group risk ratings — shown as a low / medium / high / critical badge.
Source of truth for dates. The contract end date from the ingested roster is the primary anchor for cadence and offboard timing. If no contract end date is supplied, the AD account expiry is used instead; when both are present they are cross-checked and a mismatch raises risk.
How AD group permissions are factored. Group membership is read from AD by the agent. Holding a privileged or sensitive group raises the score, and operators can assign an explicit risk rating (0-100%) to named AD groups under AI Assistance → AD group risk presets — a contractor in a rated group has their risk raised to at least that rating.
Configure which emails are sent and when. All emails use one-click tokenised buttons — no portal login required for manager responses.
Settings apply to all contractors for this tenant. Changes take effect on the next scheduled sync or heartbeat cycle.
Configure how the platform handles contractor lifecycle events — attestation requirements, auto-offboard behaviour, and HR approval gates.
Customise the subject and body of each email type. Use {{variable}} placeholders — they are replaced at send time.
{{contractor_name}}
{{contractor_upn}}
{{manager_name}}
{{manager_upn}}
{{contract_end}}
{{vendor}}
{{department}}
{{attest_url}}
{{offboard_url}}
[Label] followed by a URL are rendered as styled buttons in the sent email.
Your procurement or vendor management system can drop contractor roster CSVs directly into Azure Blob Storage. The API polls every minute, processes each file, upserts contractor records, and deletes the blob automatically.
contractor-drop{tenant}/{filename}.csv{tenant}/errors/{filename}.csv.txtTrigger a sync from the source of truth or upload a contractor roster CSV directly. The system will upsert records and apply the cadence logic immediately.
offboarding or offboarded status.