Overview
Productivity and Collaboration covers four tool sets. Activity management means tasks and events, how they relate to people and records, and what settings such as Shared Activities change. Chatter brings feeds, feed tracking and groups, including how internal and external users reach a group. The Salesforce mobile app covers how Lightning pages, app navigation and component visibility behave on phones, and how the app can be branded. AppExchange covers finding and installing packaged apps, the managed versus unmanaged distinction, and newer listings such as prompts on AgentExchange and flows.
The section exists because adoption depends on these tools. Users judge Salesforce by how easily they log calls, collaborate and work on a phone, and admins often extend the org with AppExchange rather than building. It connects to Configuration and Setup for UI and access, and to Automation for packaged flows.
How it's tested
Most questions here are capability checks set in a short scenario: can this feature do what the user asked, and what is the simplest configuration. Expect choices between task and event, group types, mobile page options and package types. The right answer usually uses a standard setting and respects a limit stated in the scenario.
-
Right activity type
A user needs to track work with or without a time slot, related to one or many people, and you choose task, event or a Shared Activities setting.
-
Who can see the group
A collaboration request involves internal staff, external customers or confidential topics, and the group type and customer access decide the answer.
-
Install or build
A requirement fits an AppExchange solution, and the managed or unmanaged nature of the package decides who maintains and upgrades it.
Sales reps on phones say the opportunity page is cluttered with a chart only useful on desktop. The administrator does not need a separate mobile page or a custom component. In Lightning App Builder, the chart component can use a form-factor visibility filter so it shows on desktop only, while the same page serves both. Recognizing component visibility by device as a standard option rules out answers that rebuild the page.
Objectives 4
Official objectives from the Salesforce outline, in outline order.
5.1 Describe the capabilities of activity management (tasks, events).Logging work and meetings against people and records.
- What it means
- Tasks are to-do items with a due date and status but no time slot, while events are calendar entries with a start and end time and optional invitees. Both relate to a person through the Name field (a lead or contact) and to a record through Related To (such as an account, opportunity, case or a custom object that allows activities).
- What to understand
- Custom objects show activities only when Allow Activities is enabled on the object. Shared Activities lets one task or event relate to multiple contacts, and once enabled it cannot be turned off. When the activity org-wide default is Controlled by Parent, a user's access to an activity follows their access to the related record.
- How it shows up
- A rep logs one meeting attended by several contacts and wants it on each contact's timeline, and the answer is an event with Shared Activities enabled.
- Common confusion
- A lead cannot be in the Name field together with a Related To record, because leads are not linked to other records until conversion; candidates expect both fields filled for a lead.
5.2 Describe the features of Chatter (groups, accessibility to groups, internal/external users).Feeds, feed tracking and the three group types.
- What it means
- Chatter provides feeds on records, users and groups, with feed tracking that posts updates when chosen fields change. Groups are Public (anyone internal can see and join), Private (members only see posts; others request to join) or Unlisted (hidden from non-members and search). Private groups can be set to allow customers so invited external users can participate.
- What to understand
- External users in a customer-enabled group see only the groups they are invited to and cannot browse the rest of the org's Chatter. Record feeds respect record access, so posting on a record does not expose it to users who cannot see the record. Feed tracking is configured per object and field.
- How it shows up
- A project team must collaborate with a client's staff without exposing internal discussions, and the answer is a private group that allows customers, with the client invited.
- Common confusion
- Unlisted is not the same as private-with-customers; unlisted hides a group from internal users who are not members, while customer access is a separate setting on private groups.
5.3 Describe the capabilities of the Salesforce mobile app (Lightning page, modifying the app, browser, app menu, visibility, branding mobile app, build launchpad).How pages, navigation and branding behave on phones.
- What it means
- The Salesforce mobile app uses the same Lightning apps, record pages and actions as desktop, with navigation items and the app menu deciding what users reach. Lightning App Builder previews pages by form factor, and components can be shown or hidden by device, field values or permissions. Branding options let an org present its own look, and admins can build launchpad-style shortcuts so mobile users reach common items quickly.
- What to understand
- Most mobile changes are made by configuring the shared Lightning app, page and actions rather than a separate mobile build. Actions appear in the mobile action bar from the page layout or dynamic actions, so a missing mobile action is usually a layout or action configuration issue. Opening Salesforce in a mobile browser and using the installed app are both supported ways to work on a phone.
- How it shows up
- Field reps need a simpler record page and quick access to two actions on their phones, and you use form-factor visibility and action placement rather than custom code.
- Common confusion
- Candidates think mobile requires separate page layouts; one Lightning page can serve desktop and phone with visibility filters by form factor.
5.4 Identify use cases for AppExchange applications (awareness of managed or unmanaged packages, who is allowed to publish, prompts on AgentExchange, flows).Extending the org with packaged apps, flows and agent assets.
- What it means
- AppExchange is Salesforce's marketplace for apps, components, flow solutions and consulting partners, and AgentExchange extends it with agent-related assets such as prompt templates and actions. Packages are managed (protected components, publisher upgrades) or unmanaged (fully editable, no upgrades). Listings are published by Salesforce partners and are subject to Salesforce's partner and security review processes.
- What to understand
- Install and test in a sandbox first, choose who the package is installed for, and review the permissions it requests. Managed packages fit when you want the publisher to maintain and upgrade the solution; unmanaged packages fit when you want a starting point you will own and customize yourself.
- How it shows up
- A team wants a ready-made solution with ongoing vendor updates, and the answer is a managed package installed and tested in a sandbox first.
- Common confusion
- Unmanaged packages are often assumed to receive upgrades; once installed they become the org's own metadata, and new versions do not update them.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Task vs. event
A task is a to-do with a due date and status; an event is a calendar entry with start and end times and optional invitees.
- Remember
- Choose event whenever a specific time slot or attendees matter.
- Tested as
- Basic activity questions and logging scenarios.
- Trap
- Logging a scheduled meeting as a task and losing calendar visibility.
-
Name and Related To fields
Name links an activity to a lead or contact; Related To links it to an account, opportunity, case or another object that allows activities.
- Remember
- When Name holds a lead, Related To must stay blank.
- Tested as
- Questions about why an activity cannot be linked to both a lead and an opportunity.
- Trap
- Expecting a lead and an opportunity on the same activity.
-
Allow Activities
A setting on a custom object that enables tasks and events to relate to its records.
- Remember
- Without it, the custom object has no activity timeline and cannot be chosen in Related To.
- Tested as
- Scenarios where users cannot log calls on a custom object.
- Trap
- Changing activity permissions on the profile when the object setting is the gap.
-
Shared Activities
A setting that lets one task or event relate to several contacts.
- Remember
- It cannot be disabled once enabled.
- Tested as
- Meetings or calls with several contacts that should appear on each timeline.
- Trap
- Creating duplicate activities for each contact.
-
Chatter group types
Public groups are open to internal users, private groups show posts only to members, and unlisted groups are hidden from non-members.
- Remember
- Only members see posts in private and unlisted groups.
- Tested as
- Collaboration scenarios with confidential topics.
- Trap
- Using a public group for sensitive discussions because members can still be controlled.
-
Groups that allow customers
Private Chatter groups configured so invited external users can join and participate.
- Remember
- External members see only the groups they are invited to.
- Tested as
- Partner or client collaboration scenarios.
- Trap
- Expecting customers to browse the internal Chatter directory.
-
Feed tracking
Configuration that posts to a record's feed when tracked fields change.
- Remember
- Set per object and field, so only chosen changes appear.
- Tested as
- Requests to make important field changes visible to followers.
- Trap
- Confusing feed tracking with field history tracking for audit reporting.
-
Form-factor visibility
A Lightning App Builder component visibility filter that shows a component on desktop, phone or both.
- Remember
- One Lightning page can serve every device.
- Tested as
- Mobile page clutter or simplification scenarios.
- Trap
- Building a separate page or custom component for mobile.
-
Mobile action bar
The set of actions shown on records in the Salesforce mobile app, drawn from layout or dynamic actions.
- Remember
- Missing actions on mobile are usually a layout or action configuration issue.
- Tested as
- Field users who cannot find a quick action on their phones.
- Trap
- Assuming mobile needs separate code to expose an action.
-
Managed vs. unmanaged package
Managed packages protect their components and receive publisher upgrades; unmanaged packages are fully editable but never upgraded.
- Remember
- Choose managed for vendor-maintained solutions and unmanaged for templates you will own.
- Tested as
- AppExchange installation scenarios.
- Trap
- Expecting an unmanaged package to update when the publisher releases a new version.
-
AgentExchange
Salesforce's marketplace for agent-related assets such as prompt templates, actions and agent solutions.
- Remember
- Treat installed agent assets like any package: review permissions and test in a sandbox.
- Tested as
- The guide names prompts on AgentExchange as an AppExchange use case.
- Trap
- Assuming installed prompts work without granting users the needed permissions.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Public vs. private vs. unlisted Chatter groups
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Public group | Any internal user can see posts and join | Open discovery and membership | Using it for confidential projects |
| Private group | Only members see posts; others request to join | Can be set to allow customers | Assuming members' external guests see everything |
| Unlisted group | Hidden from non-members and search | Membership by invitation only | Confusing hidden with customer-enabled |
Managed vs. unmanaged package
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Managed package | Publisher-owned components in a namespace | Upgradable; protected code cannot be edited | Expecting to modify its Apex |
| Unmanaged package | Editable copy of components | Not upgradable after install | Waiting for vendor upgrades that never arrive |
Task vs. event
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Task | To-do with due date and status | No time slot or invitees | Logging a timed meeting as a task |
| Event | Calendar entry with start and end | Supports invitees and calendar display | Using it for undated follow-up work |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Profile fix for missing activities
- What candidates pick
- Grant activity permissions in a permission set so users can log calls on a custom object.
- Why it looks right
- Missing features often trace back to permissions.
- Why it's wrong
- If the custom object does not have Allow Activities enabled, no permission makes activities available on it.
Clue to watch for Activities work on standard objects but not on one custom object.
-
Duplicate tasks for multiple contacts
- What candidates pick
- Create one task per contact to record a meeting with several people.
- Why it looks right
- It guarantees each contact shows the activity.
- Why it's wrong
- Shared Activities relates one activity to many contacts, avoiding duplicates and inconsistent records.
Clue to watch for One meeting or call involved several contacts.
-
Unlisted for clients
- What candidates pick
- Create an unlisted group so a client can participate without internal users seeing it.
- Why it looks right
- Hidden sounds safest for external collaboration.
- Why it's wrong
- External access depends on a private group allowing customers; being unlisted does not invite or enable external users.
Clue to watch for The scenario names customers, clients or partners joining the group.
-
Custom mobile build
- What candidates pick
- Create a custom Lightning web component or separate app for phone users.
- Why it looks right
- Mobile feels like a different platform.
- Why it's wrong
- The Salesforce mobile app reuses Lightning apps, pages and actions, and form-factor visibility handles most differences declaratively.
Clue to watch for The request is only to simplify or reorder what phone users see.
-
Unmanaged for vendor support
- What candidates pick
- Install an unmanaged package because it allows customization.
- Why it looks right
- Customization freedom sounds valuable.
- Why it's wrong
- Unmanaged packages do not receive upgrades, so the vendor cannot maintain them; a managed package fits when ongoing updates are required.
Clue to watch for The requirement mentions vendor updates or support.
-
Install straight into production
- What candidates pick
- Install a promising AppExchange app directly in production to save time.
- Why it looks right
- The listing looks reviewed and popular.
- Why it's wrong
- Packages add metadata and request permissions that can affect users and automation, so install and test in a sandbox first.
Clue to watch for The scenario asks for the recommended first step.
Answer framework
For productivity and collaboration questions, confirm the standard capability and its limit before choosing a configuration.
- Identify the tool in play: activity, Chatter feed or group, mobile app experience, or AppExchange package, and note any stated limit such as external users, phones only or vendor updates.
- For activities, choose task or event by time slot and attendees, and check Allow Activities and Shared Activities settings.
- For Chatter, choose the group type by who may see posts, and use a private group that allows customers for external participants.
- For mobile, adjust the shared Lightning app, page, actions and form-factor visibility before considering custom builds.
- For AppExchange, decide between managed and unmanaged by who will maintain the solution, then install and test in a sandbox with reviewed permissions.
Practice question
Want more like this? The Salesforce Admin practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Begin with activities, because they are the most frequently used feature in this section. In a practice org, log tasks and events against leads, contacts and opportunities, enable activities on a custom object, and note which field combinations Salesforce allows. Then turn on Shared Activities in a test org only, remembering it cannot be reversed.
Move to Chatter next. Create one group of each type, invite a test external user to a private group that allows customers, and check what each user can see. Configure feed tracking on a few fields and compare it with field history tracking.
Commonly underestimated areas are the mobile app and AppExchange. Install the Salesforce mobile app or use the phone preview in Lightning App Builder, hide a component by form factor, and confirm where actions appear. Read an AppExchange listing closely, noting package type, publisher and security review, and browse AgentExchange to recognize what kinds of agent assets are offered.
Afterwards, practice short capability questions and say the limit aloud before choosing, such as cannot disable, cannot upgrade or members only.
FAQ
How much of the exam is Productivity and Collaboration?
This section is 10% of the exam, which suggests around six of the 60 scored questions as a planning estimate.
Is this an easy section?
The concepts are familiar to most users, but questions hinge on specific limits such as which fields an activity can link, who sees a private group, and whether a package can be upgraded. Treat it as a section of details.
What do I need to know about Chatter for external users?
Know that customers can join only private groups that allow customers, that they see only the groups they are invited to, and that record feeds still follow record access.
Do I need to configure the mobile app separately from desktop?
Usually not. The mobile app uses the same Lightning apps, pages and actions, so you adjust navigation, form-factor visibility and actions in the shared configuration.
What is AgentExchange?
It is Salesforce's marketplace for agent-related assets such as prompt templates and actions, which the guide lists as an AppExchange use case. Treat its installs like other packages by reviewing permissions and testing in a sandbox.
How long should I study this section?
About 10 to 15 hours is a reasonable editorial estimate, most of it hands-on with activities, Chatter groups and the mobile preview.
How does this section relate to Configuration and Setup?
The app menu, global actions and Lightning App Builder settings from Configuration and Setup are what shape the mobile experience, and sharing settings decide what Chatter feeds expose.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 5 knowledge
You have covered tasks and events, Chatter groups and feeds, the Salesforce mobile app and AppExchange packages. Check whether you can spot the limiting detail in quick capability questions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Salesforce Admin AI tutor Get any concept explained your way