# Getting Started

<div data-full-width="false"><figure><img src="https://i.imgur.com/L00Vzms.png" alt=""><figcaption></figcaption></figure></div>

## Dashboard Access

{% hint style="danger" %}
In order to gain access to the dashboard, any authorized user **must** have a role with either `Admin` or `Manage Server`. This does not apply to **the owner of the server**.&#x20;
{% endhint %}

## Bot Minimum Required Permissions

Prior to setting up the bot in your server, it is imperative that you have given the bot proper server permissions. These permissions are as follows:

* [x] View Channels
* [x] Manage Roles
* [x] Send Message
* [x] Embed Links (For verification /panel)
* [x] Manage Messages
* [x] Manage Channels
* [x] Use Application Commands
* [x] Ban Members (*in conjunction with Alt Auto-ban*)
* [x] Add Reactions
* [x] Kick Members (*in conjunction with Auto Kick*)
* [x] Manage Server
* [x] Create Instant Invite

For a streamlined setup, granting `Administrator` is the recommended option.

{% hint style="info" %}
If you're not giving Double Counter Administrator permissions, make sure to give it "View Channel", "Send Messages", "Embed Links" and "Manage Messages" permissions in both your Channel for verifying users" and "Channel for logging".
{% endhint %}

## Role Hierarchy

In order for the bot to administer the `@verified` and/or `@unverified` role(s), the bots highest role must be above these roles. It is recommended to place the bots role nearest the top.

{% hint style="danger" %}
Please make sure the Double Counter bot permission role is **above the verified & unverified role(s)** in the role list.
{% endhint %}

## Configuring Channel Permissions

Depending on your server's configuration, there are **two different cases**.

* You already use a **bot that assigns a role from a reaction click**. For example, a `#rules` channel with a reaction role to access the server: **case 1**.
* You don't use such system, **members can directly access your server upon joining it**: **case 2**.

{% tabs %}
{% tab title="Case 1" %}

1. Remove the `read_messages` permission to the `@everyone` default role on the reaction-role channel and add that permission to the verified role set up above.
2. Set up the `@everyone` role (no actual role) so it can only see your welcome channel set up above.

{% hint style="info" %}
It is always recommended that you provide guidance to your users on exactly how the verification process will work.
{% endhint %}
{% endtab %}

{% tab title="Case 2" %}

1. Give **all users in your server** the unverified role. Several bots can do that, Carl for example.
2. For **each public channel in your server, remove the** `read_messages` **permission to** `@everyone` and **add it to the verified role.**
3. Set up the `@everyone` role (no actual role) so it can only see your welcome channel set up above.

{% hint style="info" %}
It is always recommended that you provide guidance to your users on exactly how the verification process will work.
{% endhint %}
{% endtab %}
{% endtabs %}

## Things to Keep in Mind...

* Double Counter is <mark style="color:red;">**not retroactive**</mark>. This means members already in your server at the time you add the bot are **not recorded** in our database and will not be blocked when using an alt account. The bot will prevent **future members** from using a VPN or an alt.&#x20;
* Please double check your configuration. If a user can **bypass** the Double Counter verified role (consequently the verification link) to access the server, **the protection becomes useless**. Please ensure any newcomer **must click the link to access your channels.**

## Curious about how the bot works and want to test it out?

We understand that people are curious and want to see how the bot works. It's human nature. However, because the bots database cannot be modified or edited, if you accidentally verify an alt account first, that will become your main account from the bots perspective. It is imperative that you exercise caution when "testing" with an alt account.