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, each adult's volunteer row (application, interview, background check status with its requested, completed and expiry dates and the provider's name, training and renewal, policy signed and its edition, shadow shift and placement) and any student helpers by first name, age band, team and parent contact. The church's services, funds, teams (each marked if it serves with minors), groups, events, roster and usher headcounts live in the account's own church lists, and training sessions and policy editions in their own record. 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.

Trellis records what the office recorded. A background check is only a status and dates: Trellis never runs or orders one, has no connection to any screening company, keeps no result, report or case number, offence, credit or driving record, Social Security or license number, address or date of birth, and refuses them in every note. Completed means your provider's check finished on that date; placing someone on a team is your church's own decision, and Trellis never says anyone is cleared, safe or compliant. Saving a household keeps the church tags on its linked contacts and moves the guest follow-up opportunity forward a stage, never back; volunteer steps write nothing else. Trellis reads every open household of the pipeline page by page, so none drops off past the 1,000 opportunities Seedly's board shows, and every date is read in your church's own time zone. Counts and totals read every household while the search narrows only the lists, red marks only the named alerts, and each view says when it is still reading instead of showing an empty list. The Volunteer onboarding board is optional and never synced: its Interview scheduling, Check requested follow-up and Placement welcome drafts run only when someone in your office moves an opportunity into that stage in Seedly. 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. Trellis has no child check-in and refuses children's exact ages, birthdays, names lists (also after youth words, as in “Youth: Leo, Ava, Sam”), allergy and custody notes. Care requests are category labels and health details are refused. Giving is only what the office typed in: Trellis never processes, imports or receipts gifts and makes no tax claim. Access codes, Wi-Fi and portal logins, card, bank and routing numbers are refused in recorded text, while church text such as John 3:16, Room 204 and Background check requested 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, every name answer refuses check results and offences, and the Volunteer application has no identity field. 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.