A clear path
to your workspace.

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

One contact-linked household record holds the household's status, how it found the church and who invited it, the guest path from planned visit to next step, an office note, its adults linked to Seedly contacts, its children as a first name and an age band only, the groups and serving teams it joined, recorded attendance, event sign-ups, gifts as recorded by fund, care requests as category labels and an editable checklist. The church's name, time zone, services, funds, teams with the positions each needs per service, groups, events, serving roster and usher headcounts live in the account's own church lists. The shared church lists fit one to three weekly services; a church with four or more should keep its roster and headcounts elsewhere for now.

What changed in 0.2.0, a free update for 0.1.0 owners: Bellrope now records attendance and usher headcounts as the office records them (0.1.0 took no attendance), adds three optional message drafts with every send step switched off (0.1.0 had none, and Bellrope still sends nothing itself), adds a not seen recently list with a Start re-engagement button on the Care view, and renames Households to People & households at the same address. Households, church lists, setup receipts and drafts from 0.1.0 carry over, and a 0.1.0 household's primary adult links to the contact its opportunity already has in one click, never added as a second contact; do not roll back to 0.1.0 after saving in 0.2.0. Bellrope records what the office recorded: attendance and headcounts are only what the office records. Saving a household keeps the church tags on its linked contacts and moves the guest follow-up opportunity forward a stage, never back. The three optional message drafts hold real texts and emails with every send step switched off, every text behind a check that the contact agreed to texts and every email behind one that they did not opt out, every text ending with the opt-out line, each draft added with a 10:00 to 19:30 church-time send window, and a paused check ending the run rather than sending; you add them only after ticking that you record consent, you can add them before your A2P campaign is approved, and nothing sends until your office reads each step and turns it on. Bellrope has no child check-in and refuses children's exact ages, birthdays, names lists, allergy and custody notes. Care requests are category labels and health details are refused, so a meal train or a hospital visit is kept while a diagnosis is not. Giving is only what the office typed in: Bellrope never processes, imports or receipts gifts and makes no tax claim. Access codes, passes, Wi-Fi and portal logins, card, bank and routing numbers and Social Security numbers are refused in recorded text, and so are lists of children's names, including after youth words and after a short phrase such as kids pictured or kids on the bus, while church text such as John 3:16, Room 204, Pass the plate and a team roster of adults is kept. That is a guard against accidental entry, not a guarantee, and the shapes it cannot tell from ordinary text are listed in the README. The five public form drafts hold only names, email, phone and fixed choices, with children counted and never named, and the card inbox shows an answer only when it is one of that question's own choices. Today, the day a card or prayer request arrived and a form's upcoming events are read in the church's time zone. Households are read through the kit's own paged query, so the views do not stop at 1,000 households. Install one church kit per Seedly installation. A matching Seedly church website template is available separately.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.