Approve Staff Requests

Requests in the left navigation, and in the app. It is the queue of changes waiting on an owner or a manager.

What can arrive here

• Schedule changes. A member editing their own hours or exceptions. They are told explicitly that it is a request, because their calendar has not moved.
• Preference changes. Depending on configuration, other self-service edits.
• Payment edits and deletions. Changing or removing a recorded payment to a stylist.
• Client appointment updates, with Require Approval for Client Appointment Update.
• Client appointment cancellations, with Require Approval for Client Appointment Cancellation.
• Collaboration invitations, with Approval required for collaboration — though those go to the stylist being added, not to a manager.

Acting on one

Open the request, read what is being changed, and approve or reject. Nothing has moved until you approve.

The person is notified either way. Request notifications in Communications is what tells approvers there is something waiting — turn it on for whoever actually does this, or the queue silently grows.

What to route through approval

Approve-everything is the same as approve-nothing: the queue stops being read.

Worth routing:

• Payments. A quiet edit to a recorded payment is the one change that is genuinely dangerous.
• Schedules, if your rota is coordinated rather than self-managed.
• Client cancellations, if you charge fees and want a human deciding.

Usually not worth routing:

• Notification preferences.
• Profile details and colours.
• Anything a member could change back in ten seconds anyway.

The alternative to approval

For everything else, use the audit log. It records what happened without making anyone wait. See The audit log and approvals.

The rule of thumb: approve what is expensive to undo, audit everything else.