Teams request a new server or VM; the infrastructure manager approves it, a systems engineer provisions it and records the details, and a review date goes on the calendar.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
5
Roles
Infrastructure manager, Systems engineer
Apps
Google Calendar
Level
Intermediate, about 14 min to set up
Servers are easy to create and hard to get rid of. This template asks for the purpose, environment, size, operating system and how long the server is needed. The infrastructure manager approves it with capacity and cost in mind. A systems engineer provisions it and records hostname, IP address and backup policy in a task form. The requester receives the connection details by e-mail, and a review is put on Google Calendar for the end date so the server is resized or retired rather than forgotten.
Form: New Server Request
Starts the workflow
Approve server: {{trigger.body.application}} ({{trigger.body.environment}})
Approval · Infrastructure manager
Deny: E-mail: Server request not approved · Approve: Provision the server
E-mail: Server request not approved
Provision the server
Task · Systems engineer
Mark as done: Google Calendar: review date
Google Calendar: review date
App action · Google Calendar
E-mail: Your server is ready: …
New Server Request
Starts the workflow · 12 questions
Server Build Record
Task form · 4 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