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 job record is a native contact-linked opportunity with a namespaced loss type, property address label, loss date, carrier label, claim number reference, adjuster label, lead technician label, notes, an optional job amount, a fixed five-key documentation checklist of dates, the affected areas with their material label, dry standard percent and ordered readings, and the equipment lines with their quantity, placed date and pulled date. Two jobs at the same address stay independent, and other custom fields are preserved.

Every reading is a percentage and a date somebody typed in after reading their own instrument. There is no moisture meter, sensor, data logger or remote monitoring integration, and nothing in the kit measures a building. A dry standard is the number the assessor recorded; the kit supplies none, validates none and recommends none, and makes no IICRC, certification or compliance claim. The ramp is the ratio of two recorded numbers, not a drying calculation, psychrometrics, dehumidifier sizing or engineering advice. An area at exactly its standard is dry and an area with no readings is reported as not measured rather than counted as dry. Reading overdue means an area above its standard that has not been read for more than two days, and nothing else. The documentation checklist is five dates; the kit submits, transmits and files nothing, and there is no carrier, claim system, adjusting platform or estimating platform integration. Equipment lines are labels, quantities and dates, with no inventory, asset register or rental billing. Job amounts are recorded references, separate from native opportunity value, invoices, supplements and payments. Empty values read as words, never a dash.

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.