Memory hook: Make work visible without widening data access accidentally.
Must remember
Tasks represent to-do work; events reserve a time interval, often with attendees. Activities link to relevant people and business records under their relationship/visibility rules. Ownership, due date, status and shared calendar settings influence how users find work; a missing activity may be a filter or permission issue.
Chatter supports feeds, mentions and groups for collaboration. Public, private and supported external/customer group access differ. Group membership does not automatically override all record permissions. Review audience before posting files or sensitive record details, especially where external users participate.
The Salesforce mobile experience uses configured navigation, supported pages/actions and visibility. Lightning page activation and device/form-factor behavior affect what a user sees. Test with the actual mobile user and permissions rather than assuming the desktop app's entire layout transfers unchanged. Branding changes appearance, not authorization.
AppExchange and AgentExchange help discover eligible packaged applications, components and AI-related offerings. Managed packages support a publisher-controlled lifecycle and upgrades; unmanaged packages generally copy editable components without the same managed upgrade path. Review publisher, installation permissions, dependencies, license and requested access before installation.
Installing a package, prompt or flow does not prove it fits the business process. Test in a suitable environment, review its data/action permissions and establish ownership for updates/removal. Publishing follows the platform's publisher and review requirements; it is not equivalent to exporting arbitrary org metadata publicly.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| A follow-up due next week | Task. |
| A scheduled customer meeting | Event. |
| Adopt vendor-maintained functionality | Evaluate a managed package and its upgrade/access implications. |
Traps
- A private collaboration group does not replace record security.
- A package installation can introduce automation and access that need review.
Active recall
1. Task versus event?
To-do item versus scheduled time-based activity.
2. Why test mobile separately?
Supported components, activation and screen constraints can differ.
3. Managed versus unmanaged package?
Publisher-managed lifecycle versus editable copied components without the same managed upgrade behavior.
4. What should package review include?
Trust, permissions, dependencies, licensing and operational ownership.
5. Why check a Chatter audience?
Posts/files may reach a different set of people from the underlying business record.