> 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/setup-community-link-checker.md).

# Setup Community Link Checker

{% hint style="success" %}
This feature is available for **free** to any server — no premium subscription required.
{% endhint %}

This ZTS Guard Discord Bot feature allows community members to verify the legitimacy of links, X accounts, and Discord users directly in your server that has been configured by admins or team members within the Discord Server.

## Setup Community Link Checker

{% stepper %}
{% step %}

### Create the channel

Create a channel called `#community-link-checker`.

If this is the **only feature** you're using (meaning the bot does not have Admin permissions), add the `ZTS Guard` Bot role to the channel with these permissions only:

* View Channels
* Send Messages
* Send Embedded Messages
* Read Message History

Add only roles you want to see this channel and interact with it with the below permissions:

* View Channels
* Read Message History
  {% endstep %}

{% step %}

### Open the Community Checker menu

Within the `#zts-guard-admin` channel, type `/setup` → `Community Checker` , from here you will see all the options to add to the specific sections for community members to check against.
{% endstep %}

{% step %}

### Add official links

* **Manage Links** — Add all official URLs for your project/team (one per line)
* **List Links** — Verify all entries are correct

{% hint style="info" %}
This list is completely separate from the Anti-Link allow list.
{% endhint %}
{% endstep %}

{% step %}

### Add X accounts

* **Manage X Accounts** — Add all official X (Twitter) handles
* **List X Accounts** — Verify all entries are correct
  {% endstep %}

{% step %}

### Add Discord roles

* **Manage Discord Roles** — Add a role; all members with that role are automatically added to the verified list via their username
* **List Discord Roles** — Verify all entries are correct

{% hint style="info" %}
Recommended to Add **Admin**, **Team**, and **Mod** role(s) only.
{% endhint %}
{% endstep %}

{% step %}

### Send the embed

One you have completed the above, within the  `Community Checker` Menu select `Send.` Add an optional message if you'd like to explain what this embed is or any additional information is or just click `Submit` to skip, and then select the `#community-link-checker` channel as the destination channel.  Once this is selected you will now see the embed for community members to check against.\
\
It is recommend to check and test anything you submitted to ensure you have submitted the information correctly. 
{% endstep %}
{% endstepper %}

***

## What community members can do

The below actions are actions that community members can do with the embed the ZTS Guard Discord Bot sent.  This allows them to quickly see a list of all official and verified information or to have them paste in a link and compare to see if its on the official and verified list or not.\
\
This feature is crucial to providing a quick and simple way to see if your community members are interacting with official and verified team members or scammers.

| Action                 | Description                                                     |
| ---------------------- | --------------------------------------------------------------- |
| **List Links**         | View all official links                                         |
| **Check Link**         | Manually verify if a link is official                           |
| **List X Accounts**    | View all official X accounts                                    |
| **Check X Account**    | Manually verify if an X account is official                     |
| **List Discord Roles** | View all verified admin, team, or mod roles                     |
| **Check Discord user** | Verify if a Discord user is a verified team member via username |