SysOps Approval Workflow

Approvals

Shows how requests move through review, approval, escalation, and final authorization.

Session requiredAuthenticated routes expect a real session token or cookie.API base: https://dev.sysopsai.net/api
Why It Matters

Approvals should be visible, time-bound, and easy to escalate.

The approval workflow is now route-native in `apps/web`, making authorization state and aging visible alongside queue and delivery work instead of hidden behind email.

Access approvalsSecurity exceptionsPrioritization tradeoffsChange authorizations
current queue
6

Items in approval state

needs follow-up
2

Aging approvals

automated
3

Reminder / routing actions

clear
1

Executive decision currently pending

Core Approval Flow

The goal is to make authorization simple enough to follow and strong enough to govern risk.

1

Request Submitted

Work enters through the shared intake path with the business need, desired timing, and affected users or systems.

2

IT Review

IT validates that the request is understandable, classifies the work, and determines whether approval is required.

3

Business / Risk Approval

The right approver confirms access, ownership, risk acceptance, or tradeoff decision depending on the request type.

4

Implement And Notify

Once approved, IT proceeds with the work, records the decision, and updates the requester and stakeholders.