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, a companion or family contact label, the preferred contact window, the annual check recall type, month, state, attempts and last contact date, device trials with their product label, inventory identifier, start date, length in days, follow-up appointment days and states, decision and decision date, recorded reference amount and contact attempts, retail supply reminders, recorded warranty and loss and damage end dates, and an editable front desk checklist.

This is a front desk and trial 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 practice HIPAA compliant. Do not use it to store protected health information. It never stores hearing test results, audiograms, thresholds or decibel values, word recognition percentages, degree or type of hearing loss, ear side, tinnitus or other conditions, device programming settings, medications, medical history, insurance member or policy numbers, benefit amounts, government identifiers or dates of birth. Visit and recall types are category labels only, and a product label is the office’s own plain label rather than a device specification. The shared model refuses free text that reads like one of those in every field, on the server as well as in the browser, and names the rule it matched; ordinary front desk text such as "left a message", "right away", "Trial ends 10/31" and "As discussed, call Friday" is accepted. Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the practice’s own system, and the kit gives no medical or hearing advice. The practice is responsible for its own compliance and for whatever it chooses to record in its CRM. There is no practice management integration, no manufacturer fitting-software integration, no clinical or device record, no insurance or benefits processing, no device ordering or repair tracking, no scheduling engine, no automated reminders or patient messaging, no patient portal, no payments or financing and no revenue 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.