On this page
Before you startStep-by-step: connecting Claude to a clinicWhat to tell them not to expect, in this phaseA teaching point worth emphasizing: permissions carry overCommon trainee mistakes to watch forFor Training
This is written for whoever will eventually walk a clinic through connecting Claude, once this ships. It assumes the trainee already knows how to log in to Dentolize normally.
Before you start
Confirm with engineering/product that this feature is actually live in the environment you're training on — as of this PR it is not deployed anywhere, including sandboxes. Don't demo a flow that will 404.
Step-by-step: connecting Claude to a clinic
- In Claude, the doctor adds the Dentolize connector and clicks
Connect. Claude opens a browser window/tab pointed at Dentolize.
- They land on a familiar Dentolize login screen — either the regular
email/password one, or the username + clinic-name one, whichever they normally use. Nothing about this screen is different from their everyday login. If their clinic has 2FA enabled, they'll be asked for that too, same as always.
- If their login is associated with more than one clinic, they'll be
asked which one to connect — a connection is always to exactly one clinic. If they need Claude to see a second clinic later, that's a second, separate "Connect."
- They'll see a plain-language list of what Claude is asking to read —
in this phase, that will read something like "Inventory, stock levels and supplier spending." They should actually read this list; it names exactly what's being granted, nothing more.
- They click Connect to approve, or Cancel to back out. Either way, they
land back in Claude.
- They can now just ask. No special syntax — plain questions like "what's
running low on stock?" or "how much did we spend with suppliers last quarter?" work because Claude decides which tool to call based on the question.
What to tell them not to expect, in this phase
- Don't ask about patients, appointments, billing, or clinical notes — Claude
has no access to any of that yet, and will say so rather than guess.
- Don't expect Claude to change anything — add stock, edit an order, anything.
It cannot write under any circumstance in this phase.
- Don't expect a screen inside Dentolize to manage the connection yet — if
they want to disconnect, that currently requires contacting support (see For Support), not a self-service toggle.
A teaching point worth emphasizing: permissions carry over
If a staff member's role in Dentolize already hides stock values from them (a common setup for front-desk roles), ask Claude the same question and it will say so plainly — something like "stock values are not available to you here either" — rather than just omitting the number silently. This is worth walking through live during training so staff aren't confused the first time they see it: it's not a bug, it's the connection correctly respecting the same permission their clinic already set up.
Common trainee mistakes to watch for
- Opening the Connect link in a second tab while a first attempt is still
in progress. Each attempt should be completed start-to-finish in the same tab before starting another.
- Bookmarking or saving the login link shown during the connect flow, to
reuse "next time." It's single-use and time-limited; walking them through clicking Connect fresh each time avoids confusion later.