> 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/access-and-responsibilities.md).

# Access and responsibilities

Map Lleverage access to real operational responsibility rather than granting broad access by default.

Access should follow the work people are responsible for.

A useful access review starts with the operational role, then maps that to Lleverage projects and permissions. Avoid starting from the product menu and giving people access simply because a control exists.

## Questions to answer

For each group of users, establish:

* which Projects they need to enter;
* whether they only operate existing solutions or also build and change them;
* which external systems their work may reach;
* whether they should be able to configure credentials, Connections or project settings;
* which Requests they may be asked to resolve;
* what should happen when they leave the team or change role.

Use **Control → Members** for the current project membership and role mechanics. Organisation ownership has broader authority and should be treated accordingly.

## Keep system authority separate from product access

A Lleverage user may have access to a Project while the underlying Connection carries authority in another system. Review both sides.

For example, adding a person to a Project is not the same decision as allowing that Project to send email, update an ERP record or call an external API. Connection scope and credential ownership are part of the access model too.


---

# 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/access-and-responsibilities.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.