Access request: the right approvals, a set duration, automatic revocation
An employee needs access to the correspondence system to archive letters. Access is granted with approval, revoked when no longer needed, and every step leaves a trace for audit. That is what security and audit teams want.
The journey, step by step
Click any step or use the buttons to see the ticket status.
- Request
From the catalog: system, access type, duration, justification.
Employee - Manager approval
Approved with one click from email.
Line manager - System owner approval
Sequential approval for a sensitive system.
System owner - Grant
Administrator grants access for the set period.
Administrator - Notify user
Email and portal: active until 31 December.
System - Reminder
To employee and manager: extend?
Automation rule - Auto-revoke
A revocation ticket is created and executed, all in the audit log.
System
Before and after
| Aspect | Without a system | With TixDesk |
|---|---|---|
| Request | Email without a form | A form asking for everything |
| Approvals | Email, no record | Sequential and documented |
| Duration | Open-ended | Defined |
| When no longer needed | Access remains | Revoked automatically |
| Review | Search the inbox | Full audit log |
Features used in this journey
Service catalog
The form.
Approvals
Sequential.
Automation
Reminder and revocation.
Audit log
The trail.
Security
Controls.
Notifications
To the user.
Questions about this case
Can low-risk systems skip the owner approval?
Yes, approvals are conditional on the system and its sensitivity.
Can access be granted automatically?
With identity integration, some access can be applied automatically after approval.
See the journey on your requests
We apply this case with your details in a live demo.
- A scenario from your reality
- Your teams and policies
- Direct answers