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 system is a native contact-linked opportunity with a namespaced service address label, system type, construction, liner label, cap flag, preferred fall service month, technician label, an optional recorded service price, notes, and three child collections: inspections with a date, level 1, 2 or 3, technician label, condition label and findings note; sweeps with a date, technician label and creosote level label; and repair recommendations with a label, priority and status. Two systems at the same address stay independent, and other custom fields are preserved.

Nothing in this kit certifies a system. Inspection levels, condition labels and creosote level labels are what a person typed; there is no code text, standard, certification register, inspection form, certificate or compliance status anywhere. The preferred service month is a recorded customer preference and the season countdown is calendar arithmetic on it, run at UTC noon so a window never shifts across a daylight saving boundary: nothing books a visit, reserves a technician, creates a native Calendar appointment or optimizes a route. A repair recommendation is a label, a priority and a status with no date at all, so nothing holds stock, orders a liner or cap, prices a part or tracks a delivery. Recorded service prices are references, separate from native opportunity value, invoices and payments. Three rules are enforced on both the client and the server: a level 2 or level 3 inspection requires a recorded findings note, a recorded liner label requires a recorded construction, and a gas fireplace may record no creosote level, because gas appliances produce none. The cap flag is a strict boolean with two drawn states, and "No cap recorded" means nobody recorded a cap rather than that a cap was confirmed absent. Empty values read as words, never a dash, and counts are pluralized against their own value.

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.