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 relationship. It holds the client label, the age band label, the service type labels, the intake step with the date it was reached, the family contact label with its relationship label and update due date, the agreed weekly hours, the referral source label, a non-clinical preference note, weekly shift rows carrying a day, a start and end time in 24-hour form, the caregiver assigned or nothing, the date the shift became open and the calls recorded against it, and an editable checklist. The caregiver roster, the relationship records and the recorded urgent window live in one account store behind a single revision guard, and a row is archived rather than dropped.

The fitting-caregiver column is a plain comparison of the day of the week and the time window, capped at three and sorted oldest open first. Nothing is weighted, scored or decided for you, it does not look at hours already assigned, and putting somebody on a shift is still a call a scheduler makes. This kit is for non-medical companion and personal-assistance coordination. It records no diagnosis, condition, cognitive status, medication or medication reminder, care plan, assessment score, incident or fall report, vitals, insurance, Medicaid or Medicare number, government identifier, date of birth, or door, lockbox, alarm or gate code, and it holds no monetary field at all. An age band label is the only age information it holds, and a caregiver compliance item is a plain label and an expiry 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 electronic visit verification, time clock, payroll or billing, no Medicaid, Medicare or long-term-care insurance processing, no background check or credential verification, no automated reminder or message of any kind, no family login, no payments, and the kit gives no medical or care 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.