Global Variables are most useful when admins know which one to reach for in each scenario. The workflow below covers the standard patterns for using Global Variables across formulas, Visualforce, and Lightning components.
- Identify the context the customization needs
Decide what contextual information the customization requires: the current user's identity, their profile, the org's configuration, a translated label, a static resource reference. Match the requirement to the right Global Variable from the catalog. For common scenarios (current user, profile, org), the Global Variable choice is obvious. For less common ones, the developer documentation lists every available variable with its fields.
- Reference the variable in formulas, Visualforce, or Lightning
Reference the Global Variable using the appropriate syntax. In formulas: $User.Profile.Name. In Visualforce: {!$User.Profile.Name}. In Lightning Web Components: import from @salesforce/user or use specific user-info APIs. The syntax differs slightly per tool but the underlying values are the same. Test the customization with multiple user contexts to confirm the variable resolves correctly for each.
- Handle null and missing values
Some Global Variable fields may return null in certain contexts: a user without a manager has $User.Manager equal to null. Formulas that reference such fields need null handling: ISBLANK($User.Manager) returns true for users without a manager. Visualforce expressions and Lightning component code should similarly guard against null values. Test the customization with edge-case users (no manager, no department, no specific permission) to confirm the null handling works.
- Document and maintain the usage
Document which Global Variables the customization uses and why. Future maintainers benefit from knowing the context dependencies. Watch for any Salesforce release notes that change Global Variable behavior (new fields added, deprecation of specific variables, behavior changes between Classic and Lightning). Update the customization if any referenced field is deprecated or changed.
- Global Variable fields can return null. Always handle null values in formulas and Visualforce code that references them.
- $Permission API names use the underlying permission identifier, not the human-readable label. Looking up the right name requires the Setup permissions page.
- $Setup variable accesses Hierarchy Custom Settings only. List Custom Settings use a different access pattern.
- $Label values change based on the user's language. Test the customization in each supported language to confirm the text renders correctly.
- Some Global Variables are Lightning-only or Classic-only. Cross-experience customizations may need fallback handling.