Requests for administrator or privileged accounts are approved and signed by the system owner; the IT administrator then records exactly what was granted and until when, and the record is filed in Drive.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
7
Roles
System owner, IT administrator, Security team
Apps
Google Drive
Level
Intermediate, about 16 min to set up
Privileged access is where most security incidents start, so it deserves more than a chat message. The requester names the system, the level of access, the reason and how long they need it. The system owner approves and signs. The IT administrator then grants the access and completes a provisioning record (account, privileges, expiry date, MFA confirmed), which is saved to Google Drive as audit evidence. The requester is told the access is live and when it expires, and the security team gets a flow report.
Form: Administrative Account Access Request
Starts the workflow
E-mail: request received
Approve & sign: access request
Approve & sign · System owner
Deny: E-mail: not approved · Approve: Record the access granted
E-mail: not approved
Record the access granted
Follow-up form · IT administrator
E-mail: complete
Google Drive: audit evidence
App action · Google Drive
Flow report
Flow report
Administrative Account Access Request
Starts the workflow · 11 questions
Access Provisioning Record
Follow-up form · 5 questions
You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.
Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.
Teams request new laptops, phones, instruments or tools; the department manager approves and signs, and procurement orders the items and tells the requester the PO and delivery date.
4 steps · 2 rolesHelp Desk Ticket ApprovalHelp desk tickets that need a sign-off are routed by type: purchases to the budget holder, access to the system owner, and every ticket is then approved and signed by the IT support lead.
10 steps · 5 rolesInformation Request ApprovalStaff request a data extract or report; the data owner approves sharing it, a data analyst prepares it with escalation if it stalls, and the data protection officer gets a report.
6 steps · 4 rolesIT Change RequestIT changes are routed by type: standard changes go straight to scheduling, normal changes need the CAB chair's signature and emergency changes the emergency approver's, before the window is booked and implemented.
12 steps · 4 rolesIT Incident ManagementService outages are classified and signed off by the incident manager, resolved by the resolver group, analysed for root cause and formally closed (or reopened) by the service owner.
8 steps · 4 rolesIT Service ManagementUsers describe an IT problem in their own words; AI sorts it into network, hardware, software or accounts and hands it to the right support team, with a Drive log of every ticket.
9 steps · 5 roles