Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    SubscriptionConductor
    PaymentConductor
    Payments Overview
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    WebRTC Calls & STUNner TURN
    News Module
    Member Blogs
    Public Profile Pages
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    SubscriptionConductor
    PaymentConductor
    Payments Overview
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    WebRTC Calls & STUNner TURN
    News Module
    Member Blogs
    Public Profile Pages
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    SubscriptionConductor
    PaymentConductor
    Payments Overview
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    WebRTC Calls & STUNner TURN
    News Module
    Member Blogs
    Public Profile Pages
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    1. Docs
    2. /Features
    3. /Manage via Telegram
    Updated Jul 10, 20263 min listen
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    1. Docs
    2. /Features
    3. /Manage via Telegram
    Updated Jul 10, 20263 min listen
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    1. Docs
    2. /Features
    3. /Manage via Telegram
    Updated Jul 10, 20263 min listen
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Manage via Telegram

    Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Telegram Login (see Username reservation for identity linking).

    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.

    ConcernTruth
    WebhookPOST /api/telegram/admin-bot/webhook
    Codelib/telegram/admin-bot/
    RBACfeatures/auth/user-role.ts — isPlatformAdmin / isSuperadmin
    News approvalBot callbacks + News / News Kingdom

    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.
    • Member-facing “Verified by Telegram” badges are a separate Login Widget flow — do not confuse the two.

    Security

    Defense layers and admin posture.

    News

    Telegram approval in the newsroom pipeline.

    Authentication

    Roles and session model the bot must respect.

    Typical scenarios

    • Autonomous newsroom draft arrives → admin taps Approve in Telegram → locale fan-out.
    • On-call admin checks verification / order status via bot commands (platform-admin paths).
    • Failed or unauthorized attempts are audit-logged.

    Implementation

    Modules

    PathRole
    app/api/telegram/admin-bot/webhook/route.tsTelegram updates ingress
    lib/telegram/admin-bot/bot-config.tsToken, webhook secret, setWebhook
    lib/telegram/admin-bot/whitelist.tsMap Telegram chat → Ring admin user
    lib/telegram/admin-bot/ring-api-executor.tsOperation-level RBAC before Ring HTTP
    lib/telegram/admin-bot/news-callback-handler.tsInline news approve/reject
    lib/telegram/admin-bot/anthropic-router.tsOptional NL → tool routing
    lib/telegram/admin-bot/audit-logger.tsInteraction audit
    lib/telegram/admin-bot/TELEGRAM_BOT_RBAC.mdRBAC policy SSOT (in-repo)

    Env (verified names)

    Webhook URL shape: (HTTPS in production). Validate via .

    Related

    Ring MCP Server

    IDE twin: Cursor stdio MCP for the same clone.

    News Kingdom architecture

    Scoring, promotion, Telegram callbacks.

    Generative newsroom

    Draft → image → Telegram approve pipeline.

    Admin API

    Web admin surfaces the bot mirrors carefully.

    Manage via Telegram

    Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Telegram Login (see Username reservation for identity linking).

    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.

    ConcernTruth
    WebhookPOST /api/telegram/admin-bot/webhook
    Codelib/telegram/admin-bot/
    RBACfeatures/auth/user-role.ts — isPlatformAdmin / isSuperadmin
    News approvalBot callbacks + News / News Kingdom

    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.
    • Member-facing “Verified by Telegram” badges are a separate Login Widget flow — do not confuse the two.

    Security

    Defense layers and admin posture.

    News

    Telegram approval in the newsroom pipeline.

    Authentication

    Roles and session model the bot must respect.

    Typical scenarios

    • Autonomous newsroom draft arrives → admin taps Approve in Telegram → locale fan-out.
    • On-call admin checks verification / order status via bot commands (platform-admin paths).
    • Failed or unauthorized attempts are audit-logged.

    Implementation

    Modules

    PathRole
    app/api/telegram/admin-bot/webhook/route.tsTelegram updates ingress
    lib/telegram/admin-bot/bot-config.tsToken, webhook secret, setWebhook
    lib/telegram/admin-bot/whitelist.tsMap Telegram chat → Ring admin user
    lib/telegram/admin-bot/ring-api-executor.tsOperation-level RBAC before Ring HTTP
    lib/telegram/admin-bot/news-callback-handler.tsInline news approve/reject
    lib/telegram/admin-bot/anthropic-router.tsOptional NL → tool routing
    lib/telegram/admin-bot/audit-logger.tsInteraction audit
    lib/telegram/admin-bot/TELEGRAM_BOT_RBAC.mdRBAC policy SSOT (in-repo)

    Env (verified names)

    Webhook URL shape: (HTTPS in production). Validate via .

    Related

    Ring MCP Server

    IDE twin: Cursor stdio MCP for the same clone.

    News Kingdom architecture

    Scoring, promotion, Telegram callbacks.

    Generative newsroom

    Draft → image → Telegram approve pipeline.

    Admin API

    Web admin surfaces the bot mirrors carefully.

    Manage via Telegram

    Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Telegram Login (see Username reservation for identity linking).

    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.

    ConcernTruth
    WebhookPOST /api/telegram/admin-bot/webhook
    Codelib/telegram/admin-bot/
    RBACfeatures/auth/user-role.ts — isPlatformAdmin / isSuperadmin
    News approvalBot callbacks + News / News Kingdom

    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.
    • Member-facing “Verified by Telegram” badges are a separate Login Widget flow — do not confuse the two.

    Security

    Defense layers and admin posture.

    News

    Telegram approval in the newsroom pipeline.

    Authentication

    Roles and session model the bot must respect.

    Typical scenarios

    • Autonomous newsroom draft arrives → admin taps Approve in Telegram → locale fan-out.
    • On-call admin checks verification / order status via bot commands (platform-admin paths).
    • Failed or unauthorized attempts are audit-logged.

    Implementation

    Modules

    PathRole
    app/api/telegram/admin-bot/webhook/route.tsTelegram updates ingress
    lib/telegram/admin-bot/bot-config.tsToken, webhook secret, setWebhook
    lib/telegram/admin-bot/whitelist.tsMap Telegram chat → Ring admin user
    lib/telegram/admin-bot/ring-api-executor.tsOperation-level RBAC before Ring HTTP
    lib/telegram/admin-bot/news-callback-handler.tsInline news approve/reject
    lib/telegram/admin-bot/anthropic-router.tsOptional NL → tool routing
    lib/telegram/admin-bot/audit-logger.tsInteraction audit
    lib/telegram/admin-bot/TELEGRAM_BOT_RBAC.mdRBAC policy SSOT (in-repo)

    Env (verified names)

    Webhook URL shape: (HTTPS in production). Validate via .

    Related

    Ring MCP Server

    IDE twin: Cursor stdio MCP for the same clone.

    News Kingdom architecture

    Scoring, promotion, Telegram callbacks.

    Generative newsroom

    Draft → image → Telegram approve pipeline.

    Admin API

    Web admin surfaces the bot mirrors carefully.

    https://<your-domain>/api/telegram/admin-bot/webhook
    secret_token
    validateWebhookSecret

    RBAC layers

    1. Whitelist — sender Telegram ID must map to a Ring user in PLATFORM_ADMIN_ROLES.
    2. Executor — per-operation checks in ring-api-executor.ts.
    3. Ring HTTP APIs — session/MCP auth re-validates; bot must not bypass SSOT.

    Strict superadmin examples: user delete, platform branding / AI settings mutations. Platform admins: news moderation, selected order/wallet/verification paths — see TELEGRAM_BOT_RBAC.md.

    Related member Telegram (not this bot)

    • Login Widget: features/auth/components/telegram-linking-modal.tsx
    • Callback: app/api/auth/telegram/callback/route.ts
    bash
    
ADMIN_BOT_TOKEN=...
ADMIN_BOT_WEBHOOK_SECRET=...
    https://<your-domain>/api/telegram/admin-bot/webhook
    secret_token
    validateWebhookSecret

    RBAC layers

    1. Whitelist — sender Telegram ID must map to a Ring user in PLATFORM_ADMIN_ROLES.
    2. Executor — per-operation checks in ring-api-executor.ts.
    3. Ring HTTP APIs — session/MCP auth re-validates; bot must not bypass SSOT.

    Strict superadmin examples: user delete, platform branding / AI settings mutations. Platform admins: news moderation, selected order/wallet/verification paths — see TELEGRAM_BOT_RBAC.md.

    Related member Telegram (not this bot)

    • Login Widget: features/auth/components/telegram-linking-modal.tsx
    • Callback: app/api/auth/telegram/callback/route.ts
    bash
    
ADMIN_BOT_TOKEN=...
ADMIN_BOT_WEBHOOK_SECRET=...
    https://<your-domain>/api/telegram/admin-bot/webhook
    secret_token
    validateWebhookSecret

    RBAC layers

    1. Whitelist — sender Telegram ID must map to a Ring user in PLATFORM_ADMIN_ROLES.
    2. Executor — per-operation checks in ring-api-executor.ts.
    3. Ring HTTP APIs — session/MCP auth re-validates; bot must not bypass SSOT.

    Strict superadmin examples: user delete, platform branding / AI settings mutations. Platform admins: news moderation, selected order/wallet/verification paths — see TELEGRAM_BOT_RBAC.md.

    Related member Telegram (not this bot)

    • Login Widget: features/auth/components/telegram-linking-modal.tsx
    • Callback: app/api/auth/telegram/callback/route.ts
    bash
    
ADMIN_BOT_TOKEN=...
ADMIN_BOT_WEBHOOK_SECRET=...