Titan's website and Discord work together to support joining. The website owns account state, RSI verification, and the Member approval record. Discord is the community space where people receive the access associated with that state.
Before You Sign In
Public visitors can review Titan's mission, Rules And Expectations, public event guidance, and joining information. Joining begins by signing in with Discord. Discord sign-in identifies the account, but it does not by itself grant Guest or Member access.
Unverified
A newly signed-in account starts with Unverified membership standing and unverified RSI verification health. The onboarding flow asks for the public RSI handle that you control and provides a unique verification token to place in your RSI Citizen Dossier Bio.
Unverified readers retain public access while they complete or repair verification. They do not receive Guest or Member content merely because they are signed in.
Guest
Successful direct RSI verification moves an eligible Unverified account to Guest standing. A Guest can finish onboarding preferences, continue into Discord, read Guest guidance, and wait for Member review.
Choosing a home division or notification roles helps with orientation. Those preferences do not grant Guest, Member, Leadership, Admin, or approval permission.
Member
A verified Guest may be reviewed by an authorized approver. Approval changes membership standing to Member and queues the corresponding Discord access work where configured. Approval is not automatic, and no specific review time is promised.
Membership standing and RSI verification health remain separate after approval. A Member does not lose Member standing merely because verification later needs attention, but effective restricted access can apply until verification is repaired.
Where To Get Help
Use the RSI Verification Help article for handle, token, and retry guidance. If the website reports a persistent verification, Discord access, or approval problem after you follow the displayed instructions, contact an admin through the community's established support path. Never share an OAuth code, session cookie, bot token, or verification token with another person.