KamoCRM

Design the org chat policy engine and its Policies tab

Docskamo-internal
Shipped
21 ஆகஸ்ட், 2026 அன்று 10:28 PM UTC
Author
kamo
Commit
3c54ab8

Rules are an ordered list over ordered member pairs; the first match decides, so every verdict names exactly one rule and the UI can always explain itself. Selectors cover departments (with the sub-department tree), job titles, members, member type and work location; qualifiers cover the relative predicates that selectors cannot express -- same department, different manager, in my chain. Group chats get no policy axis of their own: the invite gate is the DM gate. A room is shared context, so the only check is that whoever adds a member is allowed to DM them. A room that shrinks back to two denied members re-evaluates as a DM and freezes, which is the only bypass that model leaves open. Records two defects found on the feature's path and folded into it: the message send endpoint never checks session membership, and the directory route the add -members picker calls does not exist.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing