Find your next step.

Invite Super Security, open the dashboard, choose your server and review the setup checklist. Choose verification roles below the bot’s highest role, a ticket category and a staff role. Post a verification panel and test with another account.

Sign in with the correct Discord account. The bot must be in the server. Current owners receive access automatically; delegated staff need a dashboard grant from the owner or Developer. Discord Administrator permission alone is not a dashboard grant.

Check that the bot is online and its startup logs show synchronization for your server. Check Use Application Commands in the channel and refresh Discord. Authorized managers can use /sync_commands. Review individual command switches in server Settings.

Discord prevents assigning managed roles or roles at or above the bot’s highest role. Verified and Unverified must be different roles. Check Manage Roles and move the bot role above both.

Open a game using its slash command and choose your bet in the panel. Shared tables use /table. The Discord Activity launch requires developer-portal configuration and deployment. Server points and personal DM wallets remain separate.

The operator registers provider applications once. Streamers then click Connect, sign in on the provider and approve access. invalid_client means the configured client credentials or application setup need review. Never share secrets in chat.

Open Stream Tools → Discord notifications. Save the account's text channel, enable and resume that account, and select LIVE. Send a test; the bot needs View Channel, Send Messages and Embed Links. Check the displayed connector and delivery status. TikTok needs the experimental connector enabled and a connected LIVE room. Failed OAuth-platform posts retry while confirmed LIVE for up to ten minutes. A test post does not prove provider event delivery.

Use combined alerts or the matching separate event source, not both for the same event. If using Speech only, disable speech on other overlapping sources. Goals and TikTok statistics have silent sources. Keep source URLs private and rotate exposed URLs.

Reconnect Twitch, YouTube or Kick with optional chat permission checked. Enable native replies in Chat commands. Check delivery status and active live chat. Replies post as the connected account. TikTok responses remain overlay only.

Enable rewards, link the viewer’s platform identity and confirm current Discord membership. Check event reward amounts, pause/filter rules, cooldowns and the daily cap. Test events do not award points. TikTok requires stable actor and event IDs.

Enable OBS WebSocket authentication on your PC. Add a named scene/source rule, download the Windows bridge and run it with that account’s connection ID. Enter the private bridge token and local OBS password. Keep OBS and the bridge running.

This usually requires checking the bot service and reverse proxy on the VPS. Deploy the complete ZIP using deploy/update.sh; missing modules can crash startup. Run the redacted deploy/check-website.py diagnostic and inspect the service logs.

The reported warning remains unresolved. A working page or passing software tests do not prove website safety. Keep protection enabled while the actual server and domain are investigated. The ZIP includes deploy/WEBSITE-REVIEW.md.

Use /open_ticket in a server running the bot. Give the affected server, feature, error text and approximate time. Staff may ask for redacted diagnostics. Do not include passwords, tokens, private overlay URLs, addresses or coordinates.