> 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/guides/request-management/approval-steps-reminders-switching-approvers-and-auto-decisions.md).
# Send approval reminders and reassign approvers
Build richer approval flows in Siit, nudge slow approvers, hand an approval to someone else, or let an approval resolve itself on a condition in approval policies.
### What approval steps are
An approval step is an action Siit can take around a pending approval, beyond the approve/reject decision itself. You add steps to an approval in an **approval policy**, and they run in the order you set.
#### The four step types
**Send reminder.** Nudge approvers who haven't responded yet. Choose the channel: Slack/Teams, email, or both.
**Switch approver.** Move a pending approval to a different approver. The original pending approval expires and a fresh one is sent to the new approver. You can keep the original approver as a follower of the request.
**Auto-reject.** On a request event you choose, automatically reject the approval and let the workflow continue down its reject path.
**Auto-approve.** On a request event you choose, automatically approve and let the workflow continue.
#### Where to set them up
* **In an approval policy:** go to **Settings → Requests → Approval policies → \[policy]** and add the steps to the approval round.
Steps run top to bottom in the order listed, so put a reminder before a switch or an auto-decision if you want to give approvers a chance first.
### Frequently asked questions
**Do reminders keep repeating?**
A reminder step sends when it runs in the sequence. Chain more than one if you want repeated nudges.
**What happens to the original approver when I switch?**
Their pending approval expires and the new approver receives a fresh one. Keep the original as a follower if they should stay in the loop.
**What can trigger an auto-approve or auto-reject?**
A request event you select on the step. Use it, for example, to auto-reject once a request is cancelled, or auto-approve when a condition upstream is already satisfied.
---
# 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/guides/request-management/approval-steps-reminders-switching-approvers-and-auto-decisions.md?ask=&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.
