Giving members access to the association's Discord server

Setting up the connection

Each client installation connects to one Discord server. Staff choose the Discord roles used for members, staff, administrators, and chapters.

The administration page has five steps for creating the Discord application, choosing its permissions, adding it to the server, putting its role in the correct order, and recording the required settings.

How a member connects

An eligible member or staff member starts from their Military OS account. Discord asks them to approve the connection. Military OS then adds the Discord account to the server and assigns the roles that match the person's current association record.

Military OS keeps the Discord account number and public name needed for the link. It does not keep the temporary Discord sign-in token.

Keeping Discord roles up to date

Military OS compares each linked Discord account with the person's current membership, staff duties, administrator access, and main chapter. It adds the roles that apply and removes managed roles that no longer apply.

If a person no longer has an eligible membership or staff duty, Military OS removes the server access it manages. An administrator can check all linked accounts and see how many were checked, changed, removed, or failed.

Discord permissions

The Discord application needs View Channels, Manage Roles, Manage Nicknames, and Kick Members. Its server role must sit above the roles it manages. It does not need Discord Administrator access.

One Discord account can be linked to one member record. Disconnecting removes the saved link and asks Discord to remove the server access managed by Military OS.

Screenshots show the product version available when this post was published.

Discussion

Discussion loads here through GitHub-backed comments when JavaScript is available.