Every room and every hour, on one calendar.

Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected bookings, the rooms record, the form inbox, households, the church lists, linked contacts and setup. They preserve native account permissions, unrelated custom fields and row history, keep bookings, rooms, households, people, hours and money apart, refuse door and alarm codes, certificate and policy numbers, children's ages and names lists, allergy and custody notes, health details, logins, card and bank numbers and Social Security numbers as a guard against accidental entry rather than a guarantee, refuse dates still ahead for things that already happened, and check revisions before saving. To update, run the previous release's remove and this release's install in your Seedly working tree with no deploy or build in between, then deploy the backend, then build and deploy the web app; if remove refuses a file you edited, keep a copy of your edits, put the file back exactly as the previous release's installer wrote it (from your own commit made right after installing it, or by installing that release on a fresh copy of the same Seedly version and copying the file from there), remove and install, then re-apply your edits. Since 0.1.1 every helper an earlier page calls keeps its arguments and answers, so a page still open on the previous release keeps working between the two deploys. Pipelines, drafts, forms and documents are optional.

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.

Six optional pipeline templates and 16 inactive workflow drafts. 36 fictional in-memory bookings.

Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.