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.

Each service plan holds its service, day, target length, status and running order: every item's kind, the song from your library or a label, who leads it, its length, the key for a song and a short note. The song library holds titles, writers as text, CCLI song numbers, keys and tempos, and usage is counted on the server from the plans marked done, one use per song per service. Usage needs no clearing: a service's usage more than 13 months old whose plan has been cleared is folded into counts per song per six-month period, keeping each song's last use, so the plans record stays small year after year. The plans record holds twenty weekly services planned three weeks ahead, or twelve planned eight weeks ahead, with room to spare, and setup shows how full it is. 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 and a checklist. The church's services, funds, teams and positions, groups, events, 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.

Cuesheet records what the office recorded. Songs are titles, writers, CCLI song numbers, keys and tempos: no field holds lyrics, charts, recordings or links, item notes stop at 200 characters, and a chord chart typed into a song title, an item label or a note is refused, whether as four chord symbols in a row or as chords in square brackets the way chord-sheet services export them. Name boxes and public form name answers do not run that chord rule. Usage is a count for your church's own CCLI report; Cuesheet reports nothing and makes no licensing claim. 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, sending only from 10:00 to 19:30 church time; 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. Cuesheet has no child check-in and refuses children's exact ages, birthdays, names lists (including lists after youth words such as "Youth band: Leo, Ava and Sam"), allergy and custody notes. Care requests are category labels and health details are refused. Giving is only what the office typed in: Cuesheet never processes, imports or receipts gifts and makes no tax claim. Today, the day a card or prayer request arrived, the events offered on the event sign-up form and the day song usage is folded follow the church time zone. Counts and totals read every household while the search box narrows only the lists, and red marks only a named alert. Access codes, Wi-Fi, livestream and portal logins, card, bank and routing numbers and Social Security numbers are refused in recorded text, while worship song titles, keys, tempos and CCLI song numbers are 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. 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.