Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionarySSystem Overview
AdministrationAdvanced

System Overview

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.

§ 01

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.

§ 02

In plain English

👋 Study buddy

Here's a simple way to think about it: System Overview is the quickest way to know if your org is approaching its limits. Daily API calls, custom objects, code coverage - usage against limits, in one view. Green is fine, yellow is plan-now, red is already-trouble.

§ 03

Worked example

scenario · real-world use

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.

§ 04

Why System Overview is the quickest way to know if your org is approaching its limits

Salesforce limits aren't theoretical - they're hard caps. Daily API calls, custom objects, code coverage, scheduled jobs, custom fields per object, all have ceilings, and hitting them produces tickets nobody on your team wants to file. System Overview is the page that tracks usage against each limit in one view. Green numbers mean room to grow; yellow numbers mean it's time to plan; red means you're already in trouble.

The reason it's worth a regular look is that the alarms come quietly. The platform tells you about hitting a limit, not approaching one. A custom-field count that's at 480 of 500 is fine until next quarter's project takes it past the cap mid-deployment. Make this page part of your monthly platform review, plan capacity buys before they become emergencies, and document the path for cleanups (deleting unused custom fields, archiving inactive flows) when you're approaching a limit.

§ 05

How to set up System Overview

System Overview is a single-page admin dashboard summarizing org health — API usage, scheduled jobs, data and file storage, custom code limits, permission set assignments. Good first stop for "is anything weird?" health checks.

  1. Open Setup → System Overview

    Setup gear → Quick Find: System Overview → System Overview.

  2. Review API Usage

    Last 24 hours of API call volume vs license limit. Approaching limit means an integration is misbehaving.

  3. Review Schema (Custom Objects, Custom Fields, Code)

    Counts vs limits. Hitting the Custom Field limit blocks new field creation.

  4. Review Business Logic (Apex classes, triggers, scheduled Apex)

    Code health. Validation errors here mean Apex is broken.

  5. Review User Interface (Tabs, Custom Apps, Page Layouts)

    UI customization counts.

  6. Review Most Used Licenses and Permission Sets

    Who's using what. Identifies unused licenses for reclamation.

  7. Drill into any section for details

    Each section is a link to the underlying Setup page.

Key options
API Usageremember

Past 24h API calls. Edition-specific limits.

Schema countsremember

Custom Objects, Fields, Code, Page Layouts vs limits.

Business Logicremember

Apex code health and scheduled Apex.

License usageremember

Active assignments per license type.

Gotchas
  • API Usage is a 24-hour rolling window. Hitting the limit blocks API calls — including integrations. Slow integrations or polling loops are common culprits.
  • Custom Field limits per object are real. Hitting them blocks new field creation — must delete unused fields or pay for higher edition.
  • System Overview is read-only. It surfaces issues but doesn't fix them — fix at the underlying Setup page.
§ 06

How organizations use System Overview

Vanguard Solutions

Caught custom-field count approaching the cap; cleanup project completed before limits blocked deployments.

Pacific Crest Bank

API usage trending up flagged for capacity buy; expansion happened deliberately, not under deadline pressure.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on System Overview.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

🧠 Test your knowledge

Q1. Why is understanding System Overview important for Salesforce admins?

Q2. What is the primary benefit of System Overview for Salesforce administrators?

Q3. Can a Salesforce admin configure System Overview without writing code?

§

Discussion

Loading…

Loading discussion…