> ## Documentation Index
> Fetch the complete documentation index at: https://livingcontext.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Schema diagrams

> An interactive ER diagram of your Salesforce schema, generated automatically from synced metadata.

The **Schema** page renders your Salesforce data model as an interactive entity-relationship diagram — every object, every relationship, laid out automatically. Nothing to draw, nothing to maintain: the diagram is generated from the metadata catalog your [Salesforce connection](/integrations/salesforce) already syncs, so it reflects your org as it actually is.

Open it at `/erd` in your workspace.

## Reading the diagram

Objects appear as tables; relationship fields draw the edges between them, following the same visual language as Salesforce Schema Builder:

| Edge style      | Relationship                                                      |
| --------------- | ----------------------------------------------------------------- |
| **Solid line**  | Master-detail — the detail record cannot exist without its master |
| **Dashed line** | Lookup — an optional reference between objects                    |

Edges carry cardinality markers on each end, so one-to-many relationships read at a glance.

## Display modes

Salesforce objects routinely carry dozens or hundreds of fields — showing them all makes a diagram unreadable. The toolbar offers three display modes:

* **Key fields only** *(default)* — the record Id plus every relationship field. This is the relationship-focused view most schema questions need.
* **All fields** — the full field list per object.
* **Object names only** — maximum density for very large schemas.

## Navigating

* **Search** — press <kbd>⌘K</kbd> to jump to any object or run diagram commands (on the Schema page the palette is schema-aware; the global search lives on every other page).
* **Object details** — click an object to open a panel with its fields, types, and related objects.
* **Jump to documentation** — selecting an object shows its tagged docs in the header; one click opens them in the docs reader. Untagged objects say so — a nudge for [coverage](/guides/coverage).
* **Focus related** — highlight an object's neighborhood to trace how records connect.
* **Pan and zoom** — the canvas handles large schemas; fit-to-view brings everything back on screen.
* **Shareable links** — the URL carries the selected view and object, so a link shows a teammate exactly what you're looking at.

## Saved views

Big orgs need more than one map. The **Views** sidebar lets you save focused subsets of the schema:

<Steps>
  <Step title="Create a view">
    Click **New view**, name it (say, *Sales objects*), and tick the objects it should include. A **+N related** shortcut pulls in every object related to your selection.
  </Step>

  <Step title="Share it (or keep it yours)">
    Tick **Share with my organization** to make the view available to everyone; otherwise it stays private to you.
  </Step>

  <Step title="Switch and refine">
    **All objects** is always at the top of the list. Inside a view you can show or hide individual objects, and edit or delete the view any time — deleting a shared view removes it for everyone, and you're warned first.
  </Step>
</Steps>

## What's included

* The diagram respects your organization's **documentation filters**: managed-package objects excluded there stay out of the diagram too (see [Settings](/admin/settings-reference)).
* Very large orgs are bounded by a row budget; if yours exceeds it, the header shows **partial data** — narrowing the active space or excluding managed packages brings the diagram back under budget.
* System audit fields (created/modified metadata) are hidden to keep the signal high.
* With multiple Salesforce connections, the diagram covers the connections in your active [space](/admin/spaces-and-repos).

<Note>
  The Schema page is built on [Liam ERD](https://liambx.com/), an open-source ER diagram engine (Apache-2.0), extended by LivingContext with Salesforce relationship semantics.
</Note>