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.

One client is a native contact-linked opportunity with a namespaced preferred therapist label, pressure preference, up to eight focus area labels, an intake flag with its recorded date, staff notes, a fixed six-key package object, appointment rows and follow-up rows. Two people in the same household stay independent records, because the package, the form and the pressure preference belong to a person. Other custom fields are preserved.

An appointment row is something the desk typed. It reserves no room, holds no therapist, checks no availability, creates no native Calendar event and sends no confirmation, and there is no online booking or scheduling engine. Sessions remaining is derived from the recorded total and used counts and never stored, so the pips and the tables cannot disagree with the record; sessions used is deliberately not reconciled against completed appointments, because a client can arrive with sessions already drawn down and the desk decides whether a late cancel consumes one. Two clients may record appointments that overlap in one room: the lane splits into stacked sub-rows and the overlap is marked "Double booked" rather than refused, because the kit reserves nothing. Staff notes are a plain note the desk keeps, never a chart, a SOAP note or a clinical opinion, and the kit holds no intake form content, health history, consent record, insurance field or medical claim. Package prices are recorded references, separate from native opportunity value, invoices and payments; nothing is charged and no session is redeemed automatically. Empty values read as words, never a dash, and counts are pluralized against their own value.

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.