Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Choose who may talk to the bot
Channels and chatbots

Choose who may talk to the bot

Add ordered admission policies so the bot answers the right people, and give a shared room optional extra instructions.

How a policy is chosen

  • The first matching rule decides admission, the extra instructions for the turn and Teams room administration.
  • A rule may name a person — Entra object ID, Teams account ID or UPN — a whole conversation ID, or * for everyone.
  • * is evaluated after every named rule, whatever its position. Keep it last so the order is readable.
  • A conversation rule applies only to that conversation, so a person's own rules cannot describe access in every shared chat.
  • A policy does not replace identity. The linked Chetty account still owns Project access and tool permissions.

Add or edit a policy

  1. Open the MS Teams page → People & access. The list works even before the bot has met anyone.
  2. Select Add policy, or choose a person and Configure access to add a rule for that person.
  3. Fill in the identifier, an optional role name and optional extra instructions, then select Save policy.

Typing into the form saves nothing by itself: Save policy submits the complete rule. A person may have rules under several identifiers. Choose the identifier you want, because editing or deleting one leaves the others in place.

The Teams administrator flag on a policy allows room-administration commands and marks the conversation as trusted. It grants no Chetty account, Project access, tool permission, Microsoft access or instance administration. Teams administration and Chetty administration are different things.

Delete a policy

  1. Select the delete control next to the rule.
  2. Confirm in the dialog that opens.

The selected rule is removed. Other identifiers, conversation rules or * may still admit that person, and personal-chat sign-in keeps working. Deleting a policy never unlinks the Chetty account.

When saving fails

  • The form stays open. The save failed; nothing was stored. Read the message, correct the value and submit again.
  • "The policy changed while this form was open." The saved list moved on. Close the form, open the current rule again and repeat your change.
  • "Saved. The change takes effect after the pending daemon restart." The change is stored but not active yet. It applies when the requested restart completes.