> For the complete documentation index, see [llms.txt](https://docs.tessl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessl.io/distribute/permissions.md).

# Permissions

The following permissions are required to configure and use Tessl with your repositories.

## **GitHub permissions**

You must have **`write` access**, so Tessl can create branches and open PRs.

## GitLab permissions

* A token with the scope of **`api`** is required.\* Project or Group tokens is required, webhooks will be set.
  * For Group tokens, the **`Owner`** permission is required.
  * Project tokens require **`Maintainer`** or above.

## **Tessl permissions**

* To enable GitHub or GitLab integration: **`Manager` or `Owner`.**
* To generate a plugin: **`Member`**.
* To distribute guidance across repositories: **`Publisher` or above** for the workspace.

If these permissions are missing, specific actions won’t appear in the interface.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.tessl.io/distribute/permissions.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 `build a script that syncs our docs to a CMS` 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.