Cloud Kicks has implemented an Employee Agent to answer benefits questions for its employees. How should a Platform Administrator prevent the agent…

The most fundamental and secure method to control data access in Salesforce is through the core security model. The Employee Agent, like any user or process on the platform, operates within a specific user context. By ensuring that the permissions (via Profiles or Permission Sets) and Field-Level Security (FLS) for this context restrict access to the CEO's sensitive health plan data, the administrator guarantees the agent cannot read or retrieve this information. This approach prevents exposure at the data layer, which is more robust than relying on application-level instructions or training data.

A. Configure assignment rules to assign the agent to employee data.

Assignment rules are used for automatically routing records like Leads and Cases to users or queues; they do not control data visibility or access permissions.

C. Modify the agent’s instructions and guardrails to block questions related to the CEO’s health plan.

While guardrails are a useful feature, they are a secondary control. Relying solely on instructions is less secure than preventing data access at the platform level via permissions.

D. Train the agent on employee health plans instead of the CEO’s health plan.

This is important for knowledge-based AI, but it doesn't prevent the agent from accessing and retrieving live, restricted Salesforce record data if it has the underlying permissions to do so.

1. Salesforce Documentation - Einstein Copilot Security: "Einstein Copilot is built on the Salesforce Platform, so it inherits all the security and access controls of your Salesforce org... Copilot respects all of your existing user permissions and field-level security." This confirms that platform-level security (Permissions, FLS) is the primary control mechanism.

Source: Salesforce Help, "Einstein Copilot," Section: Einstein Copilot Trust and Security.

2. Salesforce Documentation - Control Access to Fields: "You can restrict access to fields by using field-level security. Field-level security settings control whether a user can see, edit, and delete the value for a particular field on an object." This directly supports using FLS to hide sensitive data like the CEO's benefits.

Source: Salesforce Help, "Control Access to Objects," Sub-section: Control Access to Fields.

3. Salesforce Security Guide: This guide details the layered approach to data security in Salesforce, emphasizing that object permissions, record-level sharing, and field-level security are the foundational controls that determine what data any user or automated process can access.

Source: Salesforce Security Guide, PDF Document, "Chapter 2: Data Security," pp. 7-10.