STAR CITIZEN · ORGANIZATION GUIDE

Connect your RSI organization ranks to Discord roles

Give your staff a shared set of membership and rank rules to manage, instead of choosing every member’s Discord role by hand.

ALL-E’s Organization AutoRole connects verified RSI accounts with the Discord roles your administrators choose. It supports main members, affiliates, ranks and organizational responsibilities. You can read this guide and view the configuration example without signing in.

Set up your organization’s rules

1. Add ALL-E and select your server. Add ALL-E to Discord, then sign in to the website and open Manage servers. Use the server you are authorized to manage.
2. Connect the RSI organization. Open Setup → Organization AutoRole and select your organization. Check the displayed organization before continuing.
3. Choose your mappings. Match RSI ranks to Discord roles. Configure main-member, affiliate and organizational-responsibility mappings to fit your org. Review the actual permissions of each selected Discord role.
4. Save and enable. Review the configuration and enable Organization AutoRole when you are ready for it to apply. Members then verify their RSI accounts so ALL-E can evaluate their eligible organization roles.

How members verify their RSI accounts

Members run /myhandle in an ALL-E server and follow the temporary RSI biography-code instructions. This proves ownership of the RSI account. ALL-E does not need their RSI password.

A member can verify multiple RSI accounts globally. Their qualifying verified accounts contribute to eligible organization roles and the highest qualifying rank; they do not need to choose a different handle for each server. Account ownership verification and permission to administer a Discord server are separate.

Ranks, responsibilities and optional roles

A rank mapping connects progression in your organization to a Discord role. Main-member and affiliate mappings represent the member’s relationship to the organization. Organizational-responsibility mappings let administrators account for the RSI roles their organization uses.

Reaction roles serve a different purpose: members choose optional interests or preferences. Treat verified organization membership and self-selected interests as different rules when designing your server’s access.

If the expected role does not appear

• Check the account link. Confirm that the member verified the intended RSI account and that it belongs to the expected organization.
• Check the source data. RSI availability and publicly visible profile information affect what ALL-E can evaluate. Missing source information does not prove a member is ineligible.
• Check the mapping and saved state. Make sure the selected Discord role matches your intended membership, rank or responsibility and that Organization AutoRole is enabled.
• Check Discord permissions. Confirm that ALL-E can manage the selected role and that the role hierarchy allows it. Review the dashboard’s permission guidance before changing access.

If these checks do not explain the result, contact ALL-E support with the affected server, handle and expected role. Do not send passwords or account tokens.

Bring your members together for a flight

Once your community is ready, plan an operation with a briefing, member sign-ups and clear host approval.