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 record is one patient relationship. It holds the patient label, an age band label, the referrer it names, a plain program label the clinic types, the authorized, attended and booked visit counts, the authorization end date, the last attended visit date, contact attempts and the last contact date, the drop-off, discharge, review request and wellness interest states, the preferred contact window and an editable front desk checklist. Referrers are their own relationship records, kept with the clinic's two recorded numbers under a server-owned revision.

This is a front-desk and referral relationship record, not a medical record. It is not a HIPAA compliance product, it is not an EHR, EMR or practice management system, and installing it does not make a clinic HIPAA compliant. Do not use it to store protected health information. It never stores diagnoses, injuries, body regions, surgeries, pain scores, range-of-motion or strength measurements, goals, exercises or home programs, clinical notes, medications, referral diagnoses or codes, insurance member, policy or authorization numbers, government identifiers or dates of birth. The authorized visit count and the authorization end date are recorded numbers only, the age band is a label, and the program label is a plain label the clinic types. The shared model refuses text that looks clinical in every field, on the server as well as in the browser, while accepting ordinary front-desk phrases such as "Call back after 4" and "7 of 12 used". Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the clinic's own system, and the kit gives no medical or rehabilitation advice. There is no EHR or EMR integration, no practice management integration, no clinical documentation or outcome measures, no insurance verification, authorization submission, claims or billing, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments. A booked count is a number the front desk typed: it reserves no room, holds no time and creates no calendar entry.

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.