Study guide

2.1 Company Information, Fiscal Year, Business Hours, and Locale

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

2.1 Company Information, Fiscal Year, Business Hours, and Locale

Key Takeaways Explain This Topic AI

Company Information is the first stop for confirming org identity, license consumption, feature status, storage, default locale, default language, default time zone, and fiscal year behavior.

Fiscal year choices affect forecasting, reports, quotas, dashboards, and historical comparison, so changing them is a business governance decision rather than a cosmetic Setup task.

Business Hours and Holidays drive time-based service calculations such as entitlement milestones and case escalation timing, and they must match the support model that users actually follow.

Locale, language, time zone, and currency defaults shape user experience and reporting interpretation, but individual user settings can override some org defaults.

Last updated: May 2026

Admin baseline for org-wide settings

Start in Setup with Company Settings before changing user permissions, objects, automation, or applications. Company Information gives you a snapshot of the org that explains many later symptoms: edition, org ID, feature licenses, active user licenses, data and file storage, default locale, default language, default time zone, currency settings, and fiscal year configuration. On the exam and in real work, this page is often the difference between guessing and verifying.

A practical admin records the current state before changing anything. If a stakeholder says reports are wrong after a quarter close, do not start by rebuilding reports. Confirm the fiscal year, time zone, currency, and report filters. If a new region reports date confusion, compare the org default time zone with the affected users time zones and locales. If a team cannot onboard users, check license counts and feature licenses before assuming a profile or permission set issue.

Setup path map

Need Setup area Judgment check

Confirm org ID, edition, storage, and license use Setup > Company Settings > Company Information Use this before support cases, integrations, and onboarding waves.

Define fiscal periods Setup > Company Settings > Fiscal Year Standard is simpler; custom needs stronger governance and testing.

Define work schedules Setup > Company Settings > Business Hours Match service commitments, not a generic office calendar.

Define non-working days Setup > Company Settings > Holidays Confirm whether each holiday applies globally or only to a schedule.

Set default locale, language, and time zone Setup > Company Settings > Company Information Know which values are org defaults and which can be user specific.

Fiscal year configuration is a common scenario trap. Standard Fiscal Year works when the business uses ordinary calendar-aligned months and quarters, even if the fiscal year begins in a month other than January. Custom Fiscal Year supports irregular accounting patterns, such as 4-4-5 periods, but it adds complexity. Once a custom fiscal year is enabled, returning to a standard model is not a casual toggle. Treat the decision as a finance and reporting architecture decision.

Reports, dashboards, forecasts, quotas, and date filters depend on fiscal definitions. A sales leader may ask for last quarter pipeline, but that phrase only has meaning if Salesforce fiscal quarters match the finance calendar. If the fiscal year changes after records already exist, historical reporting can shift in ways that are hard for users to interpret. The safer workflow is to document the finance calendar, test report filters in a sandbox or Trailhead Playground when possible, and get signoff from finance and sales operations before production updates.

Business Hours and Holidays are equally practical. They are not just display settings. Service features can calculate elapsed time, pause time outside coverage, and evaluate milestones against the chosen business hours. A case due in 8 business hours means something very different for a weekday support queue, a 24 by 7 premium queue, and a regional queue that observes local holidays. If the business sells different support plans, the admin may need multiple business hours records and clear assignment logic.

A clean practice exercise is to create two business hour schedules in a Developer Edition org: Standard Support and Premium Support. Add a holiday to Standard Support only. Then create or inspect cases that use each support path and explain how response timing should differ. Even without building a full entitlement model, the exercise teaches why business hours are operational data. The trap is assuming one org-wide calendar can serve every support commitment.

Locale and language settings deserve the same care. Locale affects formats such as dates, numbers, names, and addresses. Language affects labels and translated UI text when translations are available. Time zone affects how date and time values display to users. A user in London and a user in California can view the same timestamp differently without any data corruption. Admin judgment means distinguishing a display issue from a stored data issue.

Currency settings can also appear in configuration scenarios. In a single-currency org, the corporate currency is straightforward. In a multi-currency org, currency behavior affects records, reports, forecasts, and integrations. Do not enable multi-currency simply because one user wants to type a different symbol. Confirm business requirements, data model impact, historical conversion needs, and reporting expectations first.

Change checklist

Capture the current Company Information values, especially org ID, default locale, default time zone, fiscal year, currency, and license counts.

Identify the business owner for the setting, such as finance for fiscal year or support operations for business hours.

Test downstream features that consume the setting, including reports, dashboards, escalations, milestones, integrations, and user onboarding.

Communicate what will change for end users, what will not change, and when the change takes effect.

Keep a rollback or correction plan, even when the setting itself cannot be reversed cleanly.

The exam angle is usually scenario judgment, not memorizing every field on the page. If the question mentions wrong quarters, look at fiscal year before changing report types. If the question mentions case response time calculated through weekends, inspect Business Hours and Holidays before editing automation. If the question mentions date display differences by region, compare user locale and time zone before opening a data quality project. Setup navigation matters because the first page you choose reveals whether you understand the platform boundary.