Governance is where you manage access policies, permissions, and compliance controls for Enterprise Search. It gives you three connected tools that build on each other: you define Controls as reusable guardrails, group them into Policies that decide who or what they apply to, and review what they catch as Incidents.

Overview

Every guardrail in Enterprise Search follows the same chain: a Control is a single rule — for example, catch PII or block a topic. A Policy bundles one or more controls and applies them to a slice of your organization or your indexed content. An Incident is the logged record created whenever a control fires through a policy. You build controls, apply them through policies, and triage what they catch as incidents.

Chat and Knowledge surfaces

Every control, policy, and incident belongs to one of two surfaces, and you manage each separately:

• Chat guards the live agent as it answers. It watches LLM calls, responses, and tool use, and can look at the user's input, the agent's output, the tool name, and tool input/output. On a hit, a Chat control can Block the request or response, or Flag it for review.

• Knowledge guards your indexed content. It scans indexed material before it becomes searchable. On a hit, a Knowledge control can Restrict the matching content from search results, or Flag it for review.

For checks that can locate the match (for example, PII detection), a Chat or Knowledge control can also Redact the matched text or Mask it with a token, and let the rest through.

The same underlying idea — catch something and act on it — applies in two places: stopping a bad answer in Chat, or keeping sensitive content out of search results in Knowledge.

What's in This Section

Access and availability

Governance lives under Governance in the Enterprise Search admin, grouped into Controls, Policies, and Incidents, each with its own Chat and Knowledge tabs. It's an admin surface, so you need the relevant permissions on Enterprise Search to view and manage it.