Member Verification

Sending Discord invites is extremely easy, but it can quickly become confusing when a lot of players use your link or when you want to allow guild applicants to join your Discord. The member verification feature helps here. After you activate it, Aleeva asks every user who joins why they are there. Based on their answer, Aleeva grants them rights, informs guild officers, or assigns them guest permissions.

How it works

When someone joins, Aleeva messages them and asks why they are there. They pick one of the options you enabled, Aleeva checks their Guild Wars 2 account where the option calls for it, and assigns the matching roles.

Aleeva automatically kicks joining members if they do not respond to the question. The default wait is 10 minutes, and you can set anything from 5 minutes to 24 hours. This keeps users out of your server who join for no reason.

If a member is not able to complete the verification, the owner, an Aleeva Administrator, or an Application Officer can skip it for them with the command . Aleeva then lets the member through without assigning any roles, so you hand those out yourself.

The options

You choose which of these a joining member can pick. Only the ones you enable are offered, and the member sees them as a short list to select from.

Member of the guild

The member states they belong to your Guild Wars 2 guild. Aleeva checks their stored API keys against the guild roster and only grants access if one of the accounts is really a member.

If they have no API key stored yet, Aleeva tells them to run and press Verify again. If none of their accounts is in the guild, they are turned down and can try again.

On success, Aleeva either applies your Guild Rank Mapping so the member lands on the role matching their in-game rank, or, when rank mapping is off, assigns the single member role you configured.

This option needs your server to be connected to a guild through a guild API key. Until that key is set, the option shows as "API key needed" and cannot be enabled.

Application

For players who want to apply to your guild. Aleeva does not check anything here. It tells the applicant that your officers will get in touch, and notifies everyone with the Application Officer role that someone joined and applied.

Guest

For visitors who just want to hang around. Aleeva assigns the guest role you configured.

If Guest Management is active, it takes over from here: the guest role is granted for the duration you set, and Aleeva tells the guest when their stay ends if automatic kicking is on.

WvW relationship

The member states they play on your WvW world. Aleeva checks their stored API keys and grants access when one of the accounts is on the right world. You decide whether only your main world counts, or the linked worlds as well.

On servers with WvW Alliance Verification enabled, this option becomes an alliance check instead and uses that feature's configuration.

As with the guild option, a member without a stored API key is asked to add one first, and accounts on the wrong world are turned down.

Setup

Member Verification is server-based, so you activate it with the command. Select Member Verification and choose what you want to allow. Depending on your selection, you need to configure some basic things, and after that you can activate the feature.

From the configuration menu you toggle each of the four options. Aleeva asks for anything it still needs, such as the role for verified guild members, the guest role, or the Application Officer role it should notify.

The same menu holds two more buttons:

• Set allowed verification time. How long Aleeva waits before kicking a member who never answered. Between 5 and 1440 minutes.
• Edit guild key. The server's Guild Wars 2 guild API key, which the guild member option needs.