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.

Each host school keeps its relationship on its own Seedly company: main contact, room, dismissal bell, hosting days and paperwork as recorded. Each school's term is one contact-linked opportunity holding up to 16 classes (weekday, times, dates, grades, minimum and maximum, instructor, room, fee as recorded, status), up to 400 registrations (a child's first name and grade, the grown-up and their contact, status and the day it was recorded), no-class days, the proposal, flyer and confirmation dates and an editable checklist. The provider's time zone, terms and instructors sit in a small record in account settings, kept at or under 32 KiB.

Termtote records what the office typed. Children are minors, so a child is only ever a first name and a grade, and the shared GoSeedly school guard refuses common phrasings of birth dates and ages, grades and school records, allergies, medication and other health details, learning support, behavior, custody, immigration, lunch, income and foster details, pickup permissions and emergency contacts, background check results, codes, passwords and logins, and card, bank and ID numbers in recorded text and in the native form drafts, as a guard against accidental entry, not a guarantee; the README lists the phrasings it leaves open. Termtote keeps no check-in, sign-out, attendance, pickup authorization or ratio records; a clearance is a status and dates, never a result; fees are recorded one per class and never billed or totalled; nothing is sent. It never says a class, an instructor or a school is safe, cleared, certified, compliant or insured. Four alerts appear in red, counted from each class's first and last session: a class below its minimum after registration closed, no instructor 7 days out, a clearance that expires before the class ends and class dates not confirmed 21 days out. Workflow drafts run when a school term moves into their stage in Seedly, not when one is added at a later stage. Long setup jobs run in steps that stay well inside the database's read limit, and school terms are read page by page, so large accounts keep working.

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.