> For the complete documentation index, see [llms.txt](https://zts-guard.gitbook.io/zts-guard-discord-bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zts-guard.gitbook.io/zts-guard-discord-bot/quick-start-guide.md).

# Quick Start Guide

The ZTS Guard Discord Bot has many features to secure your Discord server.  You will find how to setup these features to protect your admins, teams, mods, community, and your server in the command guide.  This quick start guide shows you have to get the ZTS Guard Discord Bot in your server first to do so!\
\
Only the server owner can initially set up the bot. Ensure you're logged into the server owner account (which should be the cold admin user) before proceeding with the steps below:

{% stepper %}
{% step %}

### Invite the bot using the below link

<https://discord.com/oauth2/authorize?client_id=1361428208985309356>

{% hint style="info" %}
You will need Admin, Manage Server, or be the Server Owner to invite the bot.  Ensure when you invite the bot that other bots already in your Discord Server do not block the bot from joining such as Wick.
{% endhint %}

**Nickname:** ZTS Guard

**Discord User:** ZTS Guard#0260

**Discord ID:** 1361428208985309356

<figure><img src="/files/YceGTmocwKrAhaPfGSF1" alt="" width="218"><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Bot Permissions

This is one of the rare instances where this bot will need `Admin` permissions. This means `Admin` permissions need to be granted in Server Settings > Roles > `ZTS Guard` Role, the role will be automatically created and it should have `Admin` permissions only.

{% hint style="warning" %}
ZTS Guard asks for `Admin` permissions to protect your server wholistically to stop hackers from creating new channels that may be hidden from the bot otherwise.  Giving the bot `Admin` permissions is highly recommended for the most secure setup.  However, if you choose not to do this, then you do run the risk of the `ZTS Guard` bot not being able to stop a potential scammer with a new channel.
{% endhint %}
{% endstep %}

{% step %}

### Role Hierarchy

Ensure that the `ZTS Guard` role is dragged above other roles but below the Cold Admin (Server Owner) role. This means that the Cold Admin (Server Owner) has the ability to kick the `ZTS Guard` bot whenever they like but no other bot or member should have that ability.&#x20;

ZTS Guard should not have other bots or other roles above its role due to the risk that a hacker can compromise an account, gain those roles, and then use those roles to kick the `ZTS Guard` bot. All other roles below ZTS Guard should have minimal permissions.

<figure><img src="/files/y39mTw50sDemVe6ND49a" alt="" width="188"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Channel Creation

Create the channels `#ZTS-Guard-Logs` & `#ZTS-Guard-Admin` under a team category. Make this channel visible to the below:

* **ZTS Guard Admin Channel (`#ZTS-Guard-Admin`)**&#x20;
  * **Only Team/Admin roles:** View channel, send messages, embed links, add reactions, read message history, use application commands. Do not grant any other permissions, as they are unnecessary.
* **ZTS Guard Logs Channel (`#ZTS-Guard-Logs`)**
  * **Only Team/Admin roles:** View channels, send messages, embed links, attach files, read message history, and use application commands. Do not grant any other permissions, as they are unnecessary.

Next, go to `Server Settings` > `Integrations` > `ZTS Guard` Bot > `Manage`. In the "Channels" section, place a red X next to all channels except `#ZTS-Guard-Logs` & `#ZTS-Guard-Admin`, which should have a green check. This ensures that slash commands are only used in these channels.

<figure><img src="/files/SelHdGWwEBIPEPfoDsp9" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

Go to [ZTS Guard Discord Bot Configuration & Commands](/zts-guard-discord-bot/zts-guard-discord-bot-configuration-and-commands.md) to configure the bot features!