Guide Agent Behavior with AI Governance Policies (Developer Preview)

Agentforce Vibes supports AI governance policies configured in DevOps Center, your org’s centralized repository for AI governance. When your Salesforce admin enables governance, Agentforce Vibes fetches the active policies, and applies them as part of the agent configuration for every session. Salesforce admins set policies, which end users can’t modify or turn off.

When you send a prompt, Agentforce Vibes identifies which active policies are relevant and applies them as instructions to the agent. The agent can explain which policies it applied: ask why it wrote the code a certain way and it cites the relevant policy.

  • You must turn on and configure DevOps Center Governance in your org. See Configure AI Governance Policies for Salesforce admin setup instructions.
  • At least one policy must be active in your org for policies to appear in Agentforce Vibes.

Active policies appear read only in the Policies section of the Agentforce Vibes Toolkit, listed separately from Rules. Each policy row shows the policy ID and name. Click a row to view the full policy definition. To update policies, contact your admin. You can’t edit or turn off org policies from Agentforce Vibes.

If Agentforce Vibes can’t load policies, it proceeds without blocking chat:

  • Fetch failure: No governance policies are applied for that session. Agentforce Vibes logs the failure and continues.
  • Authentication failure: A notification appears: “Couldn’t load policies; re-authenticate org.” Re-authenticate and retry, or continue without governance for that session.
  • No policies are configured: If no policies are active in the connected org, the agent responds: “No governance policies are currently loaded.” Chat proceeds normally without governance policies applied.

In all cases, your chat session remains functional.

  • The system applies policies as system prompt instructions. Agentforce Vibes doesn’t verify or enforce that the LLM followed the policies. Policy application is best-effort at the prompt level.
  • Policy changes don’t apply mid-session. Policy changes and org switches don’t take effect in active chat sessions. Updates made in DevOps Center Governance, and policies from a newly connected org, only apply when you start a new chat. If you switch orgs mid-session, open a new chat to ensure that the correct policies are loaded.
  • This release doesn’t support policy scoping. Org-level, project-level, team-level, and user-level scoping, versioning, and delta fetches aren’t available.
  • This release doesn’t govern Model Context Protocol (MCP) servers, skills, and tools. Governance applies to policies only.