Request an audit of an IT system: the audit manager approves and schedules it, Slack and the calendar are updated, an auditor records findings and the system owner submits a remediation plan.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
8
Roles
IT audit manager, IT auditor, System owner
Apps
Google Calendar, Slack, Google Drive
Level
Intermediate, about 24 min to set up
For internal IT audits of access, patching, backups and configuration. The requester names the system, the scope and the reason (scheduled, incident follow-up, certification). The IT audit manager approves and the audit window goes on Google Calendar and is announced in Slack so the system's users expect it. The auditor runs the audit and records findings and a risk rating in a task form. The system owner then receives a remediation form for owners, actions and dates. The report is saved to Google Drive and the requester gets a summary.
Form: IT System Audit Request
Starts the workflow
Approve audit: {{trigger.body.system}}
Approval · IT audit manager
Deny: E-mail: Audit request not approved · Approve: Google Calendar: audit window
E-mail: Audit request not approved
Google Calendar: audit window
App action · Google Calendar
Slack: announce audit
App action · Slack
Audit {{trigger.body.system}}
Task · IT auditor
Mark as done: Remediation plan for {{trigger.body.system}}
Remediation plan for {{trigger.body.system}}
Follow-up form · System owner
Google Drive: audit report
App action · Google Drive
E-mail: Audit complete: …
IT System Audit Request
Starts the workflow · 8 questions
Audit Findings
Task form · 4 questions
Remediation Plan
Follow-up form · 3 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.
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.
7 steps · 3 rolesEquipment Purchase RequestTeams 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 roles