Glossary
Salesforce glossary for architects, admins and auditors
Short, precise definitions of the Salesforce terms that decide what an org really does — how a save runs, how automation and access are built, what makes an org hard to change. Each entry is checked against the official Salesforce documentation it links to.
A–Z
All terms
A
- Apex trigger
- Apex code that runs automatically before or after records of an object are inserted, updated, deleted or undeleted. Read more
B
- Before-save vs after-save flow
- The two optimisations of a record-triggered flow: Fast Field Updates run before the save, Actions and Related Records run after it. Read more
D
- Salesforce Dependency API
- The Tooling API object MetadataComponentDependency, which returns which metadata components in an org reference which others. Read more
F
- Field-level security (FLS)
- The Salesforce setting that decides, per profile or permission set, whether a user can read or edit each field of an object. Read more
M
- Managed package and namespace prefix
- A managed package is a distributable, upgradeable bundle of metadata; its namespace prefix is the identifier added to every component's API name. Read more
O
- Salesforce order of execution
- The fixed sequence in which Salesforce runs flows, triggers, validation rules and other automation when a record is saved. Read more
P
- Permission set group
- A bundle of permission sets assigned as one unit, typically per job role, with an optional muting permission set to switch permissions off. Read more
R
- Record-triggered flow
- A Flow that Salesforce launches automatically when a record of a given object is created, updated or deleted. Read more
T
- Salesforce technical debt
- The accumulated cost of past configuration and code shortcuts in a Salesforce org that makes every future change slower and riskier. Read more
V
- Validation rule
- A formula that blocks a record from being saved and shows an error message whenever the formula evaluates to true. Read more
Go further
From definitions to your own org
The guides walk through the practical work — documenting a Flow, finding where a field is used, preparing an audit.