Notifications
Clear all
Topic starter
02/08/2026 11:22 am
TL;DR: Low-code AI platforms such as Microsoft Copilot Studio and Salesforce Agentforce can go live without a risk classification, monitoring baseline, or per-inference audit trail, leaving behavioural drift and hallucinations largely outside native controls, according to Openlayer. The governance gap is no longer about deployment speed but about whether organisations can evidence what their agents did, when they did it, and under which policy assumptions.
NHIMG editorial — based on content published by Openlayer: Governing Copilot Studio, Agentforce & Low-Code AI (July 2026)
Questions worth separating out
Q: How should security teams govern business-built AI agents in low-code platforms?
A: Start with discovery, ownership, and access boundaries.
Q: Why do AI agents create new risk in non-human identity management?
A: AI agents create risk because they operate as software identities with delegated authority, but many organisations do not track them with the same discipline applied to users or service accounts.
Q: What breaks when AI agents have no behavioural baseline?
A: Without a baseline, teams cannot tell whether a response is normal variation or a regression caused by prompt changes, connector changes, or model updates.
Practitioner guidance
- Inventory every production agent and connector Build a register of all low-code agents, the connectors they use, the identities they inherit, and the data classes they can reach.
- Set policy outside the builder Define approval thresholds, groundedness limits, and drift triggers in a central governance layer rather than inside each platform's native settings.
- Capture inference-level evidence Log the prompt, retrieved context, model version, policy state, and output for every inference in an immutable record.
What's in the full article
Openlayer's full post covers the operational detail this analysis intentionally leaves for the source:
- Platform-by-platform control breakdown for Copilot Studio and Agentforce, including the exact native governance features each one exposes.
- Examples of behavioural monitoring thresholds, drift indicators, and audit artefacts used to assess low-code AI agents in production.
- The compliance mapping behind EU AI Act and ISO 42001 obligations for low-code deployments that handle regulated data.
- Implementation guidance for placing an external governance layer at the API boundary without breaking existing workflows.
👉 Read Openlayer's analysis of Copilot Studio and Agentforce governance gaps →
Copilot Studio and Agentforce governance gaps: are controls keeping up?
Explore further
02/08/2026 12:40 pm
Low-code AI has created a new governance category: behavioural access control. Traditional IAM can answer who built the agent and what systems it can reach, but it cannot by itself prove that the agent behaved within policy at inference time. That gap sits between identity governance and AI governance, and it becomes visible as soon as business users can publish agents faster than security teams can review them. Practitioners should treat behavioural controls as a first-class governance layer, not an optional observability add-on.
A question worth separating out:
Q: Who is accountable when a low-code agent produces a harmful output?
A: The deployer remains accountable, not the low-code platform. Organisations need named owners for risk classification, monitoring, and evidence retention, because vendor-native logs rarely cover the full inference lifecycle. Where personal data or regulated decisions are involved, accountability must extend beyond the builder and into the operating model.
👉 Read our full editorial: Low-code AI governance gaps in Copilot Studio and Agentforce
