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 contact-linked community holds the association kind and management status, the community manager and board contact, doors, the recorded dues per door with their period and the recorded management fee per month, every home by lot or unit with its address, owner and occupancy, every violation with its category, the manager's few words, the step as recorded, observed, step, follow-up and hearing dates and the fine as recorded, every architectural request with its project, kind, status, submitted and review-by dates and the board's decision as recorded, every board, annual, committee and special meeting with its date, time, location, agenda and minutes status, every work order with its area, vendor, status, dates and quote as recorded, and an editable checklist.

Curbline records communities, homes, violation steps, architectural requests, meetings and work orders as your office typed them. It gives no legal advice, does not decide whether a violation exists, and never says a notice, fine, hearing, decision, agenda or minutes is enforceable, valid or compliant with any statute or governing document; "approved" and "denied" are only the board's decision as recorded. It sends no notices, posts nothing, charges or collects no dues or fines, runs no votes and messages no one. Gate, pool, clubhouse, amenity and fob codes, passes, portal logins and passwords, dues autopay bank details, card numbers and Social Security numbers are refused in recorded text and in the native form drafts, while lot and unit numbers, addresses, dates and dues amounts are accepted.

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.