Settings, team, and access
The Settings section brings together everything that applies to the bot as a whole: its parameters and behavior, team member access, API tokens, and templates. The header shows the bot's status, user count, requests today, and remaining request balance.
General
- Salutation — how the bot addresses the user.
- Position in list — the bot's sort order among others.
- User display mode — "Show all" / "Active only" / "Paid only."
- Interface language — Russian / English.
Behavior
Bot operation flags:
- Request consent for personal data processing.
- Send the user an error message.
- Support HTML entities in messages.
- Combine media groups into a single message.
Bot access (team and roles)
In the "Bot access" block, add team members by name and @username with a role. The role determines what the person can do:
- Owner — full access to everything, including settings, team management, and bot transfer. The owner cannot be removed.
- Administrator — manage the bot, reactions, and data, but cannot transfer the bot to another account.
- Operator — works only in the Chats inbox: messaging users, transferring and closing conversations.
This lets you onboard support operators without giving them access to the full bot builder.
API tokens
The "API tokens" block creates keys for accessing the bot via the REST API. A token is shown once at creation time — copy it immediately; only a masked version is visible afterward. See REST API and tokens for details.
Templates
A template is a snapshot of the bot's settings and all its reactions that can be reused:
- Create template — saves the current bot (its settings and reactions) as a named template.
- Apply template — copies the template to another bot: settings are replaced with the template's values, while reactions are added to the existing ones (they are not overwritten).
Convenient for rolling out a standard bot across multiple projects. See also Bots and connection.
Bot maintenance
- Synchronize — update the bot name from Telegram.
- Change token — update the token after regenerating it in @BotFather.
- Change owner — transfer the bot to another account (irreversible).
What's next
- REST API and tokens — programmatic access.
- Bots and connection — token, transfer, templates.
- Chats and operators — the Operator role in action.