Approvals Workflow Guide

Modified on Tue, 3 Mar at 12:44 AM

Purpose:

This guide will serve as a reference for request asset management workflows in Tango Reserve.

The goal of this article is to assist a Tango Reserve client in setting up a request assets workflow successfully in Tango Reserve.

Workflow Diagram:

mceclip0.png

Prerequisites for setting up reservation approvals:

  1. Make sure that you understand how Asset Groups and User Groups work together. 
  2. An asset requiring approval must be set up and configured inside of Reserve as part of a “Requests” Asset group.
  3. The requesting Registered User must be a part of a User Group with permission to “request” an asset in the “Request Assets” group.
    • The request permission allows Users to make a Request for Reservation on an Asset. Requests must be approved by Users with the Permission to approve.

mceclip2.png

  1. An Approver must be a part of an “Asset Approvers” User Group with permission to approve requests.
    • The approve permission allows Users to approve Requests made on Assets.

mceclip1.png

Groups and Permissions

Permissions, such as the ability to View, Reserve or Manage Assets, can only be established between groups of Users, known as User Groups, and groups of Assets, known as Asset Groups.

As a guide for Administrators on a brand-new Reserve, there are default Asset/User Groups already established by default. Administrators can re-purpose these groups or create new ones to fit the needs of their organizations.

There are two default asset groups – Request Assets and Reserve Assets. Reservations for assets in the Request Assets group must be approved by an Asset Approver. Assets in the Reserve Asset group can be reserved if they are available.

There are three default user groups – All Users, Asset Approvers, and Asset Managers. It is up to an Administrator to determine which Users belong to which User Groups. At least one User Group must be assigned when a User is first created, however, Users can belong to multiple User Groups.

Asset Approvers group includes all the users that are able to approve reservation request. Asset Managers can manage and delete allocations.

Each User Group can be given the following Permissions:

  • View Assets allows user to see the selected Assets Group(s)
  • Make a Request to Reserve Assets in the Selected Asset Group(s)
  • Reserve Assets in the selected Asset Group(s)
  • Approve Requests to Reserve Assets in the selected Asset Group(s)
  • Manage Assets in the selected Asset Group(s)
  • Delete Assets in the select Asset Groups(s)

** Note: User Groups cannot have permission to both Make a Request and Reserve Assets

Approvals Workflow

  1. An end user requests use of an asset which requires approval.**
    1. This will be denoted on available assets by an “*” or “†”at the end of the resource name in the reservations screen.
  2. The user selects the room which requires approval and completes the required fields in the reservation page. Once the user clicks “submit” they will receive the message "your request has been saved" and be returned to the Agilquest Reserve landing page.
  3. The user will receive an email confirming that the reservation has been created but is “Awaiting Decision.”

 

Approval:

  1. The Approver will log into Tango Reserve and go to the Settings page. Once there, the user will navigate to “Requests” tab.**
  2. Under “Requests” the approver will see a listing of reservations that are waiting for a decision.
  3. From this screen, the Approver may check one of the boxes under “Actions” beside the reservation to approve or deny the reservation.

**Please note, you cannot approve your own reservations: Please see this article for more details.

User experience after approval or denial of a reservation:

  1. If a reservation is approved, the user will receive notification via email. This email subject line will note the reservation approval.
  2. Likewise, if a reservation is denied, the user will receive notification via email. This email subject line will note the reservation denial.
  3. End of workflow.

Reservation state changes:

Inside of the requests tab, the Approver will be able to see differing changes in reservation status. Below is a glossary of these terms.

Status 

Description 

Draft Reservation

Initial starting status for a reservation. This is for new reservations.

Request is Awaiting Decision

Reservation is awaiting a manual decision from an Approver.

Awaiting Check In

Reservation is awaiting Reservation Owner check in.

Pending - Before Start Time (only for those Assets that do  NOT require Check In)
Active - After Start Time has Passed (only for those Assets that do NOT require Check In)
Checked in - After Check In has Occurred (only for those Assets that DO require Check In)

Reservation is active or pending

Request Denied

Reservation approval was Denied by an Approver

Reservation Expired

The Reservation has expired

Reservation Canceled by Administrator

The Reservation was bumped

Reservation Canceled

The Reservation was canceled

For those Assets the DO require Check In: Reservation is Checked Out
For those Assets that do NOT require Check In: Reservation has Ended

Reservation was checked out of.

Reservation Canceled Within Lead Time

Reservation was canceled within the cancellation lead time. 

Request with Multiple Assets is Awaiting Reservation Decision

Reservation's parent is awaiting an approval decision. When the parent is approved, the child is put into a pending or awaiting decision status.

 

 

 

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article