> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/navigating-your-squad/members/permissions.md).
# Permissions
Add granular control to your operations.
Permissions are crucial for ensuring the secure and collaborative management of assets within your Squad. By leveraging permissions, users can establish granular levels of access for Squad members, thereby limiting the possibility of wrongdoing within a Squad.
{% hint style="info" %}
Permissions are only accessible to users with a Squads Business or Enterprise plan. Learn more about our pricing and subscription plans [here](/main/getting-started/pricing.md).
{% endhint %}
**Members in Squads have 3 types of roles:**
* **Proposer** - only allows creating transactions in the Squad without allowing to vote or execute them
* **Voter** - only allows signing transactions in the Squad without allowing to create or execute them.
* **Executor** - only allows executing transactions in the Squad without allowing to create or sign transactions.
Permissions
When members are added to a Squad during deployment, they are granted all three permissions. Permissions can be reassigned for existing members after the Squad deployment, and can be assigned for newly added members when launching a transaction to add them.
{% hint style="warning" %}
Please note that you must always have a sufficient amount of members with “Voter” and “Executor” permissions to successfully reach the confirmation threshold set for your Squad and execute the created transactions.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.squads.so/main/navigating-your-squad/members/permissions.md?ask=&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.
