Section 2 · Configuration and Setup · 15% of exam
2.3 User setup, licensing, and lifecycle
Exam objective
Given a scenario, set up and maintain users, including usernames, locales, working hours, licenses, feature licenses, inactive users, and login methods. A Salesforce username must be globally unique and is not necessarily the user’s email address. Locale and time zone affect formats and displayed times; working hours can support features that schedule or calculate work. Check these values when a user reports incorrect dates, times, or regional formatting.
A user license determines the baseline Salesforce products and capabilities available to that user. Feature licenses can provide additional capabilities when supported by the user license. Match the license to job responsibilities before creating the user; available licenses are finite and some features cannot be assigned to every license type. Users with business history are generally deactivated rather than deleted. Before deactivation, transfer ownership of records or important responsibilities, review scheduled work and integrations, and confirm whether the user is referenced by automation. Deactivation prevents future login while preserving historical attribution.
Additional concepts
Identity, preferences, and access are different
A username identifies a Salesforce login and must be unique across Salesforce. Locale and time zone control regional display choices. The user license sets a capability boundary, while profiles, permission sets, and record sharing determine different parts of access. A user who can log in can still lack permission to use a particular object or feature.
Before activating or deactivating
When onboarding, assign a supported license and required feature access, then verify the correct login method and user preferences. When offboarding, transfer record ownership where needed, check references in integrations or automation, and deactivate the account. Deactivation preserves historical record attribution and should be coordinated with operational handoff.
An employee leaves the company. The administrator transfers open opportunities and relevant records, reviews automation ownership, then deactivates the account instead of deleting it.
A login problem may involve username, identity provider, user status, license, or verification settings. Diagnose the layer before changing permissions.
Key takeaways
- Usernames are unique; locale, time zone, and working hours influence user experience and business processes.
- Licenses set capability boundaries; feature licenses add supported functionality.
- Deactivation preserves records and audit history; review ownership and automation first.
