> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/request-management/approvals.md).

# Approvals

Add approvals to a service or any request, sequential or parallel, with due dates and fallback logic. Approvers decide from Slack or Teams, and everything is logged

Approvals can be preconfigured in a Service Catalog item or added ad‑hoc from any request. Choose sequential or parallel approvers, set due dates, and define what happens on non‑response.

Approvers receive a card in Slack/Teams and can approve or decline with an optional comment. Everything is recorded in the request timeline. If an approver is out, fallback logic routes to the manager’s manager, app owner, or a backup group. Changing scope—like a different app or higher access level—can automatically re‑request approval.

Approvals can trigger downstream actions: on approval, provision access in Okta/Azure AD, add to a group, or notify the requester. On decline, update status and message the requester with next steps.

### Deciding from a link

Approval links in email and Teams ask you to **Confirm approval** or **Confirm rejection** before recording your decision. Links to mark manual app access actions as done or failed also require confirmation.

If the approval is already settled or the request is closed, the page shows **This request can no longer be decided**.

### How long a decision link lasts

The approve and decline links Siit sends by email, Slack and Teams are signed and expire **30 days** after they were sent. Open one after that and the page says *This link has expired* — nothing is decided, and nothing is lost. Ask for the approval again, or decide it from the request itself.

Satisfaction survey rating links work the same way, and carry the same 30-day life.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FxZo9ZAqfIkzHbqwKqp8o%2FCleanShot%202025-09-18%20at%2010.42.21%20(1).png?alt=media&amp;token=e19b20da-63b7-4cb6-9372-4d72bc3aa69d" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/request-management/approvals.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
