For Training

Who needs this training

Anyone with clinic-owner-level access (or a role granted viewPlugins/managePlugins) who will evaluate or manage third-party integrations. This is not a receptionist/doctor/nurse workflow — treat it as an owner/IT-contact training module.

Step-by-step: installing a plugin

1. Navigate. Sidebar → Settings → Plugins. You'll land on the Browse tab.
2. Find it. Use search or the category filter. Click a card to open its full listing.
3. Read before you install. Scroll the detail page: description and changelog on the left; publisher contact info and the full permissions breakdown on the right. Point out the sensitivity groupings — Basic, Operational, Financial, Patient personal data — and that a plugin requesting the last tier shows a red warning banner. This is the moment to actually read what's being requested, not the install wizard (which repeats the same list — the wizard is a second chance to notice something, not the only chance).
4. Click Install. The wizard has three steps:

• Access — same permission list again, for confirmation.
• Data agreement — read the DPA summary, follow the link to the developer's actual privacy policy if you want more detail, then check the box. The Accept & install button won't activate until you do.
• Done — your API credentials are generated here. This is a copy-now moment: the token is shown exactly once and never again in full.

1. Go to plugin settings. You land on the four-tab configuration screen. If the plugin has its own settings (API keys, preferences), fill those in on the Settings tab first — most plugins won't function until this is done.

Step-by-step: connecting a webhook endpoint

Only relevant if the plugin's own instructions ask you to add one (most plugins with a hosted backend will tell their clinic customer to do this).

1. Connection tab → Add endpoint.
2. Paste the URL the plugin developer gave you (must start with https://).
3. Select which event types to send to it — only events this plugin was actually granted appear in the list.
4. Click Add endpoint. A signing secret appears once — give this to whoever manages the plugin's backend; they need it to verify incoming notifications are genuinely from Dentolize.
5. Use Send test to confirm the connection works before relying on it — check the Activity tab afterward for the delivery result.

Step-by-step: uninstalling

Danger tab → Uninstall plugin → type the plugin's slug exactly to confirm → optionally check "request data deletion" → confirm. Emphasize: this is immediate and there's no undo from the clinic side — reinstalling later starts a fresh consent flow and issues brand-new credentials.

Key concepts to land in training

• A plugin token and a webhook secret are two different things, and neither is ever shown twice — train people to actually copy them at the moment of creation, into wherever the plugin's backend config lives, not "I'll come back for it."
• Consent is all-or-nothing. There is no partial-approval option in this release. If a plugin requests something the clinic isn't comfortable with, the answer is "don't install it," not "install it and turn off the parts I don't like."
• The Activity tab is the plugin's health check. Teach owners to glance at it if a plugin "seems to have stopped working" before calling support — a string of Failed deliveries there usually points at the plugin developer's side, not Dentolize's.