Audience: Discord server administrators, ARVEE users, and Discord reviewers evaluating ARVEE's Server Members Intent use case.
ARVEE is a Discord RPG and community-management application offering configurable server administration, welcome messages, member roles, verification, automations, moderation, and analytics through its web dashboard.
The Server Members Intent (GUILD_MEMBERS) allows ARVEE to receive real-time Discord membership events and perform administrator-configured actions when people join servers, complete membership screening, or leave.
These actions happen automatically. Members do not need to execute commands or interact with ARVEE to trigger them.
Why ARVEE requires Server Members Intent
ARVEE uses three Discord Gateway events:
| Discord event | Purpose |
|---|---|
guildMemberAdd | Detect new members joining a server |
guildMemberUpdate | Detect membership changes, particularly completion of membership screening |
guildMemberRemove | Detect members leaving or being removed |
These events are necessary for features that must respond to membership changes without user interaction.
Slash commands and buttons cannot fully replace these events, because they require explicit interaction and cannot independently notify ARVEE when a member joins or leaves.
ARVEE requests this intent for configured server-management features, not for monitoring member presence or reading ordinary chat messages.
Features powered by member events
| Feature | Trigger | What ARVEE does |
|---|---|---|
| Welcome messages | Member joins or completes screening | Automatically sends a configured greeting |
| Automatic join roles | Member joins or completes screening | Assigns eligible, manageable server roles |
| Goodbye messages | Member leaves | Sends a configured departure message |
| Member automations | Member joins or leaves | Runs approved workflows, such as sending a message |
| Anti-raid monitoring | Member joins | Detects unusual join bursts and alerts staff |
| Event logs | Member joins or leaves | Records membership event summaries |
| Server analytics | Member joins or leaves | Updates aggregate membership statistics |
| Private welcome DMs | Eligible member joins or completes screening | Sends an optional Premium welcome DM |
These features are individually configurable. A server owner can choose which modules to enable.
Installing ARVEE or enabling the RPG does not automatically enable every administrative feature.
Live demonstration: Automatic welcome messages
The following screenshot captures ARVEE sending an automatic welcome message in a real Discord server when a member joined.

View the original full-resolution screenshot
What the screenshot demonstrates
- ARVEE posted a welcome message in the Discord server.
- The welcome was triggered by an actual member joining, rather than a manual dashboard test.
- ARVEE's message appeared before Discord's own system join notification.
- The screenshot captures the visible result of ARVEE's automatic member-join functionality.
This demonstrates the intended use case for Server Members Intent: reacting to membership events and delivering configured onboarding messages without requiring commands.
Evidence clarification: The screenshot is from an actual join event. The displayed order of messages provides supporting context, but event logs or a continuous recording can provide additional independent verification of the automatic trigger.
This screenshot specifically illustrates welcome delivery. Automatic role assignment and other member-event functions should be demonstrated separately when required.
Configuring automatic welcome messages
Server managers can configure welcome messages through the ARVEE website.
- Open ARVEE's server dashboard.
- Sign in using Discord.
- Select a server where you have Manage Server permission.
- Open Welcome & goodbye.
- Enable welcome messages.
- Choose a destination channel.
- Enter the welcome message and configure its format.
- Save the changes.
- Join the server with a separate ordinary Discord account to test the automatic greeting.
ARVEE must have the necessary channel permissions, including View Channel and Send Messages.
Styled welcome messages
ARVEE also supports an optional advanced welcome builder with configurable:
- First-time member greetings.
- Returning-member greetings.
- Goodbye messages.
- Destination channels.
- Accent colors and Components V2 presentation.
When the advanced welcome builder is enabled, its configuration takes priority over the basic welcome message.
Membership screening
If Discord membership screening is enabled, ARVEE can wait until the member finishes screening before carrying out applicable onboarding actions.
This prevents a member who has not completed the server's membership requirements from receiving onboarding roles prematurely.
Duplicate-message protection
ARVEE uses a database-backed delivery claim to reduce duplicate welcome messages.
The current implementation includes a ten-minute deduplication window. If Discord's message acknowledgement is uncertain, ARVEE avoids blindly repeating delivery because the message may already have been posted.
A Send test welcome dashboard action can verify the configured channel and message formatting. However, only a real member join or screening-completion event demonstrates automatic Gateway event handling.
Automatic join roles
ARVEE can automatically assign configured server roles when eligible members join or finish membership screening.
Configuration
- Open the ARVEE server dashboard.
- Select Roles.
- Enable Automatic join roles.
- Choose the eligible roles.
- Save the configuration.
- Test by joining with a normal Discord member account.
Role limits
| Server access | Supported join roles |
|---|---|
| Free | Up to 5 |
| Eligible Premium | Up to 10 |
Permission safeguards
Automatic role assignment respects Discord's role hierarchy.
- ARVEE needs Manage Roles.
- The configuring administrator must have the appropriate role-management permissions.
- Selected roles must be below the permitted role hierarchy.
- Discord-managed and integration-managed roles cannot be assigned through this feature.
- ARVEE does not bypass membership screening.
- ARVEE does not grant administrator privileges automatically.
ARVEE rechecks the member's current state before assigning roles.
Verification and onboarding
ARVEE provides configurable interactive verification panels.
A server administrator can publish a verification panel containing a Verify button. When a member interacts with it, ARVEE checks the member's current state, membership screening status, and the target role's assignability.
If the checks pass, the configured verification role can be granted.
Verification panels complement automatic onboarding, but they are not ARVEE's primary justification for Server Members Intent.
The privileged intent is needed for real-time join, leave, and screening-completion events that happen without button interactions.
Goodbye messages
When a member leaves a server, ARVEE can automatically send a farewell message to a configured channel.
Administrators can configure:
- Whether goodbye messages are enabled.
- The destination channel.
- The goodbye message text.
- Optional advanced presentation settings.
This functionality uses the guildMemberRemove event.
It does not require access to the member's previous messages or online presence.
Member-join and member-leave automations
ARVEE supports administrator-configured workflows triggered by membership events.
Supported triggers include:
- Member joins
- Member leaves
Configured workflows can perform permitted actions such as sending a message to a designated channel or assigning a manageable role where applicable.
ARVEE validates server permissions before executing role-related actions.
These workflows do not execute arbitrary scripts, shell commands, or user-supplied code.
They operate through bounded actions defined by the server-management system.
Anti-raid monitoring
ARVEE includes optional rapid-join monitoring.
When enabled, the moderation module observes eligible join events and counts recent joins within a rolling one-minute interval.
If the configured threshold is reached, ARVEE can:
- Record a moderation case.
- Create a deduplicated alert for the relevant interval.
- Send a warning to the configured staff channel.
- Encourage moderators to review recent joins and Discord's server safety settings.
ARVEE does not automatically mass-ban users solely because several accounts joined close together.
The system is intended to provide staff with timely information for review.
Member-event logs
Server administrators can enable membership event logging.
ARVEE can record summaries such as:
- A member joining a server.
- A member leaving a server.
- Automatic role assignments.
- Related configured administrative events.
Logs are posted only when the appropriate module and destination channel are configured.
Member-event logs are not full copies of members' conversations.
Server analytics
ARVEE can maintain aggregate activity statistics based on membership events.
Examples include:
- Number of member joins.
- Number of member departures.
- Daily community activity summaries.
These statistics help administrators understand community activity without requiring ARVEE to read ordinary message content.
Optional Premium welcome DMs
Eligible Premium servers can enable additional private welcome messages.
When configured and permitted, ARVEE can send a private greeting after a member becomes eligible for onboarding.
Delivery depends on the recipient's Discord privacy settings and whether the bot is allowed to send the DM.
The feature uses delivery deduplication to reduce repeated greetings and does not assume that every DM can be delivered successfully.
Ordinary server welcome messages remain available without Premium.
Discord review: How to reproduce the functionality
Discord reviewers can evaluate ARVEE's Server Members Intent use case with the following procedure.
Test environment
Use a Discord server with ARVEE installed and a separate ordinary test account.
The test account should not have moderator, administrator, or server-management permissions.
Recommended demonstration
- Sign in to the ARVEE server dashboard.
- Select the test Discord server.
- Show that welcome messages are enabled and saved.
- Show the selected welcome channel.
- Optionally enable automatic roles and select a manageable test role.
- Have the test account join the Discord server.
- Observe ARVEE automatically posting the configured welcome message.
- If configured, verify the new member receives the expected role.
- If membership screening is enabled, complete screening and verify that the appropriate onboarding actions occur afterward.
- Optionally have the member leave and observe the configured goodbye message.
Evidence submission
A real screenshot is available here:
ARVEE automatic welcome — Discord screenshot
This screenshot captures ARVEE's automatic welcome message associated with a real member join.
If additional evidence is requested, a continuous screen recording can show the configuration, actual join, automatic welcome delivery, and optional role assignment in one sequence.
Evidence should be accessible to reviewers without requiring them to join a private Discord server.
Do not submit manually triggered messages, mockups, or simulated event logs as evidence of live member-event handling.
Explanation for Discord's privileged intent review
ARVEE requests Server Members Intent (GUILD_MEMBERS) to support optional server-management modules that automatically respond to member joins, departures, and membership-screening completion.
These modules include automatic welcome and goodbye messages, onboarding role assignments, configurable member-event workflows, rapid-join moderation alerts, event logs, and aggregate server analytics.
ARVEE receives member events through Discord's Gateway and performs the configured actions without requiring the joining or departing member to execute a command.
For example, when a new member joins a server, ARVEE can automatically send a welcome message. When applicable, it waits for the member to complete Discord membership screening before assigning configured roles.
This behavior cannot be fully replaced by slash commands or buttons because those require explicit interactions and do not independently notify the application of membership transitions.
Server administrators must explicitly configure optional modules. ARVEE applies Discord permission checks and role hierarchy restrictions when assigning roles or publishing messages.
The application does not require Guild Presences Intent or general Message Content Intent for these features.
A screenshot showing an actual automatic welcome event is provided above, and the functionality can be independently demonstrated in a Discord test server.
Permissions and troubleshooting
Welcome message does not appear
Verify that:
- The welcome module is enabled and saved.
- A valid destination channel is selected.
- ARVEE can view the channel and send messages.
- The joining account is not a bot.
- Membership screening has been completed where required.
- The bot is connected and receiving the relevant Gateway events.
Automatic role assignment fails
Verify that:
- Automatic join roles are enabled.
- ARVEE has Manage Roles permission.
- The selected role is assignable.
- The target role is below ARVEE's highest role.
- The member has completed screening.
- The selected role is not managed by another integration.
Goodbye message does not appear
Verify the goodbye module is enabled and the selected channel is writable.
Anti-raid alert does not trigger
Verify the moderation configuration, rapid-join threshold, and staff alert channel.
A single join will not trigger a threshold intended to detect unusual bursts of new members.
Manual welcome test works, but real joins do not
A manual welcome test only verifies message delivery and configuration.
Check the application's Server Members Intent access, the active Discord connection, and the actual member-event handlers.
Member data and privacy
ARVEE processes Discord server and user identifiers, membership event information, and relevant role state to support enabled features.
Depending on server configuration, the system can also retain:
- Welcome-message delivery records.
- Member-event audit entries.
- Role-assignment records.
- Workflow execution records.
- Anti-raid event samples.
- Moderation cases.
- Aggregate server analytics.
Some anti-raid samples are deleted after a short period. Other audit data, moderation cases, account-linked records, and RPG progression can have separate retention periods.
ARVEE does not claim that every user-associated record is deleted after 30 days.
Server administrators can disable optional modules. Users can contact ARVEE for applicable access and deletion requests.
For more information:
- ARVEE Privacy Policy
- ARVEE Support
- Privacy contact: privacy@arvee.world
Related documentation
- Discord Gateway Intent Overview
- Message Content and Available Alternatives
- Support and Troubleshooting
- ARVEE Server Dashboard
Implementation note: This guide describes ARVEE's current member-event functionality and the supplied real Discord welcome screenshot. Individual server configuration, live application permissions, deployment status, and Discord's privileged-intent approval determine whether a feature is operational in a particular server.
Review status: Supporting documentation and an actual welcome screenshot are available. Discord's approval of Server Members Intent must be confirmed separately through the Developer Portal or an official review response.