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 client record holds a first name and last initial, status, program label, the follow-up cadence the dietitian set, a coverage label (self-pay or insurance on file), inquiry and hold dates, preferred days and times, the referral source and thank-you date, each package with its sessions included, recorded price and bought and expiry dates, each session with its date, time, minutes, kind, format, status and the package it draws from, a non-clinical staff note and an editable front desk checklist.

Thymeline records what the front desk agreed and saw. Only attended sessions use a package, the next follow-up is the last attended session plus the cadence the dietitian recorded, and it applies no cancellation or expiry policy. Sessions, minutes and money each keep their own unit. It gives no nutrition advice, never sets a cadence, does not check anyone's availability, bill insurers, take payments or send messages. In recorded text it refuses the obvious accidental entries: conditions, lab values, medications, supplements and doses, body weight and weight change, BMI and measurements, calorie and macro targets, eating-disorder, eating-pattern and pregnancy details, dates of birth and exact ages, insurance and Medicare numbers, access codes, logins, payment card numbers and Social Security numbers, while front-desk text such as 6-session package, Session 4 of 6, Every 2 weeks and Insurance on file is kept. It is a guard against accidental entry, not a guarantee. The forms have no message box: name answers refuse codes, numbers, ages and measurements and are capped at 80 characters, and phone answers take a phone number only.

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.