پایگاه دانش GetMyBot

Settings, team, and access

Change bot behavior, invite team members, set permissions, and enable test mode. Project and cabinet access.

در این صفحه

Use Settings to change the bot's behavior and manage team access. For example, you can enable test mode for yourself, give an operator access to chats only, or let an administrator edit reactions.

Check which project is selected at the top of the cabinet before making changes. Access to one project and access to the entire cabinet are configured separately. The header also shows the bot's status, user count, and request usage.

General

  • Address: the word or name people use to address the bot in a group, if this setting is enabled.
  • 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.

Test mode

In Test users, enter the Telegram/VK IDs of the owner and testers, up to 20 IDs. Their messages run through normal reactions, but requests are not charged for starting a reaction, delivering messages, AI, or integrations. In the request log, these rows carry a test badge. The Charged column shows what an ordinary user's request would have cost. To find your ID, send /start to the bot and open your profile in People. API: PATCH /api/bots/{botID}/settings with {"test_user_ids":[123456789]}; MCP: update_bot_settings.

Project access

The "Project access" card in the bot settings opens one bot to other people: each of them signs in with their own email and sees the project in their own cabinet. To give someone every bot in the cabinet at once, including future ones, use cabinet access.

The card is visible to the bot owner and to members with the "Access" right. The list has three kinds of rows:

  • Member: an account that accepted the invitation and already works with the project. A badge shows whether they have 2FA on.
  • Invited: the invitation is sent but not accepted yet. The row shows the date the link is valid until. Such a row grants nothing.
  • Legacy row: a row from the old version of the screen, where people were typed in by name. It grants nothing and can only be deleted.

The owner carries the "Owner" badge: they hold every right and cannot be edited or removed.

Roles

A role is a preset set of rights:

  • Admin: every project right, including access management.
  • Manager: chats, analytics, viewing support tickets and replying in support.
  • Operator: chats, viewing support tickets and replying in support. This lets you onboard Chats operators without opening the bot builder to them.

Changing a row's role replaces its rights with the new role's preset. A member who does not own the bot can only assign a role whose rights they all hold themselves. Nobody can change their own role or rights.

Permissions

The "Permissions" button opens fine-grained settings. The effective permissions are listed at the top, followed by checkboxes in groups: Data, Content, Automation, Support, Analytics, Integrations, AI, Security. Each change is saved immediately, and the role then stays as a label.

  • You can only grant or remove a right you hold yourself (the owner holds all of them). Other checkboxes are disabled, and the server rejects such a change.
  • Sensitive rights: Export profiles, Revenue in analytics, Integration secrets, and Enforce two-factor. If you do not hold one, the dialog says explicitly that you cannot grant it.
  • If a right has no effect without another one (for example, "Edit profiles" without "View profiles"), a warning appears under it.

Project invitation

  1. Click "Invite", enter the email and the role ("Operator" by default), and click "Grant access".
  2. The address receives a one-time link of the form /invite?token=…, valid for 72 hours. Only the recipient sees the link; it is not shown in the interface.
  3. The person opens the link and signs in with the account on that email (or registers one). Once accepted, the project appears in their list right away.

The invitation can only be accepted from the account with that verified email:

  • if the link is opened under another account, the page offers to sign in with the right one (the "Add account" button), and the invitation stays valid;
  • if the email is not verified, the page offers to resend the verification email; once verified, click "Email confirmed — accept";
  • a used, expired, or unknown link is invalid: ask for a new invitation.

Inviting the same address again replaces the previous invitation: a new 72-hour link is sent and the old one stops working. The bot owner's own email cannot be invited, the server answers 409.

Editing and revoking

Change the role in the row's dropdown and the rights in the "Permissions" dialog. An invited person's role and rights can be adjusted before they accept. The trash button revokes a member's access, cancels an invitation (the emailed link stops working), or deletes a legacy row.

Inviting and changing roles or rights requires the bot owner's plan to include roles. Otherwise the list stays visible, a plan hint replaces the "Invite" button, and the server answers 402. Revoking access works on any plan.

Cabinet access

Project access opens a single bot. To give someone every bot in the cabinet (your account), including future ones, plus the cabinet's own rights (billing, creating bots, team), open Account → the "Cabinet access" card.

Roles:

  • Administrator: all rights.
  • Manager: chats, reactions, analytics, profiles, events, segments, content, and campaigns (view and edit), viewing support tickets and replying in support.
  • Operator: chats, viewing profiles, viewing support tickets and replying in support.
  • Finance: viewing the balance and payments only, no bot rights.

The cabinet owner is listed separately and cannot be edited or removed. You can fine-tune a role's rights with the "Rights" button; the role then stays as a label. Cabinet rights:

  • View balance and payments (billing.read);
  • Payments and top-ups (billing.write);
  • Manage the cabinet team (team.manage);
  • Create bots (bots.create);
  • Delete bots (bots.delete);
  • Security (security.manage);
  • Audit log (audit.read).

The "Rights" dialog also sets bot rights, which apply to every bot in the cabinet.

Access can be granted by the owner or by a member with "Manage the cabinet team"; nobody can grant a right they do not hold. The feature requires a plan with roles, otherwise the server answers 402.

Invitation

Access is granted by email: click "Invite", enter the address and the role. The invitee receives a one-time link valid for 72 hours. The invitation can only be accepted from the account with that verified email:

  • if the link is opened under another account, the page offers to sign in with the right one, and the invitation stays valid;
  • if the email is not verified, verify it first using the email link;
  • a used, expired, or unknown link is invalid: ask for a new invitation.

Cabinet access is managed from the web session only: these operations are not available with an API token or via MCP. How cabinet rights apply to API tokens: see The token's account.

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 Projects and channels.

Bot maintenance

  • Synchronize: fetch the bot's current name from Telegram and set up message delivery again if the bot is active. This is the usual way to restore the connection when the bot appears offline, and it is safe to repeat. Other settings, status, and sort order do not change. Technically, the action calls Telegram getMe, rereads the bot state, then registers a webhook only for an active bot. If the Telegram channel was already turned off, the check stops before getMe. Message delivery is not started for paused or frozen bots. If the channel is turned off or the bot is activated during synchronization, the name may be saved before an error is shown. If Telegram rejects the new webhook, the confirmed name is kept, the new receiver is discarded, and the existing bot process keeps running and reporting its status.
  • Channels: connect a channel or update its credentials, including a Telegram token regenerated in @BotFather. If the Telegram channel is not shown, choose “Change token” in the same window.

Forwarding user messages

The project must have exactly one enabled Telegram channel. Enable Forward user messages and select a chat where the bot can post. Optionally enter the numeric topic ID, then save the settings. Notifications include the sender's details and the original message time.

Select Add reminder and enter the number of minutes after the first message. You can add up to 20 increasing intervals from 1 to 43,200 minutes. Reminders stop when a reply has been delivered. In a group, an administrator or creator can reply from their own account; anonymous administrators cannot pass the check. The bot should be a group administrator so Telegram can reliably verify the sender. In a private chat, its other participant can reply. WhatsApp's usual 24-hour reply window applies; after it closes, use an approved template in the service.

Bot health

The "Bot health" card shows whether the bot is available now. If a failure is detected, it shows the cause, automatic restart count, next retry time, and last error. You can inspect the restart history for the current incident and past incidents with their duration and cause. A bot you turned off is shown as turned off rather than offline; previous incident history remains. For details, see Projects and channels.

The same card holds the notification settings:

  • Notify the bot owner when the bot is offline: the bot's owner gets the notification (in the bell and by email), and the bot messages the same chats as the wallet-exhausted notice.
  • Threshold, minutes without a heartbeat: a whole number 1–1440, 5 by default. An empty, fractional or out-of-range value is not saved and is not silently adjusted: the form shows an error.

Only the bot owner or a member with the "Reactions" right can change these two settings; everyone else can view the state but cannot edit the settings.

  • Change owner: invite a new owner. The invitation is valid for 72 hours. The project stays with you until they accept, and you can cancel the invitation before then. Once they accept, you lose access to the project.

What's next

Support operations and security

Support settings define the timezone, weekly coverage, breaks, overnight intervals, holidays, overflow group, and published auto-replies for working and non-working time. Use the availability preview before saving a schedule. A routing rule never substitutes an unavailable arbitrary member: it uses an eligible least-loaded candidate, configured overflow, or leaves the dialog unassigned.

Only the bot owner can require two-factor authentication for bot members. Review the affected-member count and the enrolment remediation path before enforcing the policy. Roles control access to bot configuration, support data, analytics and security policy; neither a role nor support staff can view an account's authenticator secret, recovery codes, or trusted-device token.