For the complete documentation index, see llms.txt. This page is also available as Markdown.

Governance

Define ownership, access and human responsibility around the operational work that Lleverage performs.

Governance is about the operating model around Lleverage, not just the settings inside the product.

For an IT owner or process owner, the core questions are:

  • who is accountable for the process and its outcome;

  • who may build or change automation;

  • who may use the resulting Agent, apps and Requests;

  • which decisions must remain with people;

  • who reviews recurring exceptions and failures;

  • how access changes when people or responsibilities change.

Lleverage provides controls for membership, credentials, Requests and execution. Your organisation still decides the policy those controls implement.

Two useful layers

Platform governance is configured in Lleverage: membership, project roles, Connections, Secrets, published Workflows and Request assignment.

Operational governance is organisational: process ownership, approval authority, segregation of duties, escalation expectations and who decides when an automation should change.

Keeping those layers explicit avoids treating a product permission as if it were the whole governance model.

Last updated

Was this helpful?