Study guide

10.1 New Sales Org Setup Integrated Lab

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

10.1 New Sales Org Setup Integrated Lab

Key Takeaways Explain This Topic AI

A new sales org setup should connect company settings, user access, object configuration, sales process design, data readiness, automation, and reporting.

Use profiles and permission sets deliberately, then verify with Login As, record pages, list views, and report visibility from the user perspective.

Sales process labs should include expected observations and failure modes, not only the happy path of creating fields and stages.

Admins should build in a sandbox or Trailhead Playground first, document choices, and move production changes through a controlled release path.

Last updated: May 2026

Lab scenario: launch a small sales org

A software company is moving a ten-person sales team into Salesforce. Leadership wants account and opportunity tracking, a clean lead intake process, weekly pipeline reports, and basic activity visibility. The admin has a Trailhead Playground or sandbox, two sample sales users, one sales manager, and a small CSV of accounts, contacts, and open opportunities. The goal is not to build everything Salesforce can do. The goal is to make a working sales foundation that is secure, testable, and easy to explain.

Start with org controls. Go to Setup > Company Information and confirm locale, default currency, time zone, fiscal year, licenses, and storage. Go to Setup > Fiscal Year only if the company uses a nonstandard fiscal calendar. Confirm business hours if sales handoffs or follow-up service work will depend on working time later. These settings shape forecasts, reports, dates, currency display, and user experience. A common failure mode is building reports before confirming fiscal periods, then discovering that quarterly dashboards do not match finance expectations.

Create the people model next. Use Setup > Users > Users for user records, Setup > Profiles only for broad baseline access, and Setup > Permission Sets for additive permissions. Use a Sales User permission set for opportunity, lead, account, contact, task, and report access. Use a Sales Manager permission set for dashboards, forecast management if used, and broader record visibility through roles or sharing. Do not clone large profiles casually. A new org often looks simple, but profile sprawl becomes hard to unwind.

Build area Setup path Expected observation Failure mode to watch

Company settings Setup > Company Information Dates, language, currency, and fiscal periods match the business Reports show wrong fiscal periods or currency assumptions

Users and access Setup > Users , Setup > Permission Sets Sales reps can create leads and opportunities but cannot administer the org Users receive system permissions because a profile was overused

Role hierarchy Setup > Roles Manager can see direct team records when sharing model depends on hierarchy Private sharing blocks manager reports unexpectedly

Sales process Setup > Object Manager > Opportunity > Fields & Relationships and Sales Processes Stages, probability, and record types reflect how the team sells Required fields block early-stage opportunities or allow closed deals with missing data

Reports Reports tab and Setup > Report Types Pipeline reports match expected owner, stage, amount, and close date filters Report folders or sharing hide data from the intended users

Configure the sales data model. In Object Manager, review Account, Contact, Lead, and Opportunity fields before adding custom fields. Add only fields that support decisions, automation, reporting, compliance, or required business process. Example additions might include Account Tier, Lead Source Detail, Competitor, Sales Motion, and Renewal Risk. Prefer picklists when reporting consistency matters. Use help text for fields that users might interpret differently. Avoid creating a custom object for simple opportunity attributes unless the relationship truly needs its own lifecycle.

Build the sales process with Setup > Object Manager > Opportunity > Fields & Relationships > Stage and Setup > Sales Processes if the org needs different stage paths by record type. For a basic new sales org, one opportunity record type may be enough. Add stages such as Qualification, Discovery, Proposal, Negotiation, Closed Won, and Closed Lost. Confirm probability defaults and forecast categories. Then configure Path from Setup > Path Settings so reps see key fields and stage guidance on the opportunity record page.

Add guardrails only where the business has committed to them. A useful validation rule might require Loss Reason when Stage equals Closed Lost, or require Primary Contact before Closed Won. Test validation rules from a sales rep user, a manager user, Data Loader or import context, and any flow context. The failure mode is a rule that looks correct in a demo but blocks imports, renewals, or manager corrections. If exceptions are legitimate, consider a custom permission used sparingly instead of telling users to enter fake data.

Load sample data only after the schema and access model are understood. Use Setup > Data Import Wizard for a guided small load of accounts and contacts, or Data Loader for a more realistic upsert exercise with record IDs or external IDs. Before loading opportunities, export the source file version, map owners to active users, and make sure lookup values are stable. Expected observations include successful rows, clear error files, and opportunities visible in list views by owner and manager.

Failure modes include invalid picklist values, inactive owners, missing required fields, and duplicate accounts caused by name-only matching.

Create a simple adoption surface. Build a Sales app with the App Manager, include Home, Leads, Accounts, Contacts, Opportunities, Tasks, Dashboards, and Reports, then assign it to the right profiles or permission sets. Edit Lightning record pages so key information is visible without clutter. Use Dynamic Forms where appropriate on supported objects, but do not hide required information behind too many conditions. Add list views such as My Open Opportunities, Closing This Month, and New Leads Today. A user should be able to start work without asking which tab to use.

Finish with analytics. Build a pipeline report grouped by owner and stage, an open leads report grouped by source, and a simple dashboard with pipeline by stage, opportunities closing this month, and lead conversion trend if sample data supports it. Store reports in a folder shared to the sales team and managers. Then test as a sales rep. The rep should see only appropriate records and reports. The manager should see team-level information.

If the dashboard numbers differ from list views, check report type, filters, running user, folder sharing, record sharing, and whether the report includes converted leads or closed opportunities.

Review prompts before the quiz:

Which settings would you confirm before building reports in a new sales org?

Which permissions belong in a permission set instead of a cloned profile?

Which validation rules protect closed opportunities without blocking early pipeline creation?

How would you prove that a sales manager can see the right records and not too much data?

What sample import errors would you deliberately test before a production data load?