Access reviews
Works the periodic entitlement list so access nobody still needs is released, and every decision is written down.
No ready-made setup for this job yet.
Describe the job in a sentence, the way you would brief a colleague: when it should happen, what to check, and what to hand you. That sentence is the automation.
The job, and what good looks like.
Access reviews tend to start from a spreadsheet nobody updates, so the list of who should have access drifts from the list of who does, and the gap only surfaces when an auditor asks or when someone leaves and the account stays open. This workflow pulls the live entitlements from the identity provider rather than from the previous export, groups them by application and by role so a reviewer sees one decision instead of four hundred rows, and adds the last sign-in date and the manager for each holder. Anything unused for ninety days, or held by someone who has left, is separated out as a removal recommendation with the evidence attached. The campaign then routes to each named reviewer with a deadline, and a removal only happens after a reviewer answers, so nothing is revoked on a hunch. When the cycle closes, the confirmations, the removals and the exceptions are written into one record the compliance file can pull from later. What a human still decides is which access a role genuinely requires, which exceptions are worth keeping, and what happens when a reviewer does not answer before the deadline.
When it is handled
- Every review decision applied, not just noted
- Stale access released within one cycle
- Review evidence attached to the audit record
- Managers asked once, not per system
Works with tools like
- Okta
- Microsoft Entra ID
- Jira Service Management
- Vanta
You stay in charge.
At every step.
It triages and sweeps. People approve every change.
- No change without approval
Blocking, revoking and purging wait for an analyst's OK.
- Every run on the record
What it read, what it did and what it is waiting on, kept for review and audit.
- Scoped per automation
Each automation gets only the access you grant it, and a local model can keep processing on your machine.
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Scripts and scheduled jobs
Precise, repeatable system tasks.
They break on the unexpected, and only their author can read or change them.
Security automation platforms
High-volume response playbooks in large teams.
They need a project to set up and an engineer to maintain each playbook.
AI chat assistants
Explaining an alert when you paste it in.
Nothing runs on schedule, and there is no scoped access or record of what was done.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.