Who hears when something is approved

The essentials

Overview

A decision goes back to the person it belongs to and to nobody else. Approving somebody’s leave is not announced to the team, and the rest of your staff have no way of seeing who asked for what.

Whatever is or is not sent, the outcome is always there to look at. Somebody can open their own requests and see where each one got to.

Before you start

You need approval access for the store. Read the request details rather than relying on a summary count.

Step by step

1. Where requests land

   Leave and availability changes wait in Approvals until somebody decides on them. Nothing moves on its own, and nothing lapses while it sits there.

2. Decide a leave request

   Open the leave requests and work through one. Whichever way you go, the request stops waiting and the answer is kept against it.

3. Availability waits here too

   When somebody changes the days they can work, that arrives in the same list. Approving it updates the pattern the roster builder works from, so the change reaches next week rather than just your inbox.

4. Who hears about it

   The answer goes back to the person who asked, and they see it the moment they open Orbit. Nobody else on the team is told.

What to check

If you need more help

If an action is unavailable, check your permissions and whether someone else has already reviewed the item. Do not approve incorrect hours just to clear a list.