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 applicant is one contact-linked opportunity holding the name as your office writes it, an age band, the program and start date, a schedule preference, the source, the inquiry time, the application, agreement sent, agreement back and first day dates, a status with a closed reason, prior education as a closed level, a funding path and status as labels, an optional sponsoring partner and notes, plus every contact attempt, tour and info session and an editable enrollment checklist. An applicant under 18 is a first name only, and the guardian is the Seedly contact.

Toolroll records what the admissions office typed. It makes no accreditation, eligibility, licensing, placement, earnings or financial aid statement, never bills tuition, sends invoices or takes payments, and does not decide, rank or admit anyone. It holds no grades, transcripts or test scores, and keeps background checks and drug screens as a status and dates only. A guard against accidental entry refuses the common ways sensitive details get typed: dates of birth and ages, grades and test scores, health and medical details, criminal history, background check and drug test results, DOT medical card details, immigration status, income and financial aid records, along with door, gate and shop codes, passwords and logins, card, bank, Social Security, driver license, CDL, permit and other ID numbers, in recorded text and in the native form drafts. A FAFSA night on the calendar and “Do you accept FAFSA?” on the inquiry form still go through; a filed FAFSA or an aid amount does not. Form answers are capped at 250 characters, names at 80, and phone answers take a phone number only. It is a guard, not a guarantee. When a later version's guard refuses text saved before, the record still shows and saves, and Toolroll flags the text to rewrite.

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.