> For the complete documentation index, see [llms.txt](https://web3key.gitbook.io/security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://web3key.gitbook.io/security/setup/tutorial.md). # Tutorial ### Role Hierarchy After inviting the bot to your server, ensure that your roles are arranged similar to the structure below. * Inf3Mini (Backup system) * Infinit3Guard (Main system) * Owner * Administrator * Moderator * Verified/Holder/etc In this structure, the backup bot has a role holding highest authority, with the main system beneath. A hierarchy similar to this structure is needed to ensure that Infinit3Guard's protections execute without issue. ### Setup The Infinit3Guard setup process was created with simplicity in mind. To begin, simply start by doing: `/start` You will be able to select ✔️ or ❌ to answer the questions provided. If you have made a mistake at any time during the setup process, proceed to the end of the setup and execute the process again to update your configuration. ### Option breakdown #### Webhook Protection Restricts the creation of new webhooks. If a new webhook is created, it will automatically be deleted. This action can be bypassed using the bypass command (default or custom set). If bypassed, a webhook is created in place of the deleted one. #### Role Permission Protection Restricts the granting of administrator permissions to non-previously administrator roles. During the setup process, current administrator roles are recorded. In the event of a compromise, if the attacker tries to grant a role administrator permissions, this will be revoked. This action can be bypassed using the bypass command (default or custom set) #### User Role Protection If a user is granted a role that has admin, this role will be revoked. This action can be bypassed using the bypass command (default or custom set) #### Link Filter If a user sends a link in any text channel that is not on the whitelist of links, this link will be removed. #### Fake Permissions {% hint style="info" %} If enabled, and with NO role permissions set, this option is a ***very*** strong protection. {% endhint %} If enabled, server users will be able to be granted role specific permissions (manage channels, manage messages, mention everyone, etc). A user who has been granted permissions may redeem the permission, and in doing so they will be granted a temporary role with this permission. After the time window has closed, this role will be deleted. #### Log Channel Creation If yes, a new log channel will be created which all event logs will be sent to. If no, a channel with "admin" in the name will be looked for to take place as the default log channel. #### Bypass Command This option allows you to set your own custom bypass command instead of the default one provided by Infinit3Guard. This can be anything from a string of characters to a full sentence (spaces, punctuation). --- # 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://web3key.gitbook.io/security/setup/tutorial.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.