Double Counter Docs
News, Updates, and OutagesDouble Counter DashboardGet Double Counter Premium
  • Getting Started
  • Setting up the bot
  • Configuration
  • Configuration, cont.
  • Double Counter + Onboarding
  • Analytics
  • Lens
  • Additional Commands
  • Pro version
  • Doogle
  • Alt Detections & VPN Intrusions
  • Common troubleshooting
  • Privacy Policy
  • Terms of Service
Powered by GitBook

Tellter SAS © 2025. The Double Counter name, logo and designs are the registered trademarks or service marks of Tellter SAS.

On this page
  • Role overview
  • Setting up category / channel permissions
  • Setting up Onboarding to provide the Onboarded role
  • Setting up the verification channel

Double Counter + Onboarding

Configuring Double Counter to work alongside Discord's Onboarding is possible, but will require some tinkering with permissions to ensure users are verified prior to getting access to your server.

PreviousConfiguration, cont.NextAnalytics

Last updated 8 months ago

If your server has used the in the past, you are required to disable that in the 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.

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.

We do not provide help in case you get alt detected when doing this kind of testing.

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.

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.

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.

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.

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.

Dashboard
Unverified role
The roles used in our example. For Onboarding we use the Onboarded role, for Double Counter we use the Verified User role.
Category permission showing the @everyone role permission. This configuration allows the channel to be counted as "open" by Discord when setting up Onboarding.
Permissions that are enacted when the user has finished Onboarding, but have yet to verify with Double Counter.
Permissions that are enacted for users who are fully verified using Double Counter.
One of your Pre-join Questions will have to be a required question so the user can't skip it. It may have a different text and more than one answer if you so choose.
The answer we use to provide the Onboarded role.
This image showcases the permissions for everyone. These will be overwritten by the Onboarded permissions.
Here we allow the Onboarded role view permissions, but deny send messages as we don't want this chat flooded.
After the user verifies, the channel is subseqently hidden from them to avoid any confusion about their state of verifiation.