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 or one referring dental office. A patient record holds the patient label, an age band label, the responsible party label, the referring office label, the funnel stage with the date it was entered, the recorded consult date, the decision state, the follow-up attempts and last follow-up date, the treatment type label, the contract amount and down payment in minor units, the start month, the estimated month count, the observation recall month and its attempts, the next milestone label and an editable front desk checklist.

This is a treatment-coordinator and front-desk relationship record, not a medical or dental 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 practice HIPAA compliant. Do not use it to store protected health information. It never stores diagnoses, malocclusion or Angle classes, tooth numbers, clinical findings, imaging, appliance details, wire sizes, medications, doses, medical or dental history, insurance member or policy numbers, government identifiers or dates of birth; age is an age band label at most. Treatment type and next milestone are the office’s own category labels, and contract amount and down payment are recorded reference numbers rather than a billing system, a payment plan or a financing product. The shared model refuses text that looks like one of those values in every field, on the server as well as in the browser; treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the practice’s own clinical system, and the kit gives no dental or medical advice. The practice is responsible for its own compliance and for whatever it chooses to record in its CRM. There is no practice management or imaging integration, no treatment planning, no insurance, billing or financing processing, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments. Every amount shown is the total of amounts somebody recorded, and consult to start is reported as recorded counts rather than a forecast.

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.