Skip to main content

Not yet available

This page was wrong in both directions, and it is worth saying so plainly rather than quietly fixing it. It listed capabilities as forthcoming that had already shipped and were on for every church — so a church that read it decided not to go looking for features they already had. It also said all of them were "in use by pilot churches", and there is no pilot.

So: what is here, and what is not.

Already here​

These are on for every church on the right plan. If you cannot see one, that is a plan tier or a permission rather than a rollout — ask your admin, or talk to us.

Online giving​

Card and bank gifts on a branded page, funds, recurring gifts members manage themselves, manual batches for the cash and cheques counted on a Sunday afternoon, and annual tax statements that generate and email themselves. Because giving runs on the same person record as everything else, a member's giving sits alongside their attendance and their groups.

Service planning​

The running order, who is on the platform, and a song library tracking keys, arrangements and the last time you sang something — which is usually the question nobody can answer on a Wednesday.

Campaigns and communications​

Message an audience rather than one person at a time. Pick from anything Passport already knows: first-time guests from last month, everyone in a ministry, members who have not attended since March. Rolling out church by church, so if you do not have it yet it is coming to you specifically.

Automations​

Rules that run without anybody remembering them. When a visitor is registered, when attendance is recorded, when someone joins a group, when a form is submitted. Starter recipes cover first-time visitor follow-up, returning guest recognition, new group member welcome, birthdays, volunteer onboarding and absentee care. Requires the Plus plan.

Not available​

These are built but switched off, for every church, with no date. They are listed here so that if you have read about one somewhere you know where you stand — rather than hunting through settings for a switch that is not there.

Headings rather than a list, because the admin screens for these link straight to their sections — ui/src/constants/docsLinks.ts names each anchor, and a cross-repo test checks that every one of them still resolves. Flattening them into bullets broke all three, which is how a doc rewrite silently turns three in-product help links into dead ends.

Corporate fasting​

A church-wide fast with a start and end date, a daily focus, and a place for people to say they are taking part, without anybody keeping a list.

Sermon archive​

Publish sermon audio, video or notes so members can catch up on what they missed, with a public podcast feed.

Bible study pipeline​

Track home Bible studies from the first request through to completion: who asked, who is teaching, which lesson they are on, and what came of it.

Background checks​

Order checks through a screening provider and track the result against the person's record. There is a full guide for this one because the capability itself is complete; it is the switch that is off.

Genuinely not built​

  • Member directory — a directory members can browse themselves, so they can find the person who runs the Tuesday group without going through the office.
  • Multiple campuses — more than one campus under one account, with separate service times, attendance and teams, and roll-up reporting across all of them.

:::note Interested in one of these? Talk to us. We would rather tell you honestly where something stands than leave you planning around a date we have not committed to. :::

Next steps​