> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/governance.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/administer-and-govern/governance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.