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 school year's staffing chart holds the school's own dates and up to 200 positions, each with its division, department, role, load, the person holding it, their intent to return and the opening's status and dates. Each candidate is one contact-linked opportunity for one opening, holding the name as your office writes it, the source, the applied and finalist dates, a status with a closed reason, the offer with its reply-by date and your school's own figure as recorded, the contract sent and signed and the first day, plus every interview with the panel's recommendation, references as recorded, clearances as a status and dates, credentials as a label, status and expiry, and an editable onboarding checklist.

Doorplate records what the hiring office typed and decides nothing. It has no field for a candidate's age or date of birth, race, religion (there is no statement-of-faith field or score), national origin, citizenship or visa, disability or health, pregnancy, marital or family status, sexual orientation or gender identity or veteran status, or for salary history, Social Security, driver licence and teaching licence numbers, background check, fingerprint and drug test results, criminal history, student details, door codes, passwords and card numbers. A guard refuses common phrasings of them in notes and in name fields (the candidate's name, references, the person holding a position, and "Your name" and "Candidate's name" on the forms), as a guard against accidental entry, not a guarantee; the README lists the phrasings it leaves open. Each refusal names the field and says how to rewrite: describe what the candidate did and showed. Offer figures are your school's own and are never compared or recommended, the offer letter template says your school writes its own terms, and nothing in the kit says hiring is compliant or a candidate is cleared, verified or eligible. Form answers are capped at 250 characters, names at 80, and phone answers take a phone number only. When a later version's guard refuses text saved before, the record still shows and saves, and Doorplate 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.