Access gets handed out in chat. "Can you add me to the finance tool?" Then months later nobody knows who has what, or why. I want every ask to carry a reason, a level and a manager's name, so the answer is simple and the record stays.
Who approves it?
The form collects the facts, and the manager approves outside it. A manager field and a tick box let IT check the approval. The form grants nothing and connects to no tool. It never asks for a login. IT creates the account and shares it in a safe way.
Why ask what data the tool touches?
Customer, finance and employee records need more care than a design tool. One multiple choice question shows IT which requests need a second look. The level question makes people choose the lowest access that does the job. Many people call this a system access form, and the idea is the same.
Can the person's AI fill it in?
Yes. It might ask: "Which tool do you need?" Then "View only, edit or admin?" Then "Why do you need it?" It shows the answers and sends them only after a yes. See agent-fillable forms.
Not the same job
A customer who asks to see their own personal data needs a data access request instead. Broken equipment is a work order request. More tools are in IT and operations forms.
Questions
How do I review who asked for admin?
Filter the CSV on `access_level` for Admin. Those rows deserve a second look, and the data question helps you decide how much care each one needs.
Can temporary access end by itself?
No. The form records an end date but grants and removes nothing. Sort the CSV by `needed_until` each month and remove expired access in the tool yourself.
How often should I review old requests?
Download the CSV every quarter and compare it with the real list of accounts in each tool. The gap shows access that nobody asked for or nobody removed.