> For the complete documentation index, see [llms.txt](https://token-engineering-commons.gitbook.io/tec-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-engineering-commons.gitbook.io/tec-handbook/processes/discord-roles.md).

# Discord Roles

Every single day, more and more contributors join our Discord server, and we try to keep things organized by adding roles/labels to members' accounts. 

We prepared this section to provide transparency on the roles/labels that are assigned to people who join the TEC Discord. Different roles have different levels of permissions in the TEC Discord and they are described below starting from the Admin  (which has all the Discord permissions) to the New Member (which has a very limited amount of permissions). 

If you have any questions about the roles you are assigned to, or wish to add a role to your name, please reach out to one of the @Stewards within the #Transparency text channel on our Discord Server.<br>


---

# 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://token-engineering-commons.gitbook.io/tec-handbook/processes/discord-roles.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.