Accounts and linked identities
Discord sign-in, BeatLeader, ScoreSaber, Twitch, profile data and account security boundaries.
BeatKhana account
Normal accounts are created through Discord sign-in. BeatKhana uses the returned public identity to establish the account/session; it does not give tournament organisers Discord credentials. Sign out when using shared production machines.
Linked providers
- BeatLeader: competitive identity and platform ID used by eligibility and participant resolution.
- ScoreSaber: competitive profile identity used where a tournament or feature supports it.
- Twitch: broadcast identity used for requirements, profiles or stream presentation.
Linking uses provider-specific OAuth/state validation. A link proves control at link time; it does not grant tournament staff access to the third-party account. If a provider link is wrong, unlink/reconnect through supported account settings rather than asking staff to edit IDs casually.
Profile and permissions
Profiles contain public identity, linked IDs, roles/permissions, teams, badges and related tournament information as applicable. Global permissions cover platform capabilities; tournament roles cover one event. Support staff may correct accounts under administrative authorization, and changes should be auditable.
Security
Do not share access tokens, refresh tokens, session cookies, TA bot tokens or stream keys. OAuth access tokens are bearer credentials. Discord authentication for the main website and BeatKhana OAuth for third-party apps are related but distinct flows.