Permissions
Add granular control to your operations.
Permissions are a crucial component for ensuring the secure and collaborative management of assets within your Squad. Users can establish granular levels of access for Squad members by leveraging permissions, thereby limiting the possibility of wrongdoing within a Squad.
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.
![](https://docs.squads.so/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fd2JBpU0MXarT2yD7TPuS%252FPermissions.png%3Falt%3Dmedia%26token%3Ddab300d1-ce1b-4d37-8c2a-de0ed09ae3bc&width=768&dpr=4&quality=100&sign=4fdcc445&sv=1)
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.
Please note that you must always have sufficient amount of members with “Voter” and “Executor” permissions to successfully reach confirmation threshold set for your Squad and execute the created transactions.
Last updated