Telegram Business Account Roles and Permissions

A business can answer customers from a person’s Telegram account, publish through a channel, moderate a group, run a standalone bot, or connect a bot to a person’s account. Those are different assets. Adding an employee as a channel administrator does not let them open the owner’s private chats. Giving a developer a bot token does not make that developer a channel owner. Connecting a chatbot to a profile does not transfer the profile to the bot company. Draw the boundary before inviting anyone. Telegram describes Business as features added to a user account, while its channel FAQ describes a separate owner and administrators.

The distinction matters most when a founder says “our Telegram account” but means their personal login and number. Telegram’s account recovery guidance ties a login to a mobile number the user controls. If the founder changes phone numbers or leaves, another channel admin cannot simply take over that person’s private chats. Put the phone number, recovery email, and account holder in an access register; decide separately whether the business needs a channel or bot that can be transferred. Telegram warns that an out-of-date phone number can cause permanent loss of account access.

Telegram Business adds opening hours, location, quick replies, greeting and away messages, chat links, and other profile tools. Telegram’s current API documentation says the full set is available to Premium subscribers, while a connected bot is available to non-Premium users. Telegram’s May 2026 update also calls the bot setting Settings > Chat Automation for any user. A team planning a connected bot should therefore check the current client menu before assuming that buying Premium is the access step. Telegram’s Business documentation and 2026 Chat Automation announcement describe that split.

Telegram does not publish a single company-wide employee role for Business profiles. The named roles below belong to a particular channel, group, or bot. Administrator rights are selectable permissions, so two people called administrator may have different abilities. The table is an access map, not a promise that every app screen uses identical labels. The channel FAQ and admin-rights schema are the useful checks when reviewing an invitation.

For a channel, the owner can appoint additional administrators and choose each administrator’s rights. Grant a publishing teammate posting rights only if publishing is their job; grant a moderator the relevant moderation rights in the group that they actually cover. The channel owner can add and remove administrators, and Telegram’s admin-rights definition separates actions such as posting, editing, deleting, inviting, and adding admins. A job title is not a substitute for reviewing those switches.

After the invitation, test the exact action. Have the publisher make a draft post or the moderator handle a test report, then confirm they cannot perform a more powerful action they do not need. If a contractor needs only a month of publishing, put the end date in the same access register as the channel name. On the end date, the owner removes their administrator grant. An employee who has merely left a group as a member is a different case: their membership removal is not a token rotation, and their old copies or exports of messages are not erased by removing access.

For the Business profile itself, there is no equivalent add-agent roster in the personal account. To bring in automation, the person who controls that account chooses a connected bot and chat scope. Telegram says a profile currently connects one business bot, with recipients selectable by existing versus new chats, contacts versus non-contacts, and inclusion or exclusion lists. A bot can be paused for one chat, permanently disabled for a chat, or disconnected from the profile. Those controls are documented in the connected-bot API. This is the practical replacement for handing an agency the person’s Telegram login.

A connected bot can reply on behalf of the profile only within the connection rights and the chats selected by the account holder. Telegram’s businessBotRights schema names rights including reply, read_messages, delete_sent_messages, delete_received_messages, edit_name, edit_bio, edit_profile_photo, edit_username, gift controls, transfer_stars, and manage_stories. Those are not all customer-support actions. A bot that answers opening-hour questions has no obvious need to edit a username, transfer Stars, or manage gifts. Check each switch against the vendor’s job. Telegram’s current rights schema is the source for the names.

Chat scope and rights work together. A bot with read_messages but excluded from contacts should not see contact chats through that business connection. A bot allowed into existing chats exposes more history context than one restricted to new chats. An excluded VIP chat can still be handled by the owner manually. Ask a chatbot vendor what it stores after a message reaches its own system; Telegram’s revocation stops future connection access but cannot retrieve data the vendor has already copied. Telegram’s connected-bot documentation describes the connection and its pause and disconnect controls.

The owner can review the managed chat’s Manage Bot action, which Telegram says directs them to the connected bot. If an agency says it needs the account login to run a chatbot, compare that request with Telegram’s documented connection path first. A connected bot is the explicit grant; a shared login gives that agency the user’s wider account session. Telegram’s bot feature guide describes both the managed-chat action and the bot’s business-connection rights.

A standalone bot is created with /newbot in @BotFather. BotFather asks for a name and username and issues a token used to call the Bot API. Telegram says anyone with that token can control the bot, so a copied token in a support ticket, source repository, screenshot, or departed agency’s configuration is still an active credential. Share the bot’s service endpoint or a secret-store reference with operators; keep the token out of chat. If the token is lost or exposed, BotFather’s /token command generates a replacement. Telegram’s BotFather guide documents those commands.

There are two handoffs to audit separately. /mybots lets the bot owner transfer the bot to another Telegram user who has interacted with it. Telegram calls the transfer permanent and says the recipient gains full control, including message access and deletion. Rotating /token changes the bearer credential used by code; it does not by itself change the BotFather owner. Conversely, transferring ownership is not a substitute for replacing a token that a former contractor copied. Perform both when the owner or hosting vendor changes. Telegram’s transfer and token instructions are explicit on this point.

Bot access to a group is a third grant. By default, group bots use Privacy Mode and receive relevant commands, replies, service messages, and private messages sent to the bot. A bot made group administrator receives all group messages; disabling Privacy Mode also widens message receipt and requires re-adding the bot for that change to take effect. For a bot that only answers /hours, leave Privacy Mode on. For a moderation bot that must inspect every new post, document why it needs the broader access, then remove it when the use case ends. Telegram’s Privacy Mode explanation states the difference.

Channel and group ownership can be transferred to another user. Telegram’s API description says the transfer uses the current owner’s two-step password; its error list also describes fresh-password and fresh-session delays. Plan the handoff before the owner disappears: ask the incoming owner to join the asset, confirm the current owner still has access to their login, and complete the transfer while both people can verify the result. Telegram’s ownership-transfer documentation gives the underlying requirements.

Telegram added a 2026 group behavior: if a group owner leaves, ownership transfers to an admin after one week, and the leaving owner can choose a successor immediately. That is a fallback for a group, not a replacement for an agreed handoff of a channel, bot, or personal account. A team should still name its successor and test permissions before departure. Telegram’s February 2026 announcement explains the group flow.

A checkmark is separate from access. Telegram’s verification guidance concerns notable channels, bots, and public groups and directs applicants to @VerifyBot; it does not turn a personal Business profile into a company-owned role system. Telegram Premium has its own subscriber badge, which also does not designate a channel owner. If a customer sees a badge, verify the asset and its operator independently. Telegram’s verification rules and Premium FAQ describe these different signals.

For the human login, turn on Settings > Privacy and Security > 2-Step Verification, add a recovery email that the account holder can access, and review Settings > Devices for sessions on old phones and laptops. Telegram’s own lost-phone instructions tell users to terminate sessions on a missing device and keep control of the phone number. A colleague who can post in a channel is not automatically a recovery contact for the owner’s account. Telegram’s account-security FAQ gives the menu paths.

Use an asset-by-asset offboarding pass: remove the departing person from group and channel administrator lists; transfer any group, channel, or bot they own; review connected bots on the Business profile; regenerate tokens held in their systems; and check active account sessions on devices they used. Record the new owner and the date. A common miss is removing the person from the channel while leaving their automation server with the bot token, so scheduled posts continue after the person has left. Another is rotating the token while their personal account remains the BotFather owner. Both require different actions.

Telegram does not provide a business-portfolio audit log in the material governing these assets. Keep your own access register with asset link, human owner, admins, connected bots, token custodian, and last review. Compare it to the platform’s live controls every quarter and after any agency change. A list of names from last year is not proof of current access; the channel’s administrator list, the profile’s connection settings, @BotFather, and each account’s Devices list are the checks that matter. Telegram’s channel administration, connected-bot controls, and BotFather instructions define those surfaces.

Treating Premium as corporate ownership. A paid subscription attaches Business features to a user account. If a founder pays for Premium on their personal number, that does not make the company owner of their private chat history. Decide whether customer communications should instead enter a transferable channel or bot, and document what stays personal. Telegram’s Business model makes the user-account basis clear.

Giving a bot every right because it needs to reply. A connected bot needs reply for answers, but profile editing and Stars transfers are separate rights. Review the rights list before the connection goes live. For example, an appointment bot should not be allowed to change the account’s username merely because the vendor’s setup checklist says “enable all.”

Confusing channel admin with bot operator. A publisher can be an administrator in a channel while the bot that posts there is owned by an agency’s private Telegram user. When the agency leaves, removing its human administrator may leave the bot and token active. Inventory the human admin, bot membership, BotFather owner, and token holder separately.

Assuming a bot sees every conversation. Privacy Mode limits group updates, and a connected business bot is restricted by the account holder’s recipient scope. A test message sent from an excluded contact proves more than a vendor demo from a new contact. Telegram’s bot guide and business connection controls explain the two filters.

Waiting until a phone is gone to plan succession. Telegram’s recovery guidance depends on the number or an existing signed-in device. Before a planned departure, check the number, active session, two-step password, and ownership-transfer eligibility. A last-minute request may hit the fresh-session delay described in the transfer API.