> For the complete documentation index, see [llms.txt](https://asigna.gitbook.io/asigna/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asigna.gitbook.io/asigna/stacks-multisig/quickstart/managing-your-vault/permissions.md).

# Permissions

By default, regardless of the confirmation threshold, all owners have the ability to create, sign, and execute transactions.

However, in some cases, you may want only specific owners to have these permissions.\
To configure this, use the **Permissions** section.

### Configure Permissions

#### ➱ **Open the Asigna multisig app**

Navigate to the Asigna multisig app in your web browser: [https://stx.asigna.io/ ](<https://stx.asigna.io/ >)

#### ➱ **Select the Vault**

On the homepage page select the Vault and open it by clicking the Vault preview card.&#x20;

#### ➱ **Access the Permissions section**

Navigate to the **Permissions** section.

On the **Permissions** page, you can view the **confirmation threshold**, the list of Vault owners along with their **addresses** and **public keys**, and information about how many owners are allowed to **create**, **sign**, and **execute** transactions.

You can also find **detailed permission settings** for each individual owner.

<figure><img src="/files/q1XcUf7JX1wgqFCrb6jw" alt=""><figcaption></figcaption></figure>

#### ➱ **Configure the Permissions**&#x20;

To change permission settings, simply click the checkbox for a **specific action** next to a **specific owner**. A checked checkbox means that the function is **enabled** for the owner. An unchecked checkbox means that the action is **not enabled** for the owner.

This way, you can configure individual permissions for each owner.

<figure><img src="/files/x4Ff2gkgq7497phfCBHH" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Please note that there are certain limitations when configuring permissions:**

* &#x20;The number of executers must be more than 0, at least 1 executer.
* The number of creators must be more than 0,  at least 1 creator.
* The number of signers must be **no less than the threshold**.
  {% endhint %}

<figure><img src="/files/OuOZj7wKycLBmm3Ml39Q" alt=""><figcaption></figcaption></figure>

#### ➱ **Confirm the changes**

After you finish configuring permissions, click the **Confirm** button. The window of the connected wallet will appear asking you to sign the message.&#x20;

<figure><img src="/files/BFIcqGIEldsAaWUqDzii" alt=""><figcaption></figcaption></figure>

#### ➱ **Complete the Signature Request**

Once you sign the message, this will create a **Signature Request**. To locate the created signature request navigate the **Transactions** section -> **Signature Request** tab.

<figure><img src="/files/cR8ixXJyFvLDyOI1fe73" alt=""><figcaption></figcaption></figure>

Ask the other owners to sign this signature request. Once the required number of signatures is collected, the new permissions configuration **will take effect**.

<figure><img src="/files/zmNjrjZLoLNKUDiQzNFr" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/oQ2mHhhyBnNgQ3tODGVY" alt=""><figcaption></figcaption></figure>

#### ➱ Check the Permissions

An owner who has restrictions on certain actions will see a tooltip if they try to perform an action they’re not permitted to.

<figure><img src="/files/MiZMFc3r4QwrfZN3QEcj" alt="" width="270"><figcaption></figcaption></figure>


---

# 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://asigna.gitbook.io/asigna/stacks-multisig/quickstart/managing-your-vault/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.