Letting leaders post to their own team

Your worship leader can message her own team from her phone, with no staff login and nothing for you to switch on. Most churches never find this, so it is worth telling your leaders it exists.

Who gets it

Anyone who is a lead or co-lead of an active team, or a leader or co-leader of an active group, and who has a churchHQ account. That is a membership role on the team or group itself, not a Scout role and not a permission, so you grant it by naming someone a leader on the roster. See Members, leaders, and join requests and Setting up a serving team.

Nobody needs a dashboard login for any of this.

What they do

1. 1

   Open the Updates tab

   A leader sees two extra pills in the header that other members do not: Post and Sent.

2. 2

   Tap Post

   Under Who's this for? they pick one card. Each card names the team or group and its size, like "Team · 14 members". A leader who leads exactly one thing has it chosen for them.

3. 3

   Write it

   The Message field takes plain text up to 5000 characters, with the placeholder "What do they need to know?". They can also Attach a service or group.

4. 4

   Send

   The button reads Send to {the team or group name}.

One audience per post, which is the difference from the staff composer. A leader who leads two teams posts twice.

Delivery is identical to a staff post: a feed card for every recipient with a churchHQ account, plus a push notification to anyone running the installed app. See Who receives an announcement.

What they can see afterwards

The Sent pill opens What you've sent, described on screen as "Your posts and who's seen them. Tap one to read replies." Each row carries Seen by 4 of 12, an acknowledged count, and a reply count.

The author never receives their own post, so it will not appear in their feed. It lives under Sent.

Replies

A member can reply inside an update thread. By default the reply goes to the whole audience. Ticking Send privately to {author} sends it to the author alone, and it renders with a Private chip. The checkbox resets after each send.

A reply notifies the update's author and nobody else. There is no fan-out to the audience, and the author's own replies notify no one.

The trust decision

There is no approval step, no moderation queue, and no preview for staff. When a leader taps send, it goes.

What you keep:

• Visibility. The staff Recent updates list is church-wide, so posts written by leaders from their phones appear there alongside yours.
• The audit log. Every post is recorded in Settings → Audit log.
• A way to remove one. Deleting a post pulls it from every feed. Only the author or the church owner can do it, so removing a leader's post means either asking them or acting as the owner. A push that already landed stays landed.
• The roster. Leadership follows the roster, so removing someone as a team or group leader takes the ability away.

Give leaders a sentence of guidance before you point them at it. The audience cannot be changed after the fact, and neither can the words.

Next

• Posting an announcement
• What your church sees in the app