Changes
A change is anything you do to a live service: a release, an upgrade, a new setting, a firewall rule. Change Management makes sure each one is planned, judged for risk, approved by the right people, carried out in an agreed window and checked afterwards, and that each step leaves evidence an auditor can test without anyone putting it together by hand.
Changes come with the Change Management plugin, built on Service Configuration: every change names the service it changes, and the service brings its owner, the accounts using it, its change windows and its freezes.
Who can use it
Needs the Change Management plugin, built on Service Configuration.
| Who | Can |
|---|---|
| Agent | Read changes; create them, edit them before approval, send them for approval, and carry out the changes they own or implement. |
| Change Approver | Read changes, and approve those an approval policy asks them to (a CAB member, say). |
| Change Manager | Everything: also approve, override the risk, reschedule and cancel others' changes, standard change templates and the settings. |
| Viewer, Auditor | Read changes. |
| Administrator | Everything. |
Everyone sees only the changes on the services of the units they work in. Each permission in detail: Who may do what.
The Changes page
Changes in the sidebar has views for what waits for your approval, yours, all open, this week, the calendar,
done, exceptions and the emergency register. Above the lists, Search finds words in the title or description, or
a key like CHG-12, and Service shows the changes to a service or one of its offerings (as main or other
service). Both stay when you switch views and live in the address; Clear filters removes them.
In this section
- Types and the lifecycle: Normal, emergency and standard changes, and the way from draft to closed.
- Recording a change: What a change records, the calendar, and changes in the inbox and automations.
- Approvals: Approval policies, stages, separation of duties and the CAB.
- The CAB: The Change Advisory Board's meetings, with an agenda that fills itself and locked minutes.
- Standard changes: Pre-approved changes from templates.
- Pipelines and the deployment gate: Let your CI ask the desk before it deploys.
- Customers: Approvals and notices for the accounts a change affects.
- Evidence: What an auditor gets: the record, the exceptions and the reports.
- Permissions and the API: Each permission in detail, and what AI assistants and the API can do.