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 package holds the client, the target role, the package kind and status, the start date, the coaching sessions included, the recorded price and payment, every draft with its label, kind, writer, stage, rounds included and used, due, sent and final dates, every coaching session with its focus, mode, date, window and coach, every interview the client shared with its employer, role, round, format, date and the client's report, and an editable checklist.

Nextrung records what the office sold, wrote, booked and was told. It makes no promise of interviews, offers, a job, a promotion or pay, says nothing about how an interview went or will go, and does not score documents or run applicant tracking checks. It does not write, store or send documents, search for jobs, contact employers, book sessions online, bill, take payments or send messages. Salary history tied to an employer, health and disability details, background-check results, LinkedIn, job board and email logins, Social Security numbers, dates of birth, other ID numbers, door codes, meeting IDs and payment card numbers are refused in recorded text and in the native form drafts.

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.