rolely
There are two principles behind the separation: Customer and knowledge management are divorced: the operator can neither create nor validate knowledge; he can only offer a ticket to learn. Support management and AI management are also divorced: the support administrator will not turn on autonomy, the AI administrator will not connect the channel. Only the owner can delete the content of the tickets.
The rights are always checked, not the names of the roles: the buttons that are not entitled to, the panel simply does not show, and the server rechecks each action.
The role is clearly assigned
An account without an assigned role does not get access to the module: it will see a denial with an explanation, not tacit rights. The last owner cannot be downgraded, the module will fail.Operators from Telegram
The Add Operator panel works in two modes: search by name or nickname among those who have already written to your bot, and add by numerical Telegram User ID. The operator gets a role and can immediately respond to customers in the operator forum. This creates a full-fledged Axottle user with Telegram attached and the right to access support — there is no separate “accountless” entity anymore. Such a person is visible in Settings → accounts, and in the list of operators: it is the same record, not two. It doesn’t have a password, but it does: if you set up a login via Telegram, it logs into the support portal using the “Log in via Telegram” button, and the statistics are collected from the first answer. The role of “Owner” can not be added – it requires a password. The operator with the password in the card has a “Telegram ID” field: link it so that the person can respond from the Telegram forum. Messages from accounts that the module does not know do not reach the client.Team cards
Each team member is shown with a card: a real avatar from Telegram (otherwise a monogram), name, nickname, identifier, source (“Panel” or “Telegram”), activity and role. If the operator already has statistics, the card shows processed tickets, reopenings, average scores and late SLAs. The operator can be temporarily disabled with the “Disable” button: the inactive participant loses his working rights (for history, he is counted as an observer). Deleting the operator removes the role in support; if the person did not have a password and he existed only for support, the account itself is deleted. Users with a password are saved and remain in Settings → Accounts Z. Role assignment and change of settings fall into the general panel audit log, including who issued the role and when.
