Go back to Metadata Dictionary Template

Important Information

The Metadata Dictionary is ****your central command center for understanding the Salesforce org before making any changes. This isn't just documentation, it's your decision-making toolkit.

Before any request, check the Assessment checklist below first. It'll guide you to the right information and Hub </aside>

Metadata Dictionary Structure

1.Homepage Sections

Information & Quick Navigation

Operating Principles

Link to this Guide

Change Log

5 buttons to navigate to the different Hubs

Quick Stats Dashboard

Org Health Chart and overview key aggregated metrics

Impact Assessment

Description and use case for each hub and link to the New Request Impact Assessment

flowchart TB

	
	A([Home Page]) --> S1([Quick Dashboard])
	S1([Quick Dashboard]) --> S2[Impact Assessment]
	click A "<https://www.notion.so/24f8ba4e98878023bb62fea8d59778c5?v=24f8ba4e98878141867f000c1af89c71&source=copy_link>"

	subgraph S1 [Quick Dashboard]
		Health
		Hubs
		end
	subgraph S2 [Impact Assessment]
	x("Hoe to use each hbn") 
	a("New Request Assessment") 
	
	end

2 Hub & Database Organization

Our metadata is organized into 5 focused hubs with 1 assessment checklist that mirror how I actually work:

erDiagram
    CAPABILITY_MAP ||--o{ BUSINESS_PROCESSES : supported_by
    BUSINESS_PROCESSES ||--o{ SALESFORCE_OBJECTS : uses
    BUSINESS_PROCESSES ||--o{ LIGHTNING_PAGES : displayed_on
    SYSTEMS ||--o{ INTEGRATIONS : connects_to
    BUSINESS_PROCESSES ||--o{ AUTOMATIONS : automated_by
    SALESFORCE_OBJECTS ||--o{ INTEGRATIONS : syncs_via
    LIGHTNING_PAGES ||--o{ PERMISSIONS : secured_by
    USERS }o--o{ PERMISSIONS : assigned_to

Hubs	Description	When to use	Main Databases
‣	Understand what the org does and why	"What business process does this affect?"	Capability Map
Business Process
‣	Objects, pages, and user interfaces	"Which objects and pages are involved?"	Salesfore Object
Lightning Page
‣	System connections and data flow	"What systems might break?"	Systems
Integrations
‣	Who can do what and why	"Who needs access to what”	Permissions
Users
‣	Flows, processes, and custom logic	"What automations need updating?"	Automations

Other Pages

Page	Use Case	Databases
New Request Assessment Checklist	Your workspace for evaluating new requests	User Requests

Key Operating Principles

Principle Name	Definition	Examples
Impact First	Always check who/what is affected before changing anything	• Which users will this impact?" → Users & Access Hub
• "What integrations might break?" → Integration Landscape
• "What processes use this data?" → Business Process Hub
Business Owner Accountability	Every component has a business owner (not just technical owner)	• Technical decisions require business approval
• Business owners define success criteria
• Change requests go through business stakeholders first
Evidence-Based Decisions	Track usage, measure success, justify existence	• Unused = removal candidate
• High usage = careful change management
• Medium usage = optimization opportunity
Continuous Governance	This dictionary evolves with the org	• Update after every major change
• Review quarterly for accuracy
• Sunset documentation for removed components
Efficiency Through Context	Spend 5 minutes here to save hours later	• Understand the "why" before touching the "how"
• Know the stakeholders before starting the work
• Plan communication before deployment

FAQ

Why build a Metadata Dictionary? </aside>

What skills are required to build and maintain a metadata dictionary? </aside>

How can I use this template? </aside>