Approvals

Add approvals to a service or any request, sequential or parallel, with due dates and fallback logic. Approvers decide in one click 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 clean card in Slack/Teams and can approve or decline with one click and 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.

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.