An AI identity and access management coordinator is an AI clone that prepares joiner, mover and leaver work. Dorian builds access requests, collects approvals, assembles device checklists and preps access reviews in your identity, HR and ticketing tools. He never approves his own work or changes access alone, and reports day-one readiness, deprovisioning time and orphaned accounts to your dashboard.
What a identity and access coordinator clone actually does between 8 and 5, and what it's like to work with one.
Dorian, the new contractor needs prod database access today. Can you just add her to the admin group?
I can't add her myself, and admin is broader than her ticket needs. I've drafted a request for read-only access to the two schemas in her statement of work, with a 30-day expiry, and sent it to the data owner.
What if she needs write access later?
Then she files a new request with the reason and the owner approves it. I set a reminder five days before expiry so the owner can extend or let it lapse on purpose.
A clone is hired for areas of responsibility, not prompts. These are Dorian's, with the numbers it reports.
Builds day-one access and device packages from the role profile and routes them to the right approvers before the start date.
Compares old and new role access on the day of a change and prepares the removal list so rights don't pile up.
Prepares the deprovisioning checklist the moment HR confirms a departure, covering accounts, devices, shared files and tokens.
Assembles quarterly review packets for system owners, highlighting exceptions without an owner, an approver or an expiry date.
Dashboard figures are illustrative.
Dorian connects to the apps your team already runs, with object-level permissions you set.
The capabilities that let Dorian do this role. Ask for any of them in plain words.
An AI identity and access management coordinator is AI that prepares the paperwork and checks behind joiner, mover and leaver changes, device assignments and access reviews. On Clone, it is a clone hired into that role with its own permissions. It prepares and routes requests, while approvers and system owners decide and execute.
No. Dorian does not self-approve access or independently change identities, credentials, devices or security controls. He prepares each change, sends it to the right approver and verifies afterward that what was approved is what got applied. Separation of duties is part of how he is set up.
It replaces spreadsheet chasing between HR, managers, IT and security. Dorian watches for starts, moves and exits, builds the access lists and keeps reviews on schedule. Your IAM engineers keep ownership of policy and execution, with far less manual tracking.
Dorian works with Okta for identity, Workday for HR events, ServiceNow or Jira for requests, Microsoft 365 or Google Workspace for accounts and Google Sheets for review packets. He updates owners in Slack. Each connection is limited to the scope you approve.
Each clone is default-deny, with object-level permissions you set. Most teams give Dorian read access to identity data plus rights to draft tickets. Every action he takes is logged, so auditors can see exactly what he prepared and who approved it.
Every Clone plan starts with a free trial. Paid plans are a flat monthly price with credits included, so you are not charged per identity or per device. Enterprise plans start at $2,500 per month through Book a Demo. See clone.org/#pricing.
Updated October 2026