> 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/acknowledged-cc.md).

# Acknowledged CC

This role is given to any community member who agreed with the TEC’s Terms and conditions on the #join-here section

**To get this role you need to react to the message on the #join-here section:**

* You must ✅ this message in order to see and join any TEC channels!

*General Permissions of Server*

* View channels
* Read message history
* Use application commands

*Membership Permissions*

* Create invite
* Change nickname

*Text Channel Permissions*

* Send messages
* Embed links
* Attach files
* Add reactions
* Use external emoji

*Voice Channel Permissions*

* Connect&#x20;
* Speak
* Video
* Use voice activity

*Stage Channel Permissions*

* Request to speak


---

# 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/acknowledged-cc.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.
