Starter removal, updates, and rollback
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.
What the workspace records
One contact-linked opportunity is one client or enquirer relationship. It holds the client label of a first name and last initial, the age band label, the service line as the practice’s own label, the stage with the date it was reached, the date the enquiry arrived and the date it was first answered, the contact attempts and last contact, the preferred and assigned clinician, the recurring slot day and time, the cadence label, the session length in minutes, whether a next appointment is recorded and its date, the referral source label, a fee arrangement label with no amount required, availability rows of a day and a time window, and an editable checklist. The clinicians with their own recorded weekly targets, their recurring openings, the referral sources, the recorded response days and the recorded quiet days live in one account store behind a single revision guard.
Weekly client hours are the sum of recorded session lengths over a clinician’s active clients, counted once a week for a weekly client, as one half for a fortnightly client and as one quarter for a monthly client, held in quarter-minutes so the three cadences total exactly. An opening’s fits are a plain availability comparison: the waitlist stage, the same day and the same time window, sorted oldest wait first and capped at three. Nothing is weighted, scored or decided for you, there is no clinical or suitability judgement, and offering an opening is still a conversation somebody has. This is the most careful kit in the collection and it records less than any other: no presenting concern, reason for seeking counseling, symptom, diagnosis, risk or safety information, session note, treatment goal, progress, medication, substance use, relationship or family detail, trauma history, school or employer detail beyond a referral source’s name, insurance or authorization number, government identifier or date of birth, and it holds no monetary field at all. A server-enforced guard refuses free text that looks like any of those in every field and every non-name label, which is help against accidental entry rather than a guarantee. There is no scheduling engine or calendar sync, no insurance, superbills or billing, no automated reminder or message of any kind, no client portal, no payments, no telehealth, and no crisis or emergency service: the enquiry form says so and carries a crisis line. None of the three public forms has a message box. A submission lands as a native Seedly form record, so it never passes through the kit’s guard, and an open box on a counseling form would be the one place a reason for seeking support could be typed and stored: every question other than a name, an email address and a phone number is a choice from a fixed list or a star rating, no form has a textarea and no form has a file field, and each form says “This form has no message box on purpose.” The kit gives no clinical or mental health 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.