We’re looking at enabling teams to share and reuse automation scenarios to avoid duplication. The concept is solid—why should finance and operations both build the same workflow? But I’m worried about losing control over licensing once you open this up.
With self-hosted deployments, you’re usually operating under a single enterprise license, but when multiple teams start sharing scenarios and possibly modifying them, how do you actually track what’s running where? How do you prevent teams from accidentally creating variations that bypass your governance policies?
I’m particularly interested in how teams that sell scenarios internally (or externally) manage this. Do you version control them? Do you restrict who can modify shared workflows? How do you balance flexibility for teams with the need for centralized governance?
What governance patterns have actually worked in practice? What were the mistakes people made early on that you’d recommend avoiding?