Study guide
8.6 Productivity and Collaboration Case 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
8.6 Productivity and Collaboration Case Lab
Key Takeaways Explain This Topic AI
Integrated productivity scenarios require admins to connect activities, collaboration, mobile, list views, Path, reporting, and package governance.
The best admin solution usually combines standard configuration, security review, pilot testing, training, and adoption metrics.
Support workflows should distinguish configuration defects, permission gaps, data quality issues, user training needs, and process design problems.
Hands-on practice should prove that the workflow works for real users, not only for a system administrator in Setup.
Last updated: May 2026
Scenario: field productivity without losing control
Cloud Kicks has a familiar Salesforce adoption problem. Sales reps meet customers in the field, but follow-up tasks are inconsistent. Managers ask for pipeline updates in spreadsheets because opportunity stages are stale. Support escalations happen in email threads, so product specialists miss context. Executives want mobile access to key account updates. A director also found an AppExchange package that promises automated meeting notes and wants it installed immediately.
A weak admin response would be to add required fields everywhere, enable every notification, and install the package in production. A strong admin response starts by separating the problems. Sales needs a reliable next-step and meeting-log workflow. Managers need trusted list views, Kanban, Path, and dashboards. Support needs governed collaboration tied to cases. Executives need a mobile page with high-value fields. The AppExchange request needs evaluation, not impulse installation.
Symptom Likely admin response Success evidence
Reps forget follow-up Task quick action, required next step at stage gates, overdue-task list view Fewer overdue tasks and more opportunities with next activity.
Meetings are not visible Event or activity logging guidance, activity timeline placement, email/calendar support path Completed activities visible on accounts and opportunities.
Pipeline stages are stale Kanban, Path key fields, manager list views, validation at meaningful transitions Stage updates match manager reviews and reports.
Escalations happen in email Private Chatter group or case feed process with specialists Case decisions are visible on the record.
Executives need mobile review Mobile Lightning page, compact layout, and focused navigation Executives can review key account and case data quickly.
Package request is urgent Sandbox evaluation, security review, license and data access assessment Approved decision with documented risk and support owner.
The admin should define a pilot. Choose one sales team, one support escalation group, and a small executive audience. Create a baseline report for current overdue tasks, opportunities without next steps, cases escalated by email, and mobile support tickets. The baseline prevents vague adoption debates later. If the pilot improves those measures, the admin has evidence for broader rollout.
Configuration should stay standard where possible. Add or refine object-specific actions for Log Meeting, Create Follow-Up Task, and Update Next Step. Place the activity timeline and high-value related lists on account and opportunity pages. Configure Path for opportunity stages with key fields and concise guidance. Create list views for My Stalled Opportunities, Opportunities Missing Next Step, Overdue Follow-Up, and Escalated Cases Awaiting Specialist Response. Use Kanban for opportunity stage review if validation and automation support drag updates.
Build, test, support, and measure
Testing must use representative permissions. A system administrator can usually see every field, every action, and every record, which hides adoption defects. Test as a field sales rep, sales manager, support specialist, product expert, and executive. Confirm that each persona can open the right records, use the right actions, see only appropriate fields, receive useful notifications, and complete the workflow from desktop and mobile. If a user cannot complete the process, identify whether the problem is security, page design, validation, automation, or training.
Pilot implementation checklist:
Confirm business owners for sales follow-up, support escalation, mobile executive review, and package evaluation.
Create or update actions, compact layouts, Lightning pages, Path, list views, and Kanban views in a sandbox or playground where practical.
Configure Chatter group or case feed practices for escalations, including membership, mentions, and sensitive-information guidance.
Test activity logging, task ownership, event visibility, mobile page behavior, and notification settings as each pilot persona.
Review reports for overdue tasks, completed activities, stale opportunities, escalated cases, and mobile support issues.
Evaluate the AppExchange package separately with security, data access, licenses, connected app needs, and uninstall risk.
Train users with the exact pilot records and workflows they will use.
Hold a post-pilot review and retire anything that created noise without improving work.
The AppExchange request should not be ignored, but it should be handled through governance. If the meeting-note package records sensitive customer conversations, sends data to an external service, uses AI, creates tasks automatically, or logs emails, the admin should involve security and business owners. AI or automation can assist productivity only when permissions, data retention, accuracy review, and user accountability are defined. Users should understand when they must verify generated notes or suggested follow-ups before relying on them.
Support planning is part of the lab. Create a short troubleshooting matrix for the help desk or admin queue. Missing action: check page assignment, layout, profile, permission set, and action placement. Missing activity: check related record, owner, sync or logging path, activity settings, and visibility. Too many notifications: check feed tracking, group settings, mentions, and user preferences. Kanban update blocked: check validation rules, required fields, record type, and automation. Package access issue: check package license, permission set, connected app, and object permissions.
Measurement should focus on behavior. A dashboard showing login counts is not enough. Better measures include opportunities with next activity, tasks overdue by owner, completed meetings by account segment, cases waiting for specialist response, Chatter escalation posts with resolution notes, mobile-created activities, and package pilot error rates. The admin should share these measures with managers so adoption is reinforced by the operating rhythm.
Study trap: integrated scenarios rarely have a single magic feature. The correct admin answer often combines several standard tools and a support plan. If a scenario includes mobile complaints, stale data, collaboration confusion, and an AppExchange request, slow down and classify each problem before choosing a solution.