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 contact-linked opportunity is one client and family relationship. It holds the client first name label, the age band label, the service line label, the stage with the date it was reached, the waiting-since date, the contact attempts and last contact, the recurring slot day, time and clinician first name, the authorized visit count, the visits used and the end date, the caregiver follow-up due date, the school or referrer label, caregiver rows with a relationship label and a preferred-contact flag, availability rows of a day and a time window, and an editable checklist. The open recurring slots, the relationship records and the recorded authorization window live in one account store behind a single revision guard.

Matching is a plain availability comparison: the same day, the same time window and compatible service lines, sorted oldest wait first. Nothing is weighted, scored or decided for you, and offering a slot is still a call somebody makes. The kit records no date of birth, diagnosis, condition, disability category, test score, therapy goal, session or progress note, education plan, home program, medication, medical history, insurance member, policy or authorization number, school identifier or government identifier, and it holds no monetary field at all. An age band label is the only age information it holds, and an authorized visit count with an end date is a recorded number and a date. A server-enforced guard refuses free text that looks like any of those in every field, which is help against accidental entry rather than a guarantee. There is no scheduling engine or calendar sync, no insurance verification, authorization submission or billing, no automated reminder or message of any kind, no family login, no payments, and the kit gives no therapy or medical advice.

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.