> For the complete documentation index, see [llms.txt](https://docs.mimu.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mimu.bot/autoresponder/resources/autoresponder-examples/manager-moderation-commands/self-verification-system.md).

# self-verification system

### ✎ verification system

1. set up your permissions
   * in order to make a verification system, you need to first lock all your channels to hide them from users who just join.
   * as this is mostly a discord-help thing, if you need guidance on how permissions work, [click here](<https://support.discordapp.com/hc/en-us/articles/206029707-How-do-I-set-up-Permissions >).
   * then, make a role that can't view the rest of the server and remember to set up all the channels so that this particular role cannot view the rest of the server, but can still view your rules / landing channel!
   * confused on how to set up permissions? check out the [template we've prepared](https://discord.new/JBKDfcGeRMhK). it includes 2 main roles (mod & verified member role), 4 main categories (info - everyone can see, verify category - unverified can see, main chat - verified can see, and mod corner category - only mod can see).


---

# 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.mimu.bot/autoresponder/resources/autoresponder-examples/manager-moderation-commands/self-verification-system.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.