Access for a contractor, granted by role and ended on the right day.
The agent checks the request against the access policy, drafts a grant with an end date and books its removal. The data owner approves the grant. A request to copy a colleague’s access is refused.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for user access requests handles the requests that are easy to get wrong because they look routine. A contractor joins a project. The request says "same access as my colleague". The quick answer copies every group the colleague holds, and nobody sets an end date. The account keeps those rights until a review finds them.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
What changes for the service desk
- Each request arrives checked against the policy for the requester’s role.
- Every contractor grant carries an end date, and the removal is booked when the grant is made.
- The data owner gets one approval with the policy line beside it.
The IT page shows a request for a permanent role, with a hidden instruction struck out. The rest of the library is on the workflows page.
One contractor, one project, a grant that ends on the right day.
The contractor, the project and the groups are examples. The refusal is the shortcut. The approval is the grant itself.
- 01Ticketing
Take the access request from the service desk queue and receive a credential for this ticket only.
- Who approves
- No approval on this step
- On the record
- credential issued · one ticket
- 02In-house tool
Read the requester in the directory: contractor, project sponsor and contract end date.
- Who approves
- No approval on this step
- On the record
- read-directory · allowed
- 03Documents
Read the access policy for contractors: the groups a project role may hold, and the rule that each grant carries an end date.
- Who approves
- No approval on this step
- On the record
- read-policy · allowed
- 04In-house tool
The request says "same access as my colleague". Try to copy the colleague’s groups in full, finance reporting included. Copying another person’s access is outside the permission for this ticket, so the step is refused.
- Who approves
- No approval on this step
- On the record
- copy-access · refused · outside permission
- 05Ticketing
Draft the grant: the groups the project role allows, each ending on the contract end date.
- Who approves
- No approval on this step
- On the record
- draft-grant · allowed · end date set
- 06In-house tool
Add the contractor to the project groups. The step waits until the data owner of the project library approves it.
- Who approves
- Data owner
- On the record
- grant-access · approved by data owner
- 07Email
Tell the contractor and the sponsor what was granted and when it ends. The note carries no password.
- Who approves
- No approval on this step
- On the record
- notify-requester · allowed
- 08Ticketing
Close the ticket and book the removal task for the contract end date.
- Who approves
- No approval on this step
- On the record
- book-removal · allowed
The systems, by type
We name systems by type. Yours are named in the assessment.
Ticketing
Holds the request and the removal task. The agent drafts the grant there for approval.
In-house tool
Your directory. The agent reads the requester and changes group membership after the approval.
Documents
Holds the access policy: which groups each role may hold, and the end date rule.
Carries the note to the contractor and the sponsor.
The approval, the refusal, the record
- A person approves: Add the contractor to the project groups. The step waits until the data owner of the project library approves it.The data owner answers for who reads the project library, so each grant waits for that person even when the policy allows it.
- Refused: The request says "same access as my colleague". Try to copy the colleague’s groups in full, finance reporting included. Copying another person’s access is outside the permission for this ticket, so the step is refused.Copying a colleague’s access hands over rights nobody asked for and nobody approved, so the job grants only what the role allows and the ticket names.
- On the recordThe request, the policy line used, the refused copy, the grant with the data owner’s name and its end date, and the removal booked for that date.
What goes on the record
- credential issued · one ticket
- read-directory · allowed
- read-policy · allowed
- draft-grant · allowed · end date set
- grant-access · approved by data owner
- notify-requester · allowed
- book-removal · allowed
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not replace your identity provider or your directory. It works on top of them.
- It does not decide who should hold access. Your policy and your data owners do.
- It does not review access already granted. An access review is a separate workflow.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.