Skip to content

W-23349167-governance-work-with-strategies-terminology #494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
luanamulesoft wants to merge 2 commits into
base: latest
Choose a base branch
from
+2 −0
Open

W-23349167-governance-work-with-strategies-terminology #494

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
578b904
docs: doc-drift branch for pr-1331_governance-work-with-strategies
luanamulesoft Jul 7, 2026
4c6131f
W-23349167 docs: clarify controls vs strategies terminology
luanamulesoft Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/ROOT/pages/exp-governance-work-with-strategies.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@

Use governance strategies to apply conformance rules and policies across agents, APIs and MCP servers. When your tenant includes *Governance* and your account has the required role, you can create, manage, and monitor these strategies to validate service design compliance, automate runtime enforcement, and maintain visibility as your portfolio grows.

NOTE: The MuleSoft interface uses two terms for strategy types: *controls* (for guardrail-based strategies) and *automated policies*. In this documentation, "strategy" refers to both types unless otherwise specified.


== Before You Begin

Expand Down