Lesson 4 of 29 · All lessons
Salesforce Platform Administrator
0 of 29 complete
1ADM-201 Exam Overview
  1. 1.1ADM-201 Exam Overview
2Configuration and Setup15%
  1. 2.1Company settings, fiscal year, business hours, currency, and defaults
  2. 2.2Declarative user interface configuration
  3. 2.3User setup, licensing, and lifecycle
  4. 2.4Organization security and identity controls
  5. 2.5Sharing model, record access, and folders
  6. 2.6Profiles, permission sets, groups, and muting
3Object Manager and Lightning App Builder15%
  1. 3.1Objects, schema, and relationship architecture
  2. 3.2Fields, formulas, and field dependencies
  3. 3.3Page layouts, Lightning pages, record types, and actions
4Sales and Marketing Applications10%
  1. 4.1Leads, opportunities, sales processes, and Path
  2. 4.2Campaigns, campaign members, and lead assignment
  3. 4.3Sales productivity, scoring, forecasting, and territories
5Service and Support Applications10%
  1. 5.1Case management, queues, and case assignment
  2. 5.2Support processes, auto-response, escalation, and Einstein for Service
6Productivity and Collaboration10%
  1. 6.1Tasks, events, and activity management
  2. 6.2Chatter, groups, and internal or external collaboration
  3. 6.3Salesforce mobile app configuration and user experience
  4. 6.4AppExchange, packages, AgentExchange, and Flow awareness
7Data and Analytics Management17%
  1. 7.1Importing, updating, transferring, deleting, exporting, and backing up data
  2. 7.2Matching rules, duplicate rules, and validation rules
  3. 7.3Reports and report types
  4. 7.4Sharing, folders, and report visibility
  5. 7.5Dashboards, components, filters, subscriptions, refresh, and licensing
8Automation15%
  1. 8.1Selecting automation tools for a business scenario
  2. 8.2Flow capabilities, types, configuration, and order of execution
  3. 8.3Approval processes, criteria, approvers, and outcomes
9Agentforce8%
  1. 9.1Agentforce capabilities, use cases, security, and permissions
  2. 9.2Agent Builder, prompts, instructions, testing, and conversation preview

Section 2 · Configuration and Setup · 15% of exam

2.3 User setup, licensing, and lifecycle

2 min read Updated Nov 13, 2026

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.

Check your knowledge

Answer exam-style Configuration and Setup questions with answers and explanations.

Practice Configuration and Setup
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator simulator: same number of questions, same time limit.

Get Complete Access