> For the complete documentation index, see [llms.txt](https://docs.empymanager.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empymanager.com/guides/how-to-implement-a-verification-system.md). # How to implement a verification system There are more options to make EmpyManager compatibly to a verification system. ### Channel Syncing (Premium) [Channel Syncing ](https://docs.empymanager.com/server/configuration#channel-sync)will make all your channels inherit from the category they are created in. In this way you can give permissions only to certain users to view/join the Temporary Channels. ### Discord's Verification System Instead of using channel syncing, we suggest to free users to enable Discord's verification system. It is safer than any other bot's system and users won't be able to join channels without being verified. ### Remove Global Permissions If none of the above solutions fits you, you can always remove the "View Channel" permissions from @everyone in your server's global settings and then add it only in the channels that non-approved users should be able to see. Then, you should grant the "View Channel" permissions to your **Verified** role. In this way, all the non-specified channels (including EmpyManager's channels) will be hidden by default to non-verified users. --- # 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.empymanager.com/guides/how-to-implement-a-verification-system.md?ask=&goal= ``` `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.