Skip to content
View packages

GoSeedly Dental Practice Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original Clearday helpers are required for connected record creation, edits, the recorded desk windows and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the clinical guard before anything is written, and check revisions before saving. Deploy them from your authoritative backend source. Pipelines and workflow drafts are optional. Upgrading from version 0.1.0 keeps every identifier you already have installed: the installer restores the earlier release and writes this one in a single step, and a 0.1.0 patient record is read and shown with the new defaults while every field it already held is preserved untouched and named on the record rather than displayed. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Patient relationships, Hygiene recall, Unscheduled treatment, Family booking. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

Explore eighteen fictional patients in eight households. Eleven are due or past due for hygiene, five of them past due, and three households have two or more members due. Nine unscheduled plans cover all four decision states, three past the recorded follow-up window, and four patients qualify for reactivation. Sample edits stay in page memory and reset on navigation or reload. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

MORE OF THE WORKING DAY

From the first inquiry
to the final handoff.

Editable native forms and document templates give your team a practical starting point.

01 / INTAKE & FOLLOW-UP

Three ready-to-edit forms.

  • New patient registration
  • Appointment request
  • Visit feedback

Choose forms individually in Setup & resources, then customize and publish them in the native form builder.

02 / WORKING DOCUMENTS

Three reusable templates.

  • Hygiene recall call sheet
  • Treatment follow-up call sheet
  • New patient welcome checklist

Open each template in Documents and complete it for the actual job or visit.

03 / THE NEXT STEP

Checklists alongside the work.

Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.

Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.

PLEASE READ

A front-desk workspace, not a medical record.

  • This kit is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system.
  • It is built for relationship work: recalls, reminders due, follow-up, intake progress and front-desk tasks. Clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information belong in your clinical system, not here.
  • You install the kit on your own Seedly CRM. DevLaunch does not host, receive or process your patient data. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations, including any agreements with its hosting and software providers.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-dental-practice/config.ts to set practice name, descriptor and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

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.

What the workspace records

One native contact-linked opportunity is one patient relationship, grouped into a household by a label your office types. The namespaced record holds the patient label, an age band label, the household label, the preferred contact window, the last hygiene visit month, the recall interval in months, the recall state, contact attempts, the last contact date, the last visit month, a non-clinical staff note, unscheduled plans as child rows with stable IDs, and an editable front desk checklist. Other custom fields are preserved, including every field written by version 0.1.0 of this kit.

Clearday is a front-desk and treatment-coordinator workspace. It is not a dental record, an EHR or a practice management system, and it makes no HIPAA claim. It never stores procedure names or codes, tooth numbers or surfaces, diagnoses, clinical findings, images, medications, medical or dental history, insurance member or policy numbers, remaining benefits, government identifiers or dates of birth; an age band label is the most it records about age. The shared model refuses text that looks like any of those in every field and in the plan label, on the server as well as in the browser, and names the rule it matched; the plan labels, amounts, dates, scheduling notes and phone extensions a front desk really types are accepted. Treat that as help against accidental entry, not a guarantee. A plan amount is a reference number your office typed: nothing is quoted, billed, financed or collected, and a total is a sum of those numbers rather than revenue or a forecast. Recording a recall or a booking does not contact anyone, reserve a chair, hold a time or create a calendar event. The follow-up and reactivation windows are office preferences the practice records for itself, not clinical intervals.

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.