Quick answer: Give every branch a unit, build one filter audience per branch (they maintain themselves), and split communication into organization-wide broadcasts, branch-scoped notices, and head-only audiences for coordination.
How it works
Filter audiences per unit mean branch transfers never break your lists.
A “branch heads” audience built on the head flag reaches exactly the leadership layer.
Branch-scoped notices keep local noise out of the organization-wide channel.
Frequently asked questions
Can a branch admin message only their branch?
Organization admins send today; unit-scoped sending is arriving with scoped unit-admin permissions.
How do we prevent duplicate announcements?
One owner per audience — the composer’s recipient count makes overlaps obvious.