Quarterly user access review reminders and evidence collection
Remind system owners to review who has access each quarter, collect their sign-off, and assemble the evidence folder for the security lead.
The use case
Periodic access reviews are a common control: someone checks that only current staff with a real need still have access to key systems. In small teams the review slips because exporting user lists, chasing owners, and saving proof is manual. This agent keeps a schedule of systems and owners, prepares each owner's user list from exports, compares it with the current staff roster to highlight possible leavers or unusual admin rights, and sends reminders until each owner records a decision. It collects the exports, owner comments, and dates into an evidence folder. Owners make the keep or remove calls and the security lead signs off on completeness.
Example workflow
- At the start of each quarter the agent reads the systems register listing each system, its owner, and how to export users.
- Owners receive a reminder with instructions to upload a current user export, or the export is pulled where a connection exists.
- The agent compares each export with the HR or staff roster and highlights accounts with no matching active employee or with admin rights.
- Each owner reviews the highlighted list, marks accounts to keep or remove, and records a short justification.
- Removals are carried out by the system owner or IT, and the agent sends follow-up reminders for anything still open.
- The security lead checks the evidence folder for completeness and signs off, and the agent logs the review date for each system.
Tools
- Google Sheets
- Google Drive
- Slack or Microsoft Teams
- Claude
- Zapier
- HR system export
Risks and guardrails
- Name differences between the roster and system accounts cause false alarms — guardrail: highlights are suggestions and owners confirm each one.
- User exports contain personal data — guardrail: evidence lives in a restricted folder with access limited to owners and the security lead.
- Accounts could be removed in error, locking out staff — guardrail: the agent never changes access; owners or IT make removals.
- Reminders alone do not prove the review happened — guardrail: the security lead, not the agent, signs off that each system was reviewed.
Related recipe
Provider Credentialing Packet Tracker and Reminder Drafts: An agent tracks provider licenses, DEA, board certs, malpractice COIs, CAQH attestations, and payer enrollment, flags expirations and gaps, and drafts reminders for staff to approve.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Google Drive (official page): developers.google.com/workspace/drive (checked 2026-11-19)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- Microsoft Teams MCP Server (Agent 365) (official page): learn.microsoft.com/en-us/microsoft-agent-365/tooling-servers-overview (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)