# Double Counter + Onboarding

{% hint style="danger" %}
If your server has used the [Unverified role](https://docs.doublecounter.gg/double-counter-en/configuration-cont.#unverified-role) in the past, you are required to disable that in the [Dashboard](http://dashboard.doublecounter.gg) prior to setting up Onboarding with Double Counter. During Onboarding, the user will have to pick up a role acting similar to the Unverified role, however it will *not* be removed after verification completes.

It is highly recommnded to set the bot to "Interactive" mode now, as it will be required when the setup is completed.
{% endhint %}

{% hint style="warning" %}
If you want to test your Onboarding configuration with an alt account, please make sure to manually verify your alt using `/manverify` instead of verifying using a verification link when you get to that step.&#x20;

We do not provide help in case you get alt detected when doing this kind of testing.&#x20;
{% endhint %}

## Role overview

Before setting up your permissions, you need to either create a new role, or re-use an existing "Unverified" role if you have that. Keep in mind that this role will **not** be removed by Double Counter from the user post-verification, but you are free to find alternative ways to do that if you so choose.&#x20;

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2FqEZy4WLTCqt3GP6bWEoi%2FScreenshot%202024-07-20%20at%2020.34.48.png?alt=media&#x26;token=be6e73f7-621d-4c00-aaf6-edf1ac20e5c0" alt=""><figcaption><p>The roles used in our example. For Onboarding we use the Onboarded role, for Double Counter we use the Verified User role.</p></figcaption></figure>

## Setting up category / channel permissions

In the provided example, we are configuring the category permissions for a given category of channels. The channels within this category has its permissions linked to the category. Every server has a different setup, so you will have to adapt it to your needs. The same principle works for individual channel permissions. In our example the new role we created is called **Onboarded,** and we will refer to it as that during the entire guide.&#x20;

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2FaxBS6zWHAYnQOlsdHBD8%2FScreenshot%202024-07-20%20at%2020.23.12.png?alt=media&#x26;token=33ab4977-7887-47ac-a744-d0934a4df264" alt=""><figcaption><p>Category permission showing the @everyone role permission. This configuration allows the channel to be counted as "open" by Discord when setting up Onboarding. </p></figcaption></figure>

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2F3WFyMF6mR1YHOMswCD3k%2FScreenshot%202024-07-20%20at%2020.23.49.png?alt=media&#x26;token=d7bdc8d0-34fa-47aa-9b17-8e57e97520ba" alt=""><figcaption><p>Permissions that are enacted when the user has finished Onboarding, but have yet to verify with Double Counter.</p></figcaption></figure>

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2Fw4d2hBbhH0jVULSO6iDb%2FScreenshot%202024-07-20%20at%2020.24.16.png?alt=media&#x26;token=f4d61df2-7ea9-42a8-8b3c-707b9b9da175" alt=""><figcaption><p>Permissions that are enacted for users who are fully verified using Double Counter.</p></figcaption></figure>

## Setting up Onboarding to provide the Onboarded role

Going into your Onboarding setup, you see sections for Pre-join Questions and Post-join Questions. We only care for the **Pre-join Questions** in this guide.&#x20;

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2FzCMTTGbzeRQGsMqYz25x%2FScreenshot%202024-07-20%20at%2020.40.24.png?alt=media&#x26;token=a259024f-2830-4341-969c-bfc8e5b36925" alt=""><figcaption><p>One of your Pre-join Questions will have to be a <strong>required</strong> question so the user can't skip it. It may have a different text and more than one answer if you so choose. </p></figcaption></figure>

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2FRwxSB5A9hF7dQYsWM2Xt%2FScreenshot%202024-07-20%20at%2020.44.17.png?alt=media&#x26;token=624dd9c4-5676-4130-8530-a932e3846a3a" alt=""><figcaption><p>The answer we use to provide the Onboarded role. </p></figcaption></figure>

{% hint style="warning" %}
If you have a Pre-join Question with more than one answer to pick from, make sure the user at least receives the Onboarded role regardless of which answer they choose. Failing to do so will potentially give the user access to your server without being verified by Double Counter.&#x20;
{% endhint %}

## Setting up the verification channel

Once you've set up the permissions in all channels/categories, you can set up the last and final channel needed in this tutorial - the verifiation channel. The Double Counter Dashboard refers to this channel as the Channel for verifying users. In this channel, you should run `/panel` which provides users with a method of verifying themselves. The permissions for this channel should differ from your normal channels, as we want to hide it for users that are already verified.&#x20;

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2Ffi6jnLrZ8OEpMxdHUknx%2FScreenshot%202024-08-20%20at%2014.04.09.png?alt=media&#x26;token=378577dc-e0dd-4b7a-9f5f-36e5e2d16ee2" alt=""><figcaption><p>This image showcases the permissions for everyone. These will be overwritten by the Onboarded permissions.</p></figcaption></figure>

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2FEbPaPh2kbo6NSvR7G41U%2FScreenshot%202024-08-20%20at%2014.05.35.png?alt=media&#x26;token=216e527b-4602-4623-977b-371fe7f4fcc0" alt=""><figcaption><p>Here we allow the Onboarded role view permissions, but deny send messages as we don't want this chat flooded. </p></figcaption></figure>

<figure><img src="https://2331364482-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M9cl3qQ2jFWQHKbymKg%2Fuploads%2FOaDsMqari4KWb7SsYt96%2FScreenshot%202024-08-20%20at%2014.05.44.png?alt=media&#x26;token=47b5f518-d00f-41d5-ab19-a980d8b2fa02" alt=""><figcaption><p>After the user verifies, the channel is subseqently hidden from them to avoid any confusion about their state of verifiation.</p></figcaption></figure>
