Low-code works because business teams can build for themselves. That is exactly what makes governance tricky: too few rules create sprawl, too many create shadow IT. The way out is not more approvals, it is better defaults.
Environments as the first guardrail
One shared default environment for everything is the most common mistake. What works is a separation by purpose: a personal sandbox, a shared test environment and a production environment with clear ownership. Moving from test to production then becomes a deliberate decision rather than an accident.
Tie permissions to roles, not people
Automations running under a personal account break at the next role change at the latest. Production workflows need their own identity with documented ownership. That costs setup effort once and saves troubleshooting forever.
Approve connectors deliberately
Data loss prevention policies work best when they do not forbid everything but form groups instead: business data sources, general services and blocked services. What matters is that the assignment is justified and readable – otherwise people will route around it.
Visibility before control
Before you tighten rules, create an overview: which apps and flows exist, who owns them, which connections do they use? In most organisations that transparency alone resolves a large share of the risk, because orphaned solutions become visible.
Takeaway
Good governance does not feel like a brake to business teams, it feels like a prepared workplace. When the right environment, the right identity and the permitted connectors are ready from the start, durable solutions almost build themselves.
