Church dashboard · preview

Sacristy

The quiet room where a church keeps its own page: appeals, event tags, and a code for the back of an order of service. This is a placeholder. There is no account, no password, and no form that sends what you type.

Sample church

St Michael and All Angels

id little-badminton

One example appeal is loaded. It is the leaking roof, and it is not a live campaign.

Claim this church

Preview

A mock-up of how a church would show it may receive gifts. The fields do not check a register, and they do not keep what you type.

Each yearThe claim is re-verified. A church does not stay connected on a check made once.

Two peopleAny change to payout details needs two-person approval. One officer cannot retarget a gift alone.

Services and events

Preview

A verified church would post the weekly services and the one-off events here. The rows are an example. The fields do not save, and they are not the times of St Michael and All Angels.

Appeal target

Example · treasurer preview

A treasurer would set the title, the purpose, the target, and the amount the church reports as raised. This form does not save. The CRM flag is off, so the worker route refuses the write. Donate stays disabled until legal sign-off.

Volunteer request

Example · preview

A small, dated ask. The church is reached through the form on the page, not by a published email address. Saving is off while the CRM flag is off. A Bells note to people who confirmed services updates would be built and then left unsent.

Supporters

Example

A verified church would see who asked for which kind of news, for a letter or a call that needs a person rather than a list. These four rows are an example. They are not people, and no address is shown.

Services and events: 3
Appeals and finances: 2
Lychgate: 2

Example followers by interest
Follower	Services and events	Appeals and finances	Lychgate
Example follower A	Yes	—	Yes
Example follower B	Yes	Yes	—
Example follower C	—	Yes	—
Example follower D	Yes	—	Yes

Bells

Preview

A verified church would write an impact update here and send it only to people who confirmed the matching consent. The CRM flag is off. This page does not call the worker, and nothing is sent.

What the email would look like

From: St Michael and All Angels <[email protected]>
To: Example follower B <[email protected]>
Subject: EXAMPLE — Before and after the roof

EXAMPLE.

The leaking-roof appeal on the flagship page is an illustration. This note does not report work done, money raised, or a photograph of a repair.

It would have gone only to addresses that confirmed “Appeals and finances” for this church. Example follower B is not a person.

List-Unsubscribe, one click, would be a header on this message. The link in this preview goes nowhere. The PCC would be the controller of the list. Every Church would be the processor. Draft, pending legal review.

Example · volunteer ask · not sent

A request for a tower visitor guide on 7 November 2026 would be offered only to followers who confirmed services updates for this church. The worker builds that Bells message and returns not_sent. No address is mailed, and the church's own email is not on the ask.

A code for an appeal

The address is shaped as https://everychurch.co.uk/c/<id>/<appeal>?ev=<event-tag>. The code is drawn here, in the browser.

Church idAppealEvent tag

Use lowercase letters, numbers and hyphens. The event tag becomes ?ev=. Nothing typed here leaves this browser.

https://everychurch.co.uk/c/little-badminton/leaking-roof?ev=sunday-preview

Open the preview page

The code points at everychurch.co.uk, which is not yet serving this preview. Only the leaking-roof sample has a page in this build.

Drawing the code