> For the complete documentation index, see [llms.txt](https://docs.inverter.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inverter.network/concepts/protocol-concepts/module-library/authorizers/token-gated-role-authorizer.md).

# Token Gated Role Authorizer

#### Module Category: Authorizer

Token Gated Role Authorizer allows governing permissions for roles and access rights for contract interactions based on the ownership of specified tokens.

With Token Gated Role Authorizer, token addresses can be whitelisted for specific roles in addition to whitelisting a user or a contract address. Token based whitelisting gives all the holders of those tokens the relevant permissions. Token addresses can be ERC20, NFTs, or other token standards.

## Module Functions:

#### Parameters to set:

**Role Setup:** Grant roles that are gated by token ownership.

**Token Specification:** Specifies which tokens are linked to the roles.

**Threshold:** Sets the minimum token balance required to access specific roles.


---

# 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.inverter.network/concepts/protocol-concepts/module-library/authorizers/token-gated-role-authorizer.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.