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.

A job is a native contact-linked opportunity with a namespaced job type, site address label, material type, product and supplier labels, crew label, recorded install week and day, the recorded job stage, job notes, an immutable supported currency, rooms with their measurements and material orders with their dates and received flag. The recorded quote reference stays separate from native opportunity value. Other custom fields are preserved.

Every number is something somebody measured or typed, or arithmetic on it. A room’s ordered quantity equals its recorded square footage plus the recorded waste percent of it, rounded up, and is nothing at all when either input is unrecorded. The job’s measured and ordered totals equal the sums across the rooms that are not archived. The editor computes all three and the server re-checks them, so a sheet that does not add up cannot be stored. An archived room keeps its measurements and stops counting. The quote reference is deliberately allowed to disagree with every measured figure, and the recorded order quantities are deliberately not forced to add up to the ordered total, because contractors order extra and reorder damaged boxes. The recorded job stage is evidence based: measured needs a measured room, ordered needs an order row, received needs a received order, installed needs a recorded install week. A recorded install week must start on a Monday, an install day must fall inside it, and a crew label needs a week. There is no supplier catalog, product database, SKU lookup, pricing feed or ordering integration, no inventory, cut list or remnant tracking, no takeoff from plans, and no delivery tracking or carrier feed. A late order is a comparison of a date the supplier gave with today. Nothing is invoiced, deposited, collected or ordered, nothing messages a client or a supplier, and crew labels reserve nobody and create no calendar entry. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the kit adds no stage model and no stage mutation, so recording that material arrived never moves a card.

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.