Make the workspace
feel like your team.
Edit apps/web/components/devlaunch-funeral-home/config.ts to set business name, descriptor and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.
Starter removal, updates, and rollback
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.
What the workspace records
One contact-linked record is a family case or a pre-need inquiry. A family case holds the person as a first name and last initial, the service type, where the first call came from, the funeral director, the first call and arrangement conference dates and times, the obituary's status, paper, deadline, publish date and word count, the statement total as recorded, an office note, services with their room or place and status, aftercare calls with due and done dates, vendors with their phone and status, family contacts with their role and an editable nine-step checklist. A pre-need inquiry holds the inquiry, the information sent, the planning meeting and the date the family's wishes were recorded.
Lindenrow records what your office recorded. It is not a price list, a statement of goods and services, a contract, a death registration system or a pre-need trust record, and it makes no regulatory, pricing-disclosure, legal, licensing or pre-need trust claim. It takes no payments, sends no messages, books no vendor and sends nothing to a paper. Cases, services, calls, vendors and money keep their own units and are never added together. A cause of death or medical details, Social Security numbers in the usual phrasings, veterans' service and VA file numbers, card, bank and policy numbers, dates of birth, exact ages from 10 up, access codes, passes and logins are refused in recorded text, while funeral home text such as Hymn 23, Plot 14, Section B, Pacemaker removed, Autopsy pending, release Thursday and Memorials to the American Cancer Society is kept. The guard is a protection against accidental entry, not a guarantee, so keep sensitive details out of the workspace. The three public form drafts hold only names, email, phone and fixed choices, with no message box; name answers are capped at 80 characters and phone answers take a phone number only.
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.