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 follows one child from inquiry to a start date: the child’s first name and age band (Not yet born, Infant, Toddler, Twos, Preschool, Pre-K or School age), classroom, status, waitlist position and date added, desired start month, tour date and follow-up state, schedule label, five paperwork flags that record only that a form was received, recorded transitions and an editable checklist. Classrooms (capacity, ratio limit and recorded staff count) and the center’s time zone, which sets today for days waiting and upcoming openings, are a separate per-workspace record. Other custom fields are preserved.

What changed in 0.2.0, a free update for 0.1.0 owners: a child is a first name and an age band instead of a birth month. A birth month 0.1.0 stored stays read-only until someone clicks Convert to age band, which names the band first, and the birth month is gone afterwards; nothing converts on its own. A guard in the browser, on the server and on every name and free-text field of the three form drafts refuses birth dates, ages, health, allergy, immunization and medication details, development and behavior notes, custody and pickup arrangements, a family’s immigration, income, benefits, housing, foster care or child welfare status, door codes, logins, and card, bank and ID numbers, as a guard against accidental entry rather than a guarantee. Naps, potty training, cubbies, diapers and wipes and classroom names pass. The over-ratio flag is gone: the board shows counts beside one another. Setup names any form or document 0.1.0 added and says how to replace it, and never edits one you own. Seats filled, children per staff and days waiting are derived from values your center records. Sprout makes no licensing, ratio, safety or regulatory determination, and does not provide attendance or check-in, billing or subsidy processing, parent messaging or daily reports, health record storage, or staff scheduling.

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.