Skip to main content

Standard Event Authorisation Workflow

The default approval workflow, sending all employee requests to their manager for authorisation.

Updated yesterday

Introduction

The Standard Authorisation Workflow is the default approval process applied on company set-up. This sees that all event requests made from the employee are automatically routed to the employee's manager for review and approval. It's a reliable, no-fuss approach that works well for most organisations, offering a balance of control and simplicity.

For companies with more complex needs, we also provide a range of alternative workflows in our Library, giving you the flexibility to tailor the approval process as required. For more information, please see:

How it works

The system's standard authorisation rule is that all events requiring approval are directed to the Line Manager, with some additional rules that apply in specific cases.

All rules are as followed:

  • Employee requests event and they do not have a manager – All Admins are notified, and any one can reject/approve

  • Employee requests event and they do have a manager – Manager is notified and can approve or reject

  • Employee requests event and they have more than one manager, this happens because they can have more than one job role with different managers – All managers are notified, and anyone can reject/approve

  • If the employee is an Administrator and they do not have a manager – The request is automatically approved

  • If an Administrator adds a request for another employee – it does not require an approval

  • If the manager of the employee adds an event for an employee – it does not require approval

Employee adds an event request from the Calendar. The Line Manager will receive an email and a Todo

Picture

When approved or declined, the employee will receive a confirmation email, containing the reason if provided, and the workflow ends.


FAQs


  • Can someone pick up a request in the approvers absence?

All Admins are able to action anyone else's todo in their absence, including event requests.

Did this answer your question?