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 employer account relationship. It holds the company label, the contact person label, the account stage and the date it was entered, the recorded service labels, twelve monthly visit counts for the trailing twelve months, an agreement reference amount the clinic keeps for itself, the check-in interval in days, the last check-in date and an editable checklist. Follow-up calls, review requests and community partners are workspace records behind one shared revision guard, because a person who gets a courtesy call is not a commercial relationship with a company.

This is a business development and follow-up workspace, not a medical record. It is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system, and it is not a patient queue, wait time display, triage tool or check-in kiosk. It never records why anybody visited: there is no field for a visit reason, a symptom, an injury, a diagnosis, a test or screening result including a drug screen or physical outcome, a work status or restriction, a medication, a dose, a vital sign, a workers' compensation claim number, an insurance member or policy number, a government identifier or a date of birth. Employer accounts hold company-level commercial information only, the monthly activity strip is a count somebody typed, and call categories and review states are labels only. The shared model refuses text that looks like a dose, a blood pressure reading, an ICD-10 style code, a claim or insurance identifier, clinical vocabulary or a screening result in every field, on the server as well as in the browser, and a person's or a company's name is exempt from the two word rules alone. Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the clinic's own clinical system, and the kit gives no medical advice. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations. There is no clinical system integration, no workers' compensation or insurance processing, no billing or invoicing, no scheduling engine, no automated messaging, no review platform integration and no payments. Recording a review request does not ask anybody for a review, recording a call does not dial anybody, and the recorded agreement reference is a number the clinic keeps for itself.

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.