Choose who may use the bot
Add Telegram role policies so the bot answers the right people, gives a group extra instructions and keeps operator controls for the right people.
How a role policy works
- A policy maps an identifier to access, a role name and optional extra instructions for the room.
- The identifier can be a Telegram user ID, an @username or a whole chat ID. A whole chat ID admits everyone in that chat.
- The first matching named policy applies, and
*is evaluated after every named policy whatever its position. Keep*last so the order is readable. - A sender who matches no policy is ignored, and the bot does not explain why.
- A policy does not replace identity. The sender also needs a linked Chetty account, and that account's Project access and tool permissions apply to the turn.
Add a role policy
- Open Settings → Plugins → Telegram and find Role policies.
- Add a policy with a Telegram user ID, an @username or a chat ID. Repeat for each person or group that may use the bot.
- Optionally add extra instructions for the room and turn on the administrator flag for operators.
- Add a
*policy last if every sender should be admitted. - Save. The change requests a restart, because the bot reads its access rules at start.
Operator controls
A policy with the administrator flag set makes its senders operators. Operators get:
- The shared
/model,/reasoning,/displayand/contextpickers. - The room controls
/stop,/stats,/compactand/restart.
/restart restarts Chetty for everyone in the instance, not just for that chat. /project needs no operator flag; any admitted sender can switch the conversation into one of their own Projects.