Field Level Security

💬 In plain words: If a user generates a response via Prompt Builder but lacks Field-Level Security (FLS) read access to a specific field used in that template, Salesforce does not throw an error. Instead, the field simply resolves to a blank space, and the AI model smoothly writes around the missing data. This silent failure is one of the most dangerous and easily overlooked behaviors when building AI prompts in Salesforce.

💬 In plain words: An agent can only do what its user can do. Field-level security applies, sharing rules apply, and there is no override. The only question is which user, and that is decided by the agent type. 📌 Example: A Meridian rep asks the Employee Agent about a meter on an account they cannot see. The agent says it cannot find it. The meter exists — the rep just has no access. Concept This is the single most useful fact in Agentforce, and the most commonly got wrong. Employee Agent: Runs as the logged-in user. Service Agent: Runs as its own dedicated user ( default_agent_user ). Field-level security (FLS) is enforced normally. Sharing rules are enforced normally. Apex actions inherit this through with sharing and WITH USER_MODE queries. The failure mode is silent. There is no error, no exception, and no error banner. The agent simply says it cannot help, in a perfectly polite sentence. That s...