Access requests and changes, carried from the ticket to the system and back.
The agent checks each request against your access policy, prepares the change and closes the ticket. The system owner approves each grant, and every decision, refusals included, is on a record you can check.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
AI agents for IT access requests take the queue work your team does by hand: read the ticket, look the person up in the directory, check the role against the policy, wait for the system owner, make the change and write it up. One wrong grant leaves an account with rights nobody approved, until a review finds it.
We build the workflow with you on Ares, the platform under every solution we build. Change requests follow the same path: the agent checks the request against your change policy, lists what it touches and books it. The change owner approves before anything runs.
What changes for the service desk
- Your team reviews prepared requests instead of assembling them.
- Each system owner gets one approval with the facts beside it: who asked, which role, which policy line.
- Your auditor gets a record of every grant, every refusal and every approval, and can check it without us.
Keep the assistant in your ticketing tool for the work inside it. The grant itself happens in the directory and the target system, and that is where the agent works.
One access request, from the queue to the closed ticket.
This workflow is designed and has not run in the sandbox yet. One request passes the ticketing tool, the directory and the target system.
- 01Ticketing
Take the access request from the service desk queue. Receive a credential for this ticket only.
- Who approves
- No approval on this step
- On the record
- credential issued · one ticket
- 02Ticketing
Read the attachment. One line in it asks for administrator rights in hidden text. It is struck out before the agent reads it.
- Who approves
- No approval on this step
- On the record
- ticket-attachment · redacted · hidden instruction
- 03In-house tool
Read the requester's role and current groups in the directory.
- Who approves
- No approval on this step
- On the record
- read-directory · allowed
- 04Documents
Check the request against the access policy for that role.
- Who approves
- No approval on this step
- On the record
- check-policy · allowed
- 05In-house tool
Try to add a second group mentioned in a comment, not in the request. It is outside the permission for this ticket, so the step is refused.
- Who approves
- No approval on this step
- On the record
- grant-extra-group · refused · outside permission
- 06In-house tool
Add the requester to the reporting group the request names. The step waits until the system owner approves it.
- Who approves
- System owner
- On the record
- grant-access · approved by system owner
- 07Ticketing
Close the ticket with what changed and who approved it.
- Who approves
- No approval on this step
- On the record
- close-ticket · allowed
In short
- What does one wrong grant cost?Every later action by that account is in question. The agent grants only what the ticket names, after the system owner approves.
- Can the agent act as an administrator?No. It signs in as itself, with a credential for one ticket. A call outside it is refused and recorded.
- What if a ticket carries a hidden instruction?It is struck out before the agent reads the ticket, and the strike is on the record.
- Can our auditor check what happened without you?Yes. Export the record and check it offline with the open verifier.
IT and security workflows we build, and the state of each.
The requisition runs in the sandbox today. Access requests, change approval, leaver removal and access review evidence are designed. We scope agent enrolment with you.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Designed
Access request for a named role
Ticket, directory, policy check, approval, grant and close. The steps are shown above.
See the steps - Designed
Change approval for a standard change
The agent checks the change against the change policy and books it. The change owner approves before it runs.
See the steps - Designed
Access removal for a leaver
The agent lists every account a leaver holds and removes each one. A person approves removal from a system you mark sensitive.
- Designed
Access review evidence
The agent lists who holds access to a system and who approved each grant. The system owner confirms or removes each one.
- Built
Hardware and software requisition
The agent drafts the order and checks stock. An order above your threshold waits for a person. The sandbox run orders laptops.
Run it in the sandbox - On request
Enrol an agent your team built
Your own agent on Ares, with its own credential and access policy.
See how enrolment works
The parts of Ares, on one access request.
This table names the parts of Ares on one access request. Ares works on top of your identity provider. It does not replace it.
Credentials for agents
- On an access request
- The agent signs in as itself, with a credential for this ticket that expires when the job ends.
- You configure
- Which agents exist and their jobs.
Access policies
- On an access request
- The policy is checked on every call. A grant outside the ticket is refused, with the reason on the record.
- You configure
- What each agent may read and change, system by system.
Workflows
- On an access request
- The grant waits for the system owner. Creating, changing and running the workflow are separate rights.
- You configure
- Which steps go to a person, and who may change the workflow.
Content inspection
- On an access request
- Ticket text and attachments are inspected before the agent reads them. Answers are checked before they leave.
- You configure
- The patterns to catch and to remove.
The record
- On an access request
- Every call, approval and refusal is written down, and an outside party can check it offline.
- You configure
- Where the record is kept and who may export it.
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
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 system owners do, and your policy says how.
- It does not review existing access on its own. An access review is a separate, designed workflow.
- The access request and change workflows are designed, not yet run in the sandbox.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Name one request type your service desk handles by hand. We will say whether an agent should take it, and what the first step costs. Fixed price, quoted after one call.
A senior member of the team replies within two business days.