When the Organization-Wide Default (OWD) for an object is set to Private, users can only see records they own or those shared with them. While the Role Hierarchy automatically grants " upward " visibility (managers see what subordinates own), it does not naturally allow for " lateral " visibility or visibility across different branches of the hierarchy. To solve this, a Platform Administrator should use Sharing Rules. Sharing Rules allow the admin to create exceptions to the Private OWD based on record ownership or specific criteria.
For example, the admin can create an " Owner-based Sharing Rule " that shares all records owned by the " East Coast Sales " role with the VP of Sales (or a Public Group the VP belongs to). This provides a scalable way to grant the necessary visibility for reporting without making the data public to the entire company.
Sharing Rules are a core security feature that ensures the right people have access to the right data while maintaining the principle of least privilege.

Mobile Homeis a customizable landing page for the Salesforce mobile app that acts as the default "start page" for users. It allows administrators to add various "cards" or "widgets," including reports, pinned records, and upcoming events. By enabling and configuring Mobile Home, a Platform Administrator can place a specific Report card (such as "Top Opportunities") at the very top of the screen, ensuring it is the first thing users see upon opening the app. While adding the Reports tab (Option A) or Dashboards tab (Option D) allows users to find the information, it does not automatically present specific report data on the home screen. The "Today" feature (Option B) focuses on calendar events and tasks rather than customized reporting data17.

According to Agentforce best practices, action instructions must be highly specific regarding the action ' s purpose, the expected goal, and the conditions under which it should be triggered. Option D is the strongest set of instructions because it defines the Action (Update shipping address), the Goal (Modify address on a record), and a clear Constraint/Guardrail (Only use when the user explicitly requests it). This prevents the AI from accidentally triggering a data change based on a vague inquiry. Option B is also good but more restrictive than necessary unless the business logic specifically forbids updates during active orders. Option D provides the best balance of context and intent, ensuring the Large Language Model (LLM) understands the " why " and " when " of the action.

In Salesforce, validation rules use formulas to verify if the data entered by a user meets specific criteria before saving the record1. To check the value of a picklist field like LeadSource, the ISPICKVAL() function must be used, as picklist fields do not support standard text operators like " = " in validation formulas2. The requirement is to block the save if LeadSource is " Other " but the Source__c text field is empty3. The ISBLANK() function effectively checks if a text field contains no data4. Therefore, the correct logic uses AND() to trigger the error message only when both conditions are met: the picklist is set to " Other " AND the text field is blank5. Option A is incorrect because it treats a picklist like a text field6. Option B and D use NOT() logic, which would trigger errors in the wrong scenarios.

The Kanban view provides a visual representation of a set of records, such as an opportunity pipeline, organized by a specific field like " Stage " . It allows sales teams to see all their deals as cards in columns.
The primary benefit of Kanban is its " drag-and-drop " functionality, which lets users move a card from one column to another to automatically update the stage, effectively " moving opportunities forward " with minimal effort. While reports (Option A) and dashboards (Option B) provide visual summaries, they do not allow for the interactive, one-click record updates that the Kanban view offers11. Standard list views (Option D) show data in a grid format which is less visual for tracking pipeline progress compared to the column- based Kanban layout.