Entitlement Settings
Entitlement Settings is the Setup page in Salesforce where admins enable and configure the broader Entitlement Management feature: the master toggle to turn on the feature, the auto-population behavior, the contact verification policy, the lookup filters that decide which entitlements match a case, the milestone tracker layout, and the default Entitlement Process applied to new entitlements.
Definition
Entitlement Settings is the Setup page in Salesforce where admins enable and configure the broader Entitlement Management feature: the master toggle to turn on the feature, the auto-population behavior, the contact verification policy, the lookup filters that decide which entitlements match a case, the milestone tracker layout, and the default Entitlement Process applied to new entitlements. The path is Setup, Service, Entitlement Settings. All decisions on this page apply org-wide and rarely change after the initial Service Cloud rollout.
Entitlement Settings is the single configuration surface that controls how the entire Entitlement Management feature behaves. Without enabling it, the Entitlement, ServiceContract, ContractLineItem, and EntitlementContact objects are not available. Once enabled, the feature unlocks the SLA timer engine, the case-level entitlement field, and the milestone tracking. Most admins configure this page once during rollout and revisit only when adding new support tiers or adjusting the auto-population logic.
How Entitlement Settings controls SLA infrastructure org-wide
Enable Entitlement Management: the master toggle
The Enable Entitlement Management checkbox at the top of the page activates the entire feature. Checking it surfaces the Entitlement, ServiceContract, ContractLineItem, EntitlementContact objects in the org. The objects do not exist in the schema until the flag is on. Reverting the flag does not delete the data but hides the objects from the UI; data created while enabled persists if the feature is later re-enabled. Most enterprise Service Cloud rollouts enable this on day one of the implementation.
Enable Entitlement Auto-Population
Auto-Population is the setting that lets the platform match new cases to the right entitlement automatically. Without it, agents must manually attach the entitlement, which most agents forget to do, and the SLA clock never starts. The matching logic picks the most specific entitlement: asset > contact > account. For multi-entitlement accounts, the platform picks the first match and a Flow can override the selection if needed. Enabling Auto-Population is one of the highest-leverage decisions on this page.
Enable Entitlement Contact Verification
Contact Verification restricts entitlement matching to listed EntitlementContacts. A platinum support contract might list five named support contacts; cases from anyone else do not match the entitlement. Enabling this implements named-contact support tiers, common in enterprise B2B agreements. The verification can be set to either a hard block (no match without listed contact) or a soft warning (match with a flag). The hard-block mode is the right choice for compliance-driven service contracts.
Default Entitlement Process
The Default Entitlement Process setting picks the process applied to new entitlements when no explicit process is selected at creation. For orgs with a single SLA tier (every customer gets the same response time), the default is set to the universal process. For multi-tier orgs, the default is typically the Standard support tier, with platinum and gold entitlements explicitly choosing the right process at creation. The default reduces configuration errors on new entitlement records.
Lookup Filters and the Case Entitlement field
The Lookup Filter section configures what entitlements appear when an agent picks one manually on a case. The default filter shows active entitlements (Start Date <= today, End Date >= today) for the case Account. Custom lookup filters can narrow further: only show entitlements where Process = the case Type, only show entitlements whose contact list includes the case Contact. The lookup filter is the safety net for cases where Auto-Population picks the wrong entitlement or where agents need to manually override.
Milestone Tracker layout
The Milestone Tracker is the UI component that shows pending and completed milestones on a Case page. Its position and configuration are set through the Case page layout, not Entitlement Settings. But Entitlement Settings controls a related option: which milestone fields appear in the tracker (Target Date, Time Remaining, Status, Completion Date). Most orgs use the defaults; some compliance-heavy orgs add custom fields like SLA Tier or Escalation Owner.
Knowledge integration toggles
Entitlement Settings includes toggles for integrating with Salesforce Knowledge: Allow Articles on Entitlements, Allow Knowledge Article Versions on Cases. These let agents attach Knowledge articles to entitlements and cases for self-service deflection. The toggles are off by default in new orgs. Most Service Cloud teams enable them to expose Knowledge attachment to the agent workflow without separate Knowledge Action configuration.
Configuring Entitlement Settings for a Service Cloud rollout
Configuring Entitlement Settings is a one-time setup activity during the Service Cloud rollout. Enable the master toggle, configure auto-population and verification, set the default process, then move on to building the actual entitlements and processes.
- Open Entitlement Settings
Setup, Service Setup, Entitlement Settings. The page has multiple sections covering the master enable, auto-population, contact verification, and lookup filters.
- Enable Entitlement Management
Check Enable Entitlement Management. Save. The Entitlement, ServiceContract, ContractLineItem, EntitlementContact objects become available.
- Enable Auto-Population
Check Enable Entitlement Auto-Population. Without this, agents must manually attach entitlements to cases, which they will forget to do.
- Decide on Contact Verification
For named-contact support tiers, check Enable Entitlement Contact Verification. For broader support tiers, leave unchecked.
- Set the Default Entitlement Process
Pick the process most new entitlements should use. The Standard tier is the typical default. Multi-tier orgs override per entitlement at creation.
- Configure Lookup Filters
Customize the filter that shows entitlements in the case entitlement picker. Default filters by Account and active dates. Custom filters narrow further per business rule.
- Enable Knowledge integration if needed
Check Allow Articles on Entitlements and related toggles if the org uses Salesforce Knowledge with entitlement-based case workflows.
- Add the Entitlement field and Milestone Tracker to the Case page layout
Setup, Object Manager, Case, Page Layouts. Drag the Entitlement field and Case Milestones related list onto the layout. Without these, the feature exists but is invisible to agents.
Master toggle that activates the entire feature, including all related sObjects.
Automatically matches new cases to the right entitlement based on Account, Contact, or Asset.
Restricts case creation to listed EntitlementContacts on the entitlement.
The process applied to new entitlements when no explicit process is selected.
Configurable filters that narrow which entitlements appear in the case picker.
Enables Knowledge integration so articles can be attached to entitlements and cases.
- Without Auto-Population enabled, agents must manually attach entitlements. Most will not. SLA clocks never start.
- Contact Verification rejects cases from unlisted contacts. Stale contact lists become a source of customer complaints in named-contact tiers.
- The master Enable toggle activates new sObjects in the schema. Reverting hides them from the UI but does not delete the data. Plan carefully before enabling in production.
- Lookup Filters apply to the manual entitlement picker on cases. Auto-Population follows its own internal logic and ignores the filter.
- The Milestone Tracker is configured through the Case page layout, not Entitlement Settings. Forgetting to add the related list means agents do not see the SLA progress on cases.
Trust & references
Straight from the source - Salesforce's reference material on Entitlement Settings.
- Set Up Entitlement ManagementSalesforce Help
- Entitlement Management OverviewSalesforce Help
- Entitlement Settings ReferenceSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Which Salesforce Cloud includes Entitlement Settings as a key feature?
Q2. How does Entitlement Settings help support agents be more productive?
Q3. What customer experience metric would Entitlement Settings help improve?
Discussion
Loading discussion…