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 booking is an opportunity in Facility requests or Outside rentals & weddings, linked to the requester's contact, holding the title, kind, rooms, date, start and end as clock times, setup and teardown, a weekly repeat with skipped weeks, the status and the dates the request came in and was decided, the people expected, and for outside bookings the fee and deposit as recorded, whether an agreement is needed and its dates, the certificate of insurance as yes or no, the tour, walkthrough and rehearsal, plus setup and AV tickets. Rooms and maintenance blockouts live in their own account record. 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. 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.

Lintel records what the office decided. It creates each booking's opportunity at the stage that matches its status and never moves it afterward; the office drags it in Seedly. A stage draft runs only when a booking is dragged into its stage on the Seedly board, not when Lintel records a booking at a later stage, and the Requests view marks a board that is behind. The Setup sheet task is due the day before the booking's next date, one task per drag even for a weekly booking. Lintel reads every open booking and every open household with its own paged queries, past Seedly's 1,000-opportunity board limit, and no read takes every household at once, so a church with years of attendance and giving stays inside the database's read limits. Today, the masthead, setup and the day each card, request and prayer request arrived follow the church time zone, and the week rolls over at the church's midnight, daylight saving nights included. Clock times stay wall-clock times, so a daylight saving change moves nothing, and conflicts count setup and teardown. Lintel never approves a booking by itself, never compares capacity with a headcount, says nothing about occupancy or safety rules, keeps no door, alarm or keypad code and no certificate or policy number, and processes no fee or deposit. The facility use agreement is a bracketed template your church writes with its own advisers, not legal advice. 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. Lintel has no child check-in and refuses children's exact ages, birthdays, names lists, allergy and custody notes and health details. Giving is only what the office typed in. 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 Custodian unlocks the side door at 7:30, Room 204 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, plus one guarded event name line on the room request. 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.