Discord OAuth, X identity, and member voting

Community Admissions uses Discord OAuth so people cannot simply type another person’s Discord ID.

Applicant connection

When an applicant connects Discord, OAuth confirms the real Discord account. CollabOS stores the applicant session and can return the existing active application when the same Discord user reconnects.

When Advanced X is ON, the applicant must also connect X. The public application UI uses the stored connected X identity rather than manually entered X details.

Voter connection

Discord OAuth confirms the voter’s real Discord user ID. CollabOS checks the synced Discord member table to confirm the voter is still in the community and is not a bot.

When Advanced X is ON, the voter must also connect X before voting or vouching. Visible voter identity should prefer the stored X profile picture, X display name, clickable username, and vote date. Discord remains the background membership and role check.

Voting eligibility

Voter eligibility can be based on:

• any current server member
• selected Discord roles
• excluded Discord roles
• manually selected Discord IDs

💡Best practices

Keep Discord member sync current. Do not use X connection as a replacement for Discord membership validation.