Subscription access

Choose the publics users must join before using your bot.

Loading settings…

Required subscriptions

—

Every enabled public is required. Users receive join buttons and a button to check their subscription.

Add a public

Checker connection

Use a separate Telegram bot. Make it an administrator in every required public so it can verify membership.

No checker tokenNew checker bot tokenRemove the saved checker token

The token stays on the server and is never shown after saving.

Access rules

Require subscriptions to use the bot

Turn this on after adding at least one enabled public and configuring the checker. Administrators retain access.

Require an invitation too

Keep this checked for invitation-only access. Uncheck it to let users unlock the bot by subscribing to the required publics.

Recheck every N bot requests

With 5 selected, subscriptions are verified before requests 1, 6, 11… An unsubscribe revokes access at the next check. Users can also check immediately with “I subscribed”.

If verification fails, access pauses and the user can retry. Changing settings forces a fresh check on their next request.

What users see

The bot guides users through subscription access and shows the current result.

Subscribe to continue

Join the required publics below, then check your subscription to unlock the bot.

I subscribed · check access

Already subscribed users continue normally. Missing subscriptions and temporary checker errors have separate messages and a retry action.

Connections

Admin pageWebSocket · live connection

Membership verificationTelegram HTTPS API

Subscriptions are checked when users interact with the bot. No background tracking of membership changes.

All changes saved

Welcome back

Subscription access

Required subscriptions

Checker connection

Access rules

What users see

Connections