> For the complete documentation index, see [llms.txt](https://docs.adjutor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adjutor.io/adjutor-api-endpoints/transactions-and-balances-with-kolo/permission-scopes.md).

# Permission Scopes

The Kolo API uses certain scopes to control access to various resources and actions on a customer's account. Each scope allows specific operations on the associated resources.&#x20;

Below is a detailed explanation of the available scopes, including the corresponding endpoints and how they work.

## **Scope Descriptions**

| Scope                 | Description                                        |
| --------------------- | -------------------------------------------------- |
| `transaction:list`    | Allows listing all transactions.                   |
| `transaction:view`    | Allows viewing details of a specific transaction.  |
| `transaction:update`  | Allows updating a specific transaction.            |
| `bank_account:list`   | Allows listing all bank accounts.                  |
| `bank_account:view`   | Allows viewing details of a specific bank account. |
| `bank_account:add`    | Allows adding a new bank account.                  |
| `bank_account:update` | Allows updating a specific bank account.           |
| `bank_account:delete` | Allows deleting a specific bank account.           |
| `bank_account:sync`   | Allows synchronizing a specific bank account.      |
| `profile:view`        | Allows viewing the user's profile.                 |

Depending on the use case, make sure to EXPLICITLY state what scopes you are requesting for in your request.&#x20;

{% hint style="warning" %}
Note

If any of these scopes are not clearly defined in your initial URL, you won't be able to carry out any of these actions.
{% endhint %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adjutor.io/adjutor-api-endpoints/transactions-and-balances-with-kolo/permission-scopes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
