How to work with Approvals

On this page

Some tickets need an approval before their work goes on: a change request, for example, is usually approved before its planning and implementation begin. A technician creates an approval on the ticket in the Web App and requests it. The approvers vote in the Web App or in the Self Service Portal, and their votes decide the approval. At the end, the ticket is Approved or Rejected, and its Approvals tab lists every approval stage and approval request.

An approval round on a ticket is an approval stage, and it holds one approval request for each approver. A ticket can have several stages, ordered by their rank, and each stage can have its own approvers and its own type, which decides how the votes are counted. For the full description, see Approvals.

Before you begin

  • In a new 2026.1 database created with the Default Workflow, approvals are raised, voted on, and reassigned with workflow actions, and this article follows that configuration; see Default Workflow Configuration. An upgraded database need not have this content, and an administrator may have changed it.
  • Incidents, service requests, change requests, and work orders carry the actions Create Approval, Request Approval, Approve Request, and Reject Request. The forms named in this article are those of a change request; the other ticket classes carry actions with the same names.
  • On a change request, Create Approval is offered to the administrator roles and the Change Request Manager and Technician roles.
  • You see a ticket's approval stages only if you may view the ticket. Changing or deleting an approval stage or an approval request also requires the right to edit the ticket; see Permissions Reference.
  • Decide who approves: the active members of a group, individual people, or one approver found from the ticket by a position, such as, on an incident, the requester's manager or the service manager of the incident's service.

Create the approval

In the Web App (for how to find and run actions on a ticket, see Work on a Ticket):

  1. On the ticket, run Create Approval. On a change request it is offered in Draft, Assigned, or In Progress.
  2. Complete the form:
    • Reason for Approval Request, which is set to the change request's summary in the Default Workflow.
    • Create Approvals by: individuals, a group, or a position, with the matching Approvers, Approval Group, or Position and Position Type. It is set to "Choosing a Group", and Position to "Requester Manager", in the Default Workflow.
    • Type, which is set to Any Approved in the Default Workflow, and Category. The type decides how the votes are counted; see Read the outcome.
    • Minimum Vote Percentage or Single Vote Timeframe, depending on the type. Minimum Vote Percentage is set to 30 in the Default Workflow.
    • Attachments.
  3. Run the action. It creates one approval stage with one approval request per approver and logs "Created Approval". When you chose a group, every active member of the group becomes an approver, and members who are Inactive or Disabled are skipped.

To have the ticket approved in more than one round, for example by different approvers or with a different type, run Create Approval again: each run creates one more approval stage.

Request the approval

In the Web App:

  1. On the ticket, run Request Approval. On a change request it is offered in the statuses from Draft to Implemented, and only while the change request has both a pending approval stage and a pending approval request.
  2. Enter the Approval Deadline, which is set to five days from now in the Default Workflow, Comments, time spent, and attachments.
  3. Run the action. On a change request, the change request is set to Pending Approval, its followers and collaborators are notified, and the request goes to the pending approval stage of lowest rank. The stage's pending approvers are e-mailed: by rank on a stage of the Sequential Approval type, and all at once on a stage of any of the four other types.

In the Mobile App, a change request's Actions page offers Create Approval and Request Approval as well; see Approvals in the Mobile App.

Follow the approval

In the Web App, open the ticket's Approvals tab. The tab is a tree: each top row is an approval stage, and the stage's approval requests are listed under it. A stage row shows the stage's name in the approver column. The columns are the approver, the decision date, the type, the status, and the rank. Open a row to open the approval stage or the approval request.

Approval requests are also listed in Approval Requests, in the Service Desk group of the main menu. To go from a request to the ticket being approved, use the link in the approved record's column.

Vote on the approval

Each approver approves or rejects. After every vote, the stage's outcome is calculated from its type.

In the Web App

  1. Open the ticket awaiting approval or its approval stage, or open your approval request from the ticket's Approvals tab or from the Approval Requests list.
  2. Run Approve Request or Reject Request.
    • On the ticket, the actions are offered only to a pending approver on a pending stage. On a change request, they are offered while it is in Pending Approval, and on a Sequential Approval stage only to the first pending approver by rank. The form asks for approval notes or a reason for rejection (on a change request, Approval Notes or Reason for Rejection), and optionally time spent and attachments.
    • On an approval request, the actions are offered while it is Pending, and only to the request's approver. The form asks for a Comment.
  3. Run the action.

In the Self Service Portal

The tabs of Tickets and Requests depend on the portal modules that are enabled, and the tab of approval requests appears only for users who have approvals. In a new 2026.1 database created with the Default Workflow, an approval request has two portal actions, Approve Request (Self Service Portal) and Reject Request (Self Service Portal), each with its own form.

  1. Open Tickets and Requests.
  2. Select the tab of approval requests.
  3. Open the approval request. It records its approver, when the vote is due, the decision and when it was made, and the approver's comment.
  4. Select the action you want to run. If it is not among the buttons, open the … menu and select it there.
  5. Complete the action form and submit it. If the portal shows messages about what you entered, close each one.

If an action leaves the approval request no longer visible to you, the portal takes you to the list of approval requests. For the details of action forms in the portal, see Record your decision.

From an e-mail or a mobile app

In a new 2026.1 database created with the Default Workflow, the approval e-mails can carry one-click links to approve or reject the request. They carry the links only when the workflow parameter Enable Graphical Approval Submission is on, and it is set to off in the Default Workflow. The links need the API to be installed and working, and they work only when the API uses token authentication; see Vote from an e-mail.

In the Mobile App, approvers vote from the Actions page of the record or of their approval request; see Approvals in the Mobile App. In the Alloy Self-Service app, approval requests are on the Approval Requests tab of My Items when the Approvals module is on; see Alloy Self-Service Mobile App.

Change the approvers or cancel the approval

While a vote is open, you can give an approval request to another approver. In the Web App:

  1. Open the approval stage from the ticket's Approvals tab.
  2. On the General tab, in the Approval Requests grid, use Actions on the approval request and choose Change Approver. It is offered while the approval request is Pending, to the administrator roles and the Approval Manager role.
  3. In the Change Approver Information form, choose the approver and the approval stage and enter a Reason for Change. You can also change the type, the due date, and the rank.
  4. Run the action.

To add an approver to a stage, run New Approval Request, offered while the approval stage is Pending. Its form, Create Approval Request, requires an approver and asks for a type and a rank. Adding a request writes "Approver added" to the stage's history.

To stop the approval before it is decided, run Cancel Approvals on the ticket. It is offered while a stage is Pending or Pending Approval; on a change request, only in Draft, Assigned, In Progress, and Pending Approval, and only to the Administrator (Full), Administrator (Workflow), and Approval Manager roles. It sets those stages and their pending approval requests to Not Required and returns the ticket to In Progress.

Read the outcome

The type of the approval stage decides how its votes are counted:

  • Any Approved: one approval approves the stage; the stage is rejected when all approvers reject.
  • Single Vote Rejection: one rejection rejects the stage; the stage is approved when all approvers approve.
  • Majority Decision: 51 percent decides the stage, either way.
  • Required Percentage: the votes are compared against the stage's minimum vote percentage.
  • Sequential Approval: approvers approve or reject individually in order of rank. One rejection rejects the stage, and the stage is approved when all approvers approve; until then, the next pending approver by rank is determined.

When a stage is approved or rejected, its approval requests that are still pending are set to Not Required. An approved stage opens the stage of the next rank: that stage is set to Pending Approval, its start time is set to the current time, its deadline is shifted by the length of the first stage's window, and its approvers are e-mailed. A rejected stage opens no next stage.

The ticket's status follows the stage that was created last for it. When that stage is approved, the ticket is set to Approved; when it is rejected, the ticket is set to Rejected. If an earlier stage is rejected while a stage created later is still pending, the ticket's status stays as it is.

An approved change request goes on with its work, for example with Implement Change, which is offered in Approved; see Take a change request from Draft to Closed. Closing the ticket later leaves its approval stages and approval requests as they are.

What you have now

The ticket is Approved or Rejected. Its Approvals tab keeps every approval stage with its approval requests, each with its approver, decision date, type, status, and rank.