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 registration is an opportunity in Event registrations, linked to the household's contact, holding the event, the household, the status, the date it came in, its people as row IDs from that household (never a copy of a child's name) with a cabin, room, bus, van, tent or table for each kind the event uses or a recorded not needed, an adult's role and a leader's church steps as a status, each child's permission form and medical release as received yes or no, the amount due, a scholarship and payments as recorded, and a short note. Registration events live in their own account record with their dates, place, prices and deposit as recorded, capacity, spaces and readiness list; it shares the Seedly account's one stored document with the church lists and setup's receipts, and a save that would fill that document is refused with what to clear, never half-written. Households keep the shared church record: adults linked to Seedly contacts, children as a first name and an age band only, groups and teams, attendance, sign-ups, gifts as recorded by fund and care requests as category labels.

Bedroll records what the office decided. It creates each registration's opportunity at the stage its record has reached and never moves it afterward; the office drags it in Seedly. A stage draft runs only when a registration is dragged into its stage on the Seedly board, not when Bedroll records a registration at a later stage, and the Registrations view marks a board that is behind. The Forms, Balance and Packing list tasks are due 10, 14 and 7 days before the event, read from the registration when the draft runs. Bedroll reads every open registration and every open household with its own queries, past Seedly's 1,000-opportunity board limit, and today, the strap, the inbox days and the server's own checks (clearing an event a year after it ends, the 120-day window of finished events, marking a registration attended only once its event has started) follow the church time zone. The card inbox, the Event registration form inbox, prayer requests and the consent counts read within a fixed budget on any size of pipeline, matching each submission to its household with one indexed read, and say how far they got when the budget runs out or a form holds more than its newest 200 submissions, so a busy church's inbox never fails on size. The registration events record holds a busy year: about 18 events of 40 cabins, rooms or buses at a time fit, up to 40 events, and at 40 the editor names the earliest event and the day it can be cleared; the README gives the sizing. Every Seedly write re-reads the account's settings document, so on a large account Bedroll does long jobs in steps that each stay within Convex's read limit, and the page goes on by itself and shows how far it got: draft due dates after a start-date move, setup's adds and removals, a large household's church tags and re-engagement. Each board move saves that household's registration and says so when it fills a space past its capacity. Lists that follow the search box say showing N of M while their counts read every household, red carries only an alert's own name, and every view says what it is still reading instead of an empty list. A family marked attended as it arrives stays on the board, in every count and in every alert until the event ends. A household has one open registration per event, an event keeps its currency once it has a registration, and moving an event's start date moves its registrations' task due dates. Bedroll takes no payment, sends no payment link and issues no receipt; amounts are what the office typed, in the event's currency. A child's permission form and medical release are received yes or no; their contents stay on your church's own paper or secure form, and medicines, allergies, diets, injuries and other health details, and behavior, custody, pickup and rooming-restriction notes, are refused in every note. Counts of adults and children per space are shown, never judged: Bedroll makes no safety, supervision or compliance claim, has no room-sharing field and records a leader's church steps only as a status, never a check result. Saving a household keeps the church tags on its linked contacts and moves the guest follow-up opportunity forward a stage, never back. The household editor finds any contact by first name, email or company with its search box, and an unlinked primary adult is offered the household's own Seedly contact while it is still in Seedly, so Add as a contact never makes a second contact for the same person, while a partner on the family phone or email or an adult child with a parent's name gets a contact of their own; a contact deleted in Seedly is never linked or tagged again, its adult gets Add as a contact, its household still saves, and no registration is recorded on it. 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. Bedroll has no child check-in and refuses children's exact ages, birthdays, names lists (including lists after youth words and after a short place, such as Kids on the bus: Leo, Ava), allergy and custody notes and health details. Giving is only what the office typed in, and trip payments are never counted as giving. Access codes, Wi-Fi and portal logins, card, bank and routing numbers and Social Security numbers are refused in recorded text, while text such as Bus 2 leaves at 7:30 AM, Medical release received and John 3:16 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, and the Event registration form asks no medical, allergy or diet question. 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.