> For the complete documentation index, see [llms.txt](https://docs.bloks.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloks.io/wallet/permissions/linkauth.md).

# Link Auth

Now that a new custom permission has been created (previous guide), you need to assign to the permission what it is allowed to do using Link Auth.

## HOW TO MAKE A LINK AUTH

### 1. Select **Wallet** on the top menu.

![](/files/4gBUc8wCxcMHFUcgAZSy)

### 2. Select Keys and Permissions from the left side menu.

![](/files/oXZerdCI66yndidXEfa2)

Click on the Link Auth tab.

It will show;

* Permission (only needed for linking) - This is the name of the permission you created from Add Custom Permission (eg. In our case it was vote). 
* Contract Name - Name of the contract (eg. eosio)
* Contract Action - Name of the action (eg. claimrewards)

{% hint style="info" %}
You can find a complete list of eosio contract actions at [EOSIO on Bloks.io, Contract, and Actions. ](https://bloks.io/account/eosio?loadContract=true\&tab=Actions\&account=eosio\&scope=eosio\&limit=100)
{% endhint %}

### 3. Fill in the 3 required blank fields and click Link Auth.

![](/files/-Lmv2NN9qwpGrIZxiprI)

Once all three required fields are filled out, check the bottom to see if the correct permission you want to link authorization to is highlighted with the contract name and contract action you've input. Click Link Auth to finalize transaction. 

![](/files/-Lmv2w9Q3RGAAic2Y42d)

If you are using Scatter, you will need to click Allow action linkauth to proceed with this action.

![](/files/-Lmv3E7gp8YzfM4GIW-s)

A success message will pop up with a transaction has to confirm you've completed Link Auth.


---

# 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.bloks.io/wallet/permissions/linkauth.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.