Jobs and Cleanup
This chapter covers the company-scoped operational pages for jobs, storage, metrics, and cleanup.
What belongs here
| Area | Why admins use it |
| jobs | review cadence and operational status of company-relevant processing |
| storage | understand growth and retained operational volume |
| metrics | inspect health signals in company scope |
| config cleanup | remove stale or obsolete company-side configuration data carefully |
Practical page matrix
| Page | What admins usually read there | Typical next step |
| jobs | whether operational processing looks healthy enough for company scope | compare with the affected product area after the next cycle |
| storage | whether retained or generated data is growing unusually | review cleanup or retention decisions |
| metrics | whether delay, backlog, or pressure is visible from company scope | decide whether the issue is local or needs superadmin review |
| config cleanup | whether stale configuration can be removed safely | confirm ownership and downstream impact first |
Operator rule of thumb
- use jobs and metrics to confirm whether data is merely delayed
- use cleanup only when ownership and impact are clear
- check downstream product areas after changing anything operational
Typical warning signs
- product data looks stale after a settings change
- storage grows, but business value does not
- cleanup is requested without a clear owner
- one company shows pressure while others do not
Need the technical deep dive?
See System Documentation: Admin Jobs.