Patch Operator
Records asset-specific patch attempts and their outcomes.
Can
- Manage patch attempts
- View patch catalog, Assets, Changes, Services
Starts on: Change schedule
Give each person the records needed for their patch and service decisions.
| Role | Patch catalog | Patch attempts | Changes | Assets and services | Incidents and problems | Requests and receipts |
|---|---|---|---|---|---|---|
| Patch Operator | View | Edit | View | View | View | View |
| Change Manager | — | View | Approve | View | View | View |
| Service Owner | — | View | Edit | Edit | Edit | Edit |
| Incident Responder | — | View | View | View | Edit | View |
| Problem Analyst | — | — | View | View | Edit | View |
| Request Coordinator | — | — | View | View | View | Edit |
| Admin | Edit | — | View | View | View | Edit |
Records asset-specific patch attempts and their outcomes.
Starts on: Change schedule
Reviews service change risk, timing and rollback plans.
Starts on: Change schedule
Reviews service impact and responds to service interruptions.
Starts on: Change schedule
Investigates active incidents and adds dated updates.
Starts on: Failed patch attempts
Owns root cause investigation following recurring or serious incidents.
Starts on: Open incidents
Reviews and fulfils requests for the service team.
Starts on: Requests awaiting decision
Maintains users, people links and integration receipt review access.
Start free, then use Proto to change fields, steps and approvals before your team goes live.