Governance and Admin Controls
Define who can build, publish, and approve automation, and keep a record of every change.
Central control, local ownership
Governance and Admin Controls let a central team decide how automation is built across the company. Administrators define roles, set approval policies for publishing, and restrict which systems each department may connect.
A department builder drafts a workflow, submits it for review, and publishes it only after the required approvers sign off. The review history is stored with the workflow so a later audit can see who approved what.
Controls administrators use most
- Custom roles separate builders, reviewers, publishers, and run operators.
- Approval policies require sign-off before a workflow touches a finance or customer system.
- Change history records every edit with the author and the time.
- System allowlists limit which integrations each workspace can use.
Scale across departments
The same policies apply to every workspace in the organization. A new department inherits the governance model on day one, which keeps the program consistent as it grows from a first team to a company-wide capability.
Reviewing the record
Auditors and compliance teams can open any workflow and see its full history, including each draft, each reviewer, and each approval. Governance reports summarize which workflows are live, who owns them, and which ones have not been reviewed recently, so owners can be asked to confirm or retire them.