An automation belongs to a team, not to a person, so every member of that team reads the same triggers and templates. Changing what they say is a narrower question than reading them, and BrokerPlus keeps the two separate on purpose.
Authoring Against Working the Queue
Two different things "change" could mean here, and they are answered differently. Working the queue is approving a draft, sending it, or dismissing it: a support member's ordinary day, and it needs no special permission at all. Authoring is rewriting the rule itself, the trigger that starts it, the steps and templates it runs, the block list, or the assistant settings that produce any of those. Authoring changes what every future client on the team hears; working the queue only decides what happens to what a rule already produced. The permission below, Manage automations, gates authoring alone.
Who Holds It Without Being Granted It
Two people never need this handed to them. An admin at the brokerage level holds it everywhere by default, the same oversight that opens every team's book to read. And a team's own broker, the person accountable for that team, holds it on their own team automatically the moment they are its broker, with no separate switch to flip. Anybody else on a team, including a teammate holding every other permission on their row, changes nothing about that team's automations until its broker hands them this one specifically.
Granting It to a Teammate
A team's broker opens a teammate's row from Invite Your Team and turns on Manage automations there. What it hands over is stated plainly on the same row: the teammate can change the team's Pulse triggers, templates and block list. It does not touch the queue, which the teammate could already work before the grant existed.
Why a Control Says to Switch Teams
Authority follows the exact team an automation belongs to, never the brokerage as a whole. An admin's brokerage-wide oversight opens every team's book to read, but it does not carry into rewriting a sibling team's automations: that authority still runs through the team's own broker, and an admin who has never joined that team's roster meets the same refusal a stranger would pressing save on one of its triggers. Building on the canvas asks for your active team specifically, since a new automation is filed under whichever team you are currently working. Saving one while you are looking at a team you do not belong to asks you to switch to a team you actually stand on first, rather than quietly filing it somewhere you never intended.
What a Teammate Without It Still Sees
Losing this permission costs nothing to read. The Library still lists every trigger and template running on the team in full, because working the queue means recognizing what produced the draft in front of you. What closes is the canvas itself: opening it without the grant sends you straight back to the Library instead of an editor whose every button would refuse the press.
What to Do Next
- Invite Your Team to hand a teammate the Manage automations permission.
- Review the Pulse Queue for the part of this job that needs no grant at all.
- See Everything Running Automatically to read what is on before deciding who should be able to touch it.