Definition
System Overview is a Setup page that provides a high-level summary of the org's usage against key platform limits, including API calls, storage, custom objects, rules, flows, and other configurable components. It helps administrators monitor the org's capacity and avoid hitting governor limits.
Real-World Example
The admin at Apex Dynamics checks System Overview before creating new automations and sees the org has used 380 of 500 available workflow rules, 45 of 50 Process Builder processes, and 175 of 200 custom objects. She decides to consolidate some legacy workflows into Flows to free up capacity before adding new automations.
Why System Overview Matters
System Overview is a Setup page in Salesforce that provides administrators with a high-level dashboard of the org's usage against key platform limits. It displays consumption metrics for API calls, data storage, file storage, custom objects, workflow rules, Process Builder processes, Flows, validation rules, Apex classes, and other configurable components. Each metric shows the current usage alongside the maximum allowed, giving admins an at-a-glance view of where the org stands relative to its capacity. This page is essential for proactive governance, allowing admins to identify approaching limits before they become blocking issues.
As a Salesforce org accumulates customizations over years of development, tracking limit consumption becomes critical to avoiding unexpected failures. An org that hits its custom object limit cannot create new objects until existing ones are removed, and exceeding API call limits causes integrations to fail. System Overview helps administrators plan capacity for new projects by understanding current utilization before committing to designs that require additional objects, rules, or storage. Organizations that review System Overview regularly as part of their governance process can consolidate legacy automations, archive unused components, and request limit increases from Salesforce before constraints become emergencies.
How Organizations Use System Overview
- Apex Dynamics — The admin at Apex Dynamics checks System Overview before building new automations and discovers the org has used 380 of 500 workflow rules and 45 of 50 Process Builder processes. She decides to consolidate legacy workflows into Flows to free up capacity, ultimately converting 40 workflow rules into 8 record-triggered Flows and creating headroom for the new project.
- DataVault Financial — DataVault's Salesforce team reviews System Overview quarterly as part of their governance cadence. During a recent review, they noticed data storage had reached 85% capacity with three months of growth projected to exceed the limit. They proactively purchased additional storage and implemented an archival strategy for records older than five years.
- Skyline Real Estate — Skyline's architect references System Overview during the design phase of a new property management module. She sees the org has used 175 of 200 custom objects, which means the new module's planned 30 custom objects would exceed the limit. She redesigns the module to use 15 objects with junction objects and custom metadata types instead, keeping the org within capacity.