# What is Salesforce dependency?

> A Salesforce dependency exists when one component references another: a Flow that reads a field, an Apex class that queries an object, a validation rule that compares a picklist value. Dependencies come from code, automation, formulas, layouts and security settings across the org.

Source: https://synconai360.com/glossary/salesforce-dependency

## Why it matters

Dependencies decide whether a change is safe. A dependency map is only useful if every line in it is backed by evidence and its gaps are stated, because a missing line looks the same as no dependency.

## In SyncOnAI 360

SyncOnAI 360 builds one dependency graph per org from parsed source and Salesforce's own dependency data. Every relationship traces to evidence, and components whose source could not be read are reported rather than treated as having no dependencies.

## Related terms

- [Blast radius](https://synconai360.com/glossary/blast-radius)
- [Impact analysis](https://synconai360.com/glossary/impact-analysis)
- [Salesforce metadata](https://synconai360.com/glossary/salesforce-metadata)