Calling-based access
Access that follows the calling, not the person.
Group chats and shared inboxes do not know who is in which calling, so access drifts every time a ward sustains someone new. CouncilFlow ties what you can see to the calling you currently hold — and updates the moment that calling changes hands.
How it works.
Access in CouncilFlow is granted to a calling, not to a name on a list. That one shift solves a long list of small ward-leadership headaches at once.
Scoped to a calling, not a person
Each council is visible to whoever currently holds the relevant callings — bishopric, ward council, RS presidency, EQ presidency, and so on. The role does the gating, not a hand-managed user list.
Assignments follow the calling too
When work is assigned to the elders quorum president, it stays with whichever brother holds that calling on any given week. Nothing has to be re-routed by hand.
Private councils stay private
Bishopric youth committee, welfare-sensitive items, and other restricted discussions only appear to the callings that should see them. There is no shared inbox where a stray invite leaks the wrong context.
When a calling changes.
Sustainings happen often enough that access management cannot be a weekend project. CouncilFlow handles the handoff automatically the moment the bishopric records the change.
Step 1
A calling changes
The bishopric records the new calling in CouncilFlow — the same way they would update their own ward roster.
Step 2
Access updates immediately
The new person sees every council, thread, and open task tied to their calling. The previous holder loses access on the same beat.
Step 3
Nothing falls through the cracks
Open assignments, due dates, and threaded context all stay attached to the calling, so the new leader walks in with the same picture the previous one had.
The bishopric confirms calling changes inside CouncilFlow itself. CouncilFlow is not connected to LCR or any Church-of-record system, so the ward stays in control of when access flips over.
A note on privacy.
CouncilFlow is an independent tool. It is not affiliated with The Church of Jesus Christ of Latter-day Saints and is not connected to LCR, ChMS, or any other Church-of-record system. No membership records, ordinance data, or directory information is pulled in — ward leaders enter the callings they want CouncilFlow to know about, and nothing more.
A look at it.
Real product screenshots land in a later phase. For now, here is what calling-scoped access looks like from each side.
- Councils visible to the current calling holder
- Calling change confirmed inside CouncilFlow
Bring CouncilFlow to your ward.
Setup takes a few minutes. Invite your council and CouncilFlow handles the rest before the next meeting.