> For the complete documentation index, see [llms.txt](https://legacy-docs.aragon.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.aragon.org/developers/tools/the-basics/permissions.md).

# App permissions

{% hint style="success" %}
Use the <mark style="color:purple;">**Access Control List (ACL)**</mark> to control who can access your app's functionality.
{% endhint %}

## How does it work?

The ACL essentially just contains a set of who has permission to execute an action in an Aragon app and who can re-grant or revoke that permission.

Most generally, an *Entity* can hold the permission to call a function protected by *Role* in an *App*, and their permission is managed by a *Manager*, who can revoke or regrant that permission.

### Example

Now let's say we have these 3 apps:

* A *Token Manager* app, which represents BOB token holders and forwards all their intents to another app
* A *Voting* app, which executes any arbitrary action after a voting of BOB token holders passes
* A *Finance* app, which controls the funds of the organization

| Entity        | App     | Role       | Manager |
| ------------- | ------- | ---------- | ------- |
| Token Manager | Voting  | OPEN\_VOTE | Voting  |
| Voting        | Finance | WITHDRAW   | Voting  |

With the simple mapping in the table above, we have done the following:

* Given permission to BOB token holders, using the *Token Manager*, to open votes in the *Voting* app
* Given permission to the *Voting* app to withdraw funds from the *Finance* app

{% hint style="info" %}
We have achieved a fully democratic way of withdrawing funds in Ethereum! :tada:
{% 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://legacy-docs.aragon.org/developers/tools/the-basics/permissions.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.