Skip to main content
Give a team the Manage announcements permission on a team role, so it only applies to the announcement rules and post templates that team owns. Set the owning team using the Announcement rule owner field (or Template owner for a template) when you create or edit it at Settings → Announcements. Once owned, only members of an owning team with the permission, or anyone who holds it account-wide, can manage it. Manage announcements is in the Standard role by default, so you’ll need to remove it there first. Changing who owns a rule or template is an account-level action. It needs Manage announcements account-wide (typically an admin), so a team-role holder can manage what their team already owns but can’t reassign it to another team.
Your default template can’t be owned by a team, and choosing which template is the organization default is always an account-level action.

​
Announcement rules that run on private incidents

Setting an announcement rule to announce private incidents requires a different permission: the Manage announcement rules that run on private incidents permission. This is a broader version of the Manage announcements permission. It also covers creating, editing, and deleting announcement rules, so someone who holds it doesn’t need Manage announcements as well. It can be granted through a team role, so a team can manage rules that announce their own private incidents. A team-role holder needs it for every one of the rule’s owning teams.
Announcing all private incidents (not just an owning team’s) always requires the Manage announcement rules that run on private incidents permission account-wide, since it reaches incidents no team has been given access to.
See Team roles for the full setup, and Announcing private incidents for the per-rule options.

​
FAQs

They can be managed by anyone who holds Manage announcements account-wide. Until you remove it from your base roles (typically Standard), that’s everyone.
Yes. You can assign multiple owning teams, and a member of any one of them (with the permission granted to that team) can manage it.
Anyone who holds Manage announcements account-wide can manage any rule or template that doesn’t run on private incidents, regardless of which team owns it. Rules whose scope includes private incidents also need the Manage announcement rules that run on private incidents permission. See above.
Yes, if they hold the Manage announcement rules that run on private incidents permission for the rule’s owning team(s). They can then set the rule to Private incidents for owning teams, the private incidents those teams can access. Announcing all private incidents requires the permission account-wide.
You need the Manage announcement rules that run on private incidents permission for every owning team (or account-wide). On a rule owned by teams A and B, holding it for only A isn’t enough. This is stricter than Manage announcements itself, where holding it for any one owning team is sufficient, because the rule can announce the private incidents of any owning team, so whoever sets the scope needs authority over all of them.