Assign cost review, service decisions and change approval to named people.
A Change Approver records the decision; Cloud Operations Engineer records the deployment outcome.
Assign service, account and incident owners before relying on their reports.
Give cost line and allocation editing to people who reconcile those records.
| Role | Spend evidence | Accounts and allocation | Cost incidents | Optimization | Changes and deployments | Data operations |
|---|---|---|---|---|---|---|
| Cloud Cost Analyst | Edit | View | Edit | View | View | — |
| Cost Center Owner | Edit | Edit | — | — | — | — |
| Service Owner | View | Edit | View | Edit | Edit | — |
| Change Approver | — | — | — | View | Approve | — |
| Cloud Operations Engineer | — | View | — | — | Edit | Edit |
| Finance Manager | View | Edit | — | Edit | View | — |
| Admin | View | Edit | View | — | View | — |
Investigates spend evidence, anomalies and cost incidents.
Starts on: Open Incidents
Reviews allocated spend and the accounts charged to a cost center.
Starts on: Allocated Resources
Owns service context, requests and optimization recommendations.
Starts on: Active Service Requests
Reviews planned cost changes and records decisions.
Starts on: Change Schedule
Tracks billing data movement, resource changes and deployment outcomes.
Starts on: Change Schedule
Reviews allocation, commitments, subscriptions and realized savings.
Starts on: Recommendation Board
Maintains access and the shared operating setup.
Start free, then use Proto to change fields, steps and approvals before your team goes live.