Manage via Telegram

Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Login via Telegram (OIDC) or Mini App initData auth. Member auth: Authentication. Stars membership: SubscriptionConductor.

Ring ships a Telegram Admin Bot so platform admins can moderate news, run selected admin operations, and receive approval callbacks without opening the web admin UI — while still obeying the same RBAC SSOT as /admin.

Concern	Truth
Webhook	`POST /api/telegram/admin-bot/webhook`
Code	`lib/telegram/admin-bot/`
RBAC	`features/auth/user-role.ts` — `isPlatformAdmin` / `isSuperadmin`
News approval	Bot callbacks + News / News Kingdom

Do not confuse these Telegram surfaces

Surface	Audience	Secret / crypto
Login via Telegram	Members (browser)	`AUTH_TELEGRAM_ID` / `SECRET` — OIDC at `oauth.telegram.org`
Mini App initData	Members (WebApp client)	WebAppData HMAC — `TELEGRAM_MINI_APP_BOT_TOKEN` (fallbacks documented on Authentication)
Link Telegram (profile)	Logged-in members	Login Widget HMAC with `ADMIN_BOT_TOKEN` / `TELEGRAM_LOGIN_BOT_TOKEN`
telegram_stars membership	Paying members	Same Mini App bot token + Bot API `createInvoiceLink` — SubscriptionConductor
Admin bot (this page)	Platform admins

Why operators use Telegram

Missile-hour ops and travel-friendly moderation: approve newsroom drafts, check critical queues, and keep an audit trail — without VPN into a desktop admin session.

Trust & Brand fit

Telegram management sits with authentication, security, and verification:

Only whitelisted Telegram IDs mapped to Ring admin / superadmin users can talk to the bot.
Destructive actions (user delete, platform settings) stay superadmin-only.
Admins must first link Telegram on their Ring profile (or sign in via Telegram OIDC so communication.telegramId is set) before the whitelist can see them.

Security

Defense layers and admin posture.

News

Telegram approval in the newsroom pipeline.

Implementation

Modules

Path	Role
`app/api/telegram/admin-bot/webhook/route.ts`	Telegram updates ingress
`lib/telegram/admin-bot/bot-config.ts`	Token, webhook secret, `setWebhook`
`lib/telegram/admin-bot/whitelist.ts`	Map Telegram chat → Ring admin user via `communication.telegramId`
`lib/telegram/admin-bot/ring-api-executor.ts`	Operation-level RBAC before Ring HTTP
`lib/telegram/admin-bot/news-callback-handler.ts`	Inline news approve/reject
`lib/telegram/admin-bot/anthropic-router.ts`	Optional NL → tool routing
`lib/telegram/admin-bot/audit-logger.ts`	Interaction audit

Manage via Telegram

Concern	Truth
Webhook	`POST /api/telegram/admin-bot/webhook`
Code	`lib/telegram/admin-bot/`
RBAC	`features/auth/user-role.ts` — `isPlatformAdmin` / `isSuperadmin`
News approval	Bot callbacks + News / News Kingdom

Do not confuse these Telegram surfaces

Surface	Audience	Secret / crypto
Login via Telegram	Members (browser)	`AUTH_TELEGRAM_ID` / `SECRET` — OIDC at `oauth.telegram.org`
Mini App initData	Members (WebApp client)	WebAppData HMAC — `TELEGRAM_MINI_APP_BOT_TOKEN` (fallbacks documented on Authentication)
Link Telegram (profile)	Logged-in members	Login Widget HMAC with `ADMIN_BOT_TOKEN` / `TELEGRAM_LOGIN_BOT_TOKEN`
telegram_stars membership	Paying members	Same Mini App bot token + Bot API `createInvoiceLink` — SubscriptionConductor
Admin bot (this page)	Platform admins

Why operators use Telegram

Missile-hour ops and travel-friendly moderation: approve newsroom drafts, check critical queues, and keep an audit trail — without VPN into a desktop admin session.

Trust & Brand fit

Telegram management sits with authentication, security, and verification:

Only whitelisted Telegram IDs mapped to Ring admin / superadmin users can talk to the bot.
Destructive actions (user delete, platform settings) stay superadmin-only.
Admins must first link Telegram on their Ring profile (or sign in via Telegram OIDC so communication.telegramId is set) before the whitelist can see them.

Security

Defense layers and admin posture.

News

Telegram approval in the newsroom pipeline.

Implementation

Modules

Path	Role
`app/api/telegram/admin-bot/webhook/route.ts`	Telegram updates ingress
`lib/telegram/admin-bot/bot-config.ts`	Token, webhook secret, `setWebhook`
`lib/telegram/admin-bot/whitelist.ts`	Map Telegram chat → Ring admin user via `communication.telegramId`
`lib/telegram/admin-bot/ring-api-executor.ts`	Operation-level RBAC before Ring HTTP
`lib/telegram/admin-bot/news-callback-handler.ts`	Inline news approve/reject
`lib/telegram/admin-bot/anthropic-router.ts`	Optional NL → tool routing
`lib/telegram/admin-bot/audit-logger.ts`	Interaction audit

Manage via Telegram

Concern	Truth
Webhook	`POST /api/telegram/admin-bot/webhook`
Code	`lib/telegram/admin-bot/`
RBAC	`features/auth/user-role.ts` — `isPlatformAdmin` / `isSuperadmin`
News approval	Bot callbacks + News / News Kingdom

Do not confuse these Telegram surfaces

Surface	Audience	Secret / crypto
Login via Telegram	Members (browser)	`AUTH_TELEGRAM_ID` / `SECRET` — OIDC at `oauth.telegram.org`
Mini App initData	Members (WebApp client)	WebAppData HMAC — `TELEGRAM_MINI_APP_BOT_TOKEN` (fallbacks documented on Authentication)
Link Telegram (profile)	Logged-in members	Login Widget HMAC with `ADMIN_BOT_TOKEN` / `TELEGRAM_LOGIN_BOT_TOKEN`
telegram_stars membership	Paying members	Same Mini App bot token + Bot API `createInvoiceLink` — SubscriptionConductor
Admin bot (this page)	Platform admins

Why operators use Telegram

Missile-hour ops and travel-friendly moderation: approve newsroom drafts, check critical queues, and keep an audit trail — without VPN into a desktop admin session.

Trust & Brand fit

Telegram management sits with authentication, security, and verification:

Only whitelisted Telegram IDs mapped to Ring admin / superadmin users can talk to the bot.
Destructive actions (user delete, platform settings) stay superadmin-only.
Admins must first link Telegram on their Ring profile (or sign in via Telegram OIDC so communication.telegramId is set) before the whitelist can see them.

Security

Defense layers and admin posture.

News

Telegram approval in the newsroom pipeline.

Implementation

Modules

Path	Role
`app/api/telegram/admin-bot/webhook/route.ts`	Telegram updates ingress
`lib/telegram/admin-bot/bot-config.ts`	Token, webhook secret, `setWebhook`
`lib/telegram/admin-bot/whitelist.ts`	Map Telegram chat → Ring admin user via `communication.telegramId`
`lib/telegram/admin-bot/ring-api-executor.ts`	Operation-level RBAC before Ring HTTP
`lib/telegram/admin-bot/news-callback-handler.ts`	Inline news approve/reject
`lib/telegram/admin-bot/anthropic-router.ts`	Optional NL → tool routing
`lib/telegram/admin-bot/audit-logger.ts`	Interaction audit

Related documentation

Authentication

Prerequisite: member Login via Telegram OIDC + Mini App initData vs this admin bot.

SubscriptionConductor

See-also: telegram_stars invoices share the Mini App bot token helper — not this admin webhook.

News Kingdom architecture

Same-workflow: scoring, promotion, and Telegram approve callbacks.

Autonomous Newsroom (Grok)

Next-step: draft → image → Telegram approve pipeline.

Path	Role
`features/auth/components/telegram-signin-button.tsx`	Login via Telegram OIDC
`lib/auth/telegram-oidc.ts`	Auth.js OIDC provider
`lib/auth/telegram-miniapp-initdata.ts`	Mini App WebAppData HMAC + bot token helper
`features/auth/components/telegram-linking-modal.tsx`	Legacy Login Widget linking
`app/api/auth/telegram/callback/route.ts`	Widget callback (session required)
`lib/auth/telegram-login-widget-hash.ts`	Shared widget HMAC
`lib/payments/subscription/providers/telegram-stars-subscription.ts`	Stars XTR invoices

Path	Role
`features/auth/components/telegram-signin-button.tsx`	Login via Telegram OIDC
`lib/auth/telegram-oidc.ts`	Auth.js OIDC provider
`lib/auth/telegram-miniapp-initdata.ts`	Mini App WebAppData HMAC + bot token helper
`features/auth/components/telegram-linking-modal.tsx`	Legacy Login Widget linking
`app/api/auth/telegram/callback/route.ts`	Widget callback (session required)
`lib/auth/telegram-login-widget-hash.ts`	Shared widget HMAC
`lib/payments/subscription/providers/telegram-stars-subscription.ts`	Stars XTR invoices

Path	Role
`features/auth/components/telegram-signin-button.tsx`	Login via Telegram OIDC
`lib/auth/telegram-oidc.ts`	Auth.js OIDC provider
`lib/auth/telegram-miniapp-initdata.ts`	Mini App WebAppData HMAC + bot token helper
`features/auth/components/telegram-linking-modal.tsx`	Legacy Login Widget linking
`app/api/auth/telegram/callback/route.ts`	Widget callback (session required)
`lib/auth/telegram-login-widget-hash.ts`	Shared widget HMAC
`lib/payments/subscription/providers/telegram-stars-subscription.ts`	Stars XTR invoices

Documentation

Quick entry (CTOs · auditors · agents)

Documentation

Quick entry (CTOs · auditors · agents)

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Documentation

Quick entry (CTOs · auditors · agents)

Loading documentation...

Loading documentation...

Loading documentation...

Manage via Telegram

Do not confuse these Telegram surfaces

Why operators use Telegram

Trust & Brand fit

Security

News

Related documentation

Related documentation

Authentication

SubscriptionConductor

News Kingdom architecture

Autonomous Newsroom (Grok)

Manage via Telegram

Do not confuse these Telegram surfaces

Why operators use Telegram

Trust & Brand fit

Security

News

Related documentation

Related documentation

Authentication

SubscriptionConductor

News Kingdom architecture

Autonomous Newsroom (Grok)

Manage via Telegram

Do not confuse these Telegram surfaces

Why operators use Telegram

Trust & Brand fit

Security

News

Related documentation

Related documentation

Authentication

SubscriptionConductor

News Kingdom architecture

Autonomous Newsroom (Grok)

Authentication

Typical scenarios

Env (verified names)

RBAC layers

Related member Telegram (not this bot)

Ring MCP Server

Admin API

Authentication

Typical scenarios

Env (verified names)

RBAC layers

Related member Telegram (not this bot)

Ring MCP Server

Admin API

Authentication

Typical scenarios

Env (verified names)

RBAC layers

Related member Telegram (not this bot)

Ring MCP Server

Admin API