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 student enrollment is a native contact-linked opportunity with namespaced student, grade, school, guardian and tutor labels, up to eight recorded subject labels, a reference package count and price, enrollment start and next review dates, reference notes, session rows and progress review rows. Two enrollments for one student, or two children in one family, stay independent records; unrelated custom fields are preserved.

Every value on screen is a label, a date, a duration or a short note typed by a member of staff. A session row records a slot the center agreed: it reserves no room, no tutor and no time, creates no native Calendar appointment, detects no conflict and repeats nothing, and an empty cell means only that nobody recorded a session there. A progress review is a staff-written summary with agreed next steps, not a score, a mark, a rubric or a test result, and the grade label is the grade the student is in. Recorded package counts and prices are reference figures: nothing is charged, invoiced, collected, refunded, prorated or recognized as revenue, and no balance is tracked. Subject chip colour comes from an exact match on the recorded label, so a subject your center invents keeps a neutral gray chip instead of borrowing another subject’s colour, and every chip prints its label as text. This is not a learning management system, a curriculum, an assessment or grading system, or a student information system, and it makes no FERPA, COPPA or other compliance claim.

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.