# Manual Verification

{% hint style="danger" %}
**This is for server moderators / owner(s) to manually verify a user in their server.**\
\
If you are an end-user trying to access a server, please refer to the [<mark style="color:blue;">**User Helpbook**</mark>](https://docs.authenticateme.xyz/en/help/verify-error) instead of the <mark style="color:orange;">**Owner's Manual.**</mark>
{% endhint %}

If you have our application in your server set up with anti alt enabled, there will be instances of users claiming to have a secondary account linked to a different user, or unable to verify due to whichever reasons- leading to the alt account error.

***

## Conditions Required

<div align="left"><figure><img src="https://1788922157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmylUMdjeDt6ueEdie39%2Fuploads%2FvnOBb561G2dQzGajOkCJ%2Fimage.png?alt=media&#x26;token=ac7318ea-bb87-4465-94aa-57be9f6ffb66" alt=""><figcaption></figcaption></figure></div>

* **The affected user&#x20;**<mark style="color:yellow;">**must attempt at least once to verify**</mark>**&#x20;and be registered in our database in order to execute a manual verification.**\
  \
  \&#xNAN;*Users who receive this error will be registered in our database, otherwise you will receive an error message noting the user is 'not registered in database'.*
* The affected user must prove they are indeed a different user from the main account.

{% hint style="danger" %}
**This executable is not a transfer of main account rights!**

If the user is using a new account to verify due to the main account being suspended or hacked etc., it is **recommended to use the Reset Verification executable instead**.
{% endhint %}

***

## How to determine a true alternative account?

We recommend you to check for the following if you intend to allow a secondary account into your server. The following list is meant to be examples and may not be exhaustive, so do be creative in your due diligence.

**Photographic Evidence**

* Separate Devices (may not be 100% true if its shared)
* Discord Tag ID handwritten with face mugshot

If you require further clarification, please do feel free to approach [AuthenticateMe Support](https://discord.gg/invite/snbauHPdR4) about this issue!

***

## Resolution

If you deem that the user's provided evidence / reasoning is satisfactory, you can do the following to verify them manually either on desktop or mobile on Discord.

#### **Desktop / Browser App**

1. Right Click on the affected user.
2. Select the <mark style="background-color:blue;">Apps</mark> option.
3. Select <mark style="background-color:blue;">Verify</mark> .

<div align="left"><figure><img src="https://1788922157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmylUMdjeDt6ueEdie39%2Fuploads%2FPQ1eUPXEDZdtczJDGBWg%2Fimage.png?alt=media&#x26;token=81284743-8e84-4c1d-af7d-dd5ba977e93f" alt=""><figcaption></figcaption></figure></div>

***

#### **Mobile App**

1. Tap on the affected user's profile.
2. Scroll down until you see <mark style="background-color:blue;">Apps</mark> .
3. Select <mark style="background-color:blue;">Verify</mark> .

<div align="left"><figure><img src="https://1788922157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmylUMdjeDt6ueEdie39%2Fuploads%2FqjGnnV7m7580Ep3YIVil%2Fimage.png?alt=media&#x26;token=eaeb449b-390d-4594-bc44-468f66657a5d" alt="" width="375"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://1788922157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmylUMdjeDt6ueEdie39%2Fuploads%2FF7y4xR7Mz9gMG2Ju9O3v%2Fimage.png?alt=media&#x26;token=57d1d9b9-8c10-469d-adb9-7565bea64c36" alt="" width="375"><figcaption></figcaption></figure></div>

***

### Completion

You will receive a confirmation text of the affected user now being verified in your server, and a receipt of it will be kept in your logs channel as well.

<div align="left"><figure><img src="https://1788922157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmylUMdjeDt6ueEdie39%2Fuploads%2FsDueF8651aqZNfRx2Xu2%2Fimage.png?alt=media&#x26;token=4f652f83-868e-4615-a151-78221a47ffb4" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://1788922157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmylUMdjeDt6ueEdie39%2Fuploads%2F2rveeaP91heBnXtywpP4%2Fimage.png?alt=media&#x26;token=fe204e45-17db-4cd0-a19a-12733a8d1c0e" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.authenticateme.xyz/en/owners-manual/servers-helpbook/manual-verification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.