Authentication

The main website uses Discord OAuth for identity and server access. The static docs frontend does not depend on that session and does not ask for Discord credentials.

Normal login requests identity/server access for the dashboard. Add to Discord begins a separate installation-intent flow. Signing in alone does not add the bot or authorize every server.

The production OAuth callback remains on the main website. The docs subdomain is not a second OAuth callback or an authentication proxy.

Server authorization

Protected dashboard routes and APIs check the session and guild access on the backend. A visible button, stale tab or known server URL is not authorization. Losing a Discord role can invalidate a previously allowed operation.

Verification problems

Complete the supported verification and official Discord flow. Do not disable browser security or share tokens to work around a login failure. Local visual previews intentionally cannot complete real login. Use Dashboard Login for safe checks.