Change Requests
Change requests let you plan, document, get approval for, and execute configuration changes on network devices.
Nothing is changed on a device until the request is approved. Each request gets a unique reference number —
CHG-0001, CHG-0002, etc.
Change request lifecycle
draft
→
pending_approval
→
approved
↘
rejected
→
(edit & resubmit)
| Status | Meaning |
|---|---|
draft | Being built out. Not yet submitted. Can be edited freely. |
pending_approval | Submitted and waiting for a reviewer to approve or reject. |
approved | Approved. Execution jobs are automatically queued and sent to the edge agent. |
rejected | Reviewer rejected it. You can edit and resubmit. |
What happens when a change is approved
Approval automatically creates one execution job per structured change action in the plan. Those jobs are dispatched to the edge agent at the target device's site and executed. You can track the execution status of each action back on the change request detail page.
Guides
- 1 Create a Change Request Open a new change request with a title, description, and target device.
- 2 Add Change Actions Define the specific configuration steps — port descriptions, VLANs, admin state, speed/duplex.
- 3 Submit for Approval Send the completed change request to a reviewer.
- 4 Approve or Reject a Change Review a pending change and approve it to execute or reject it with feedback.