Definition
Hierarchy Custom Settings refers to a set of configuration options in Salesforce that control how a specific feature or area of the platform behaves. Administrators adjust these settings through the Setup menu to tailor functionality to their organization's requirements.
Real-World Example
an admin at Redwood Financial recently implemented Hierarchy Custom Settings to ensure the Salesforce org runs smoothly and securely. They configure Hierarchy Custom Settings during a scheduled maintenance window, test it in a sandbox first, and then deploy to production. The result is tighter security and a more streamlined experience for all 200 users in the org.
Why Hierarchy Custom Settings Matters
Hierarchy Custom Settings in Salesforce are a configuration mechanism that allows administrators to define custom data sets with values that can be overridden at three levels: organization-wide defaults, profile-specific values, and individual user values. When Salesforce evaluates a Hierarchy Custom Setting, it checks for a user-level value first, then profile-level, and finally falls back to the org-wide default. This hierarchical resolution makes them ideal for managing feature toggles, business thresholds, and configuration parameters that need to vary across different user populations without code changes. Unlike Custom Metadata Types, Hierarchy Custom Settings are accessible in formula fields, validation rules, and workflow criteria without SOQL queries.
As organizations scale with diverse user populations that require different configurations - different discount limits for sales managers versus reps, different feature access for beta users versus general users, different business rules for regional offices - Hierarchy Custom Settings provide a clean, maintainable approach. Without them, organizations resort to hardcoding values in Apex triggers, creating unwieldy if-else chains based on profiles, or building custom objects to store configuration data. These alternatives create technical debt that compounds with every new configuration requirement. Hierarchy Custom Settings centralize configuration management in a structure that administrators can update through Setup without developer involvement, enabling rapid business rule changes that don't require deployments.
How Organizations Use Hierarchy Custom Settings
- NexGen Sales Corp — NexGen Sales Corp uses a Hierarchy Custom Setting called 'Discount_Limits' where the org default is 10%, the Sales Manager profile override is 20%, and the VP of Sales has a user-level override of 35%. A validation rule on Opportunity references this setting to enforce the appropriate discount ceiling for each user automatically.
- Brightpath Engineering — Brightpath Engineering created a 'Feature_Flags' Hierarchy Custom Setting to control which users see new features during phased rollouts. Developers set the org default to 'disabled,' then enable features profile-by-profile or for specific beta testers at the user level without deploying code changes.
- Meridian Financial Services — Meridian Financial Services stores regional compliance thresholds in Hierarchy Custom Settings. The org-wide default sets the AML (Anti-Money Laundering) review threshold at $10,000, but the European operations profile override sets it at €5,000 to comply with EU regulations, and individual compliance officers can have custom thresholds based on their territory.