Privileged access review

Confirms every standing admin grant is still needed, and turns one-off elevation into a recorded, time-boxed grant.

macOS — coming soonSee the 4 automations
IT / AUTOMATE.md

Every Friday at 4pm, pull the week's admin sign-ins, flag any from a country or address not seen before, and post the short list for review.

Ready-made: Privileged Login Review

The job, and what good looks like.

Administrator rights are handed out to clear a one-day problem and never handed back, so the list of people who can change production grows every quarter. Nobody can say which of those grants are still required, and the evidence an auditor asks for is a screenshot of a settings page. The workflow starts from the vault, not from a spreadsheet. It lists standing admin grants, the reason each one was issued, how old it is, and what it was last used for. Anything older than the agreed window is queued for the named owner to confirm or release, with release as the default answer. New elevation is issued just-in-time for a fixed number of hours against a recorded reason, and it expires on its own without a ticket closing first. At the end of the cycle the decisions, the releases and the grants that stayed are written to one evidence record. A human approves every release, every extension, and any exception that stays open.

When it is handled

  • Standing admin grants justified or released
  • Elevation expires without a reminder
  • Review evidence exportable for an audit

Works with tools like

  • CyberArk
  • Microsoft Entra ID
  • Microsoft Sentinel
  • Vanta

Ready-made automations. Pick the one that fits.

Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.

Access Review Evidence Pack

When a review cycle closes, pull the decisions into one evidence document and attach it to the compliance record, so the next audit question is a download.

When an access review cycle closes

Elevation Expiry Check

Every weekday at 8am, list admin grants older than 30 days from the vault, then open one review ticket per owner with the reason each grant was issued.

Every weekday at 8:00am

Just-In-Time Admin Request

When an engineer asks for production access, record the reason, issue a four-hour elevation through the vault, and link the change ticket so the session can be reviewed later.

When an engineer requests production access

Privileged Login Review

Every Friday at 4pm, pull the week's admin sign-ins, flag any from a country or address not seen before, and post the short list for review.

Every Friday at 4:00pm

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.

Privileged Login Review

Approve before it posts in Slack?

ReviewApprove

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.

Related workflows.

Access reviews

Works the periodic entitlement list so access nobody still needs is released, and every decision is written down.

Write your own

Joiner, mover and leaver access

Grants, adjusts and removes application access from one approved people record, so nothing survives a leaver.

4 automations

Audit trails

Joins the scattered administrative change records into one timeline, so an auditor's question is a search rather than a fortnight of exports.

Write your own

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 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.

macOS — coming soon