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, the guest path, 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, a checklist and each adult's pathway steps with the class, date and sessions attended. The church's name, time zone, campuses, services, funds and teams with positions live in a small directory in the account's settings (large team lists move to a stored list of their own), and the lists that grow live on stored lists of their own in your Seedly database, one per roster week, headcount year and event year and one for the groups, so they keep growing without a ceiling. Sized for a church with two campuses and six weekly services: a full roster week of 180 people serving is about 53 KB of a 256 KB list, a year of headcounts at six services about 55 KB and a year of 120 events about 23 KB. Roster rows clear after eight weeks when the roster is saved, a year of events can be cleared once it ended more than a year ago, and household attendance older than three years and gifts older than seven fold into yearly counts, so nothing blocks a new entry. The pathway's steps and classes have their own stored list. Remove all church records in setup deletes the church lists, the stored lists and the pathway, because deleting a Seedly account does not. It leaves only a small marker with no church data, so a page left open from before can never save its old lists or pathway back over what the office enters next.

Waymark records what the office recorded. 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 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. Waymark has no child check-in and refuses children's exact ages, birthdays, names lists, allergy and custody notes and a child's baptism or dedication in notes. Care requests are category labels and health details are refused. Giving is only what the office typed in: Waymark never processes, imports or receipts gifts and makes no tax claim. Access codes, Wi-Fi passwords (including one written after the network name) 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, Baptism class, a team roster of adults, Bible names in a lesson title and a youth band's instruments listed together 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 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 pathway does not stop at 1,000 households, and Giving, Groups and Care counts read every household while the search box narrows only the lists. A contact deleted in Seedly is never offered or newly linked and never gets a tag, and its household still saves; Add as a contact is refused only for the primary adult while the household's own contact is still in Seedly, and the household editor searches every contact by first name, email or company. Setup flags any QR code, value, snippet or draft whose form was deleted, adds and removes in steps on a large account, and shows how much of the account's record the kit uses. 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.