Who approved that access? Ask the ticket.
A user access review our founder built. It compares Active Directory application access month to month, then checks the changes against Jira ticket numbers for the authorization behind them.
Sound familiar?
Maybe your access review goes something like this. This month's group memberships come out of AD in one export and last month's in another, and somebody lines them up in a spreadsheet to find what moved. Then the Jira searching starts. One change, one search, until the afternoon's gone.
"Who approved this?" takes two seconds to ask. Answering it shouldn't eat the rest of the day.
What the review does
It does the comparing. The review sets this month's Active Directory application access against last month's. Then it checks the changes against Jira ticket numbers.
A ticket number turns "who approved this?" into something anyone can look up, and a change without one is exactly where a reviewer's time belongs.
Deciding who should have access stays with a person. On purpose.
What you'd look at
Your reviewer starts from what changed since last month, with the ticket check already done, instead of from two raw exports and a search bar. That's a much shorter read. And the review leaves a record behind, so the answer is there the next time someone asks.
Your systems, same method
Jira held the approvals in this build. Yours might sit in a service desk or an HR system, and your directory might be Entra ID rather than on-premises AD. The comparison works the same way once both sides can be read, and we confirm they can before quoting anything.
Access review work runs through our Automation & Integrations service. You get a written scope and quote before you commit, and the acceptance test is agreed before anything gets built.
Who built it
Chrysis Networks is an automation firm led by Tyler Fameli, who built this review. We show it here because it's the clearest picture of how we handle access and the paper trail behind it. Our restore-testing pipeline has a published build log too.
Start with a description
Tell us where access gets granted and where approvals get recorded. We'll tell you straight whether a review like this fits your setup.
No employee data or passwords. Not even a ticket export.