How do I share credentials with a dental client securely?
On this page
- Key facts
- Why is "just email them the passwords" the wrong answer?
- What does owner-controlled access look like?
- Which credentials should be in the vault?
- What about the one-time handoff at go-live or offboarding?
- Which free tools help with this?
- How FloorStack helps
- Free tools for this step
- Frequently asked questions
- Sources
Don't "send" them at all. Put every credential in a vault the practice owns, give your technicians named accounts with MFA, and keep at least 2 emergency admin accounts the practice controls (Microsoft Learn). In 2026, the owner should be able to revoke you in one step.
Key facts
| Item | What the source says | Source |
|---|---|---|
| Emergency admin accounts | At least two, cloud-only, not tied to an individual, phishing-resistant auth, checked at least every 90 days | Microsoft Learn |
| Password managers | Verifiers "SHALL allow the use of password managers and autofill" | NIST SP 800-63B-4 |
| Forced periodic changes | Verifiers "SHALL NOT require subscribers to change passwords periodically," but must force a change on evidence of compromise | NIST SP 800-63B-4 |
| CISA advice | Use a password manager to create long, random, unique passwords | CISA |
| MSP accounts | Enforce MFA on MSP accounts and disable accounts no longer in use | CISA AA22-131A |
| Microsoft 365 partner access | GDAP gives partners "granular and time-bound" least-privileged access the customer must grant | Microsoft Learn |
| Withholding PHI access | A business associate may not block a covered entity's access to PHI in a payment dispute | HHS FAQ 2074 |
Why is "just email them the passwords" the wrong answer?
Because the problem isn't delivery. It's control. A list emailed once is stale the next time you rotate a password, sits in two mailboxes forever and gives the practice no idea who used what. The question a dental owner actually asks is "can I get in without you, and can I see what you did?" Design for that.
I run a dental MSP, and my view is simple: the practice owns the keys; we borrow them. That stance also matches HHS. HHS says a business associate may not block a covered entity's access to PHI, even to resolve a payment dispute (HHS FAQ 2074). Credentials are how that access happens.
What does owner-controlled access look like?
Five layers, from the most important down.
1. A vault the practice owns
The vault account, billing and top-level admin belong to the practice. Your firm is a guest with scoped access. NIST's digital identity guidelines require verifiers to allow password managers (NIST SP 800-63B-4), and CISA recommends them for long, random, unique passwords (CISA). Organize entries by device and room, so "firewall," "imaging server" and "Op 2 workstation" each have their own record.
2. Named accounts, not shared ones
Each technician gets their own login to the firewall, server and Microsoft 365, with MFA. CISA and partner agencies tell MSP customers to enforce MFA on MSP accounts that access the customer environment (CISA AA22-131A). Named accounts are also how you satisfy HIPAA's unique user identification requirement (45 CFR 164.312).
3. Emergency access the practice holds
For Microsoft 365, Microsoft recommends two or more emergency access accounts, cloud-only, not tied to any individual, protected with phishing-resistant authentication, stored in separate secure locations and validated at least every 90 days (Microsoft Learn). The doctor or office manager should control at least one. Do the same for the firewall and domain registrar: one owner-held admin that you don't use day to day.
4. Least-privilege partner access
Use the platform's delegated model where it exists. Microsoft's GDAP lets partners configure "granular and time-bound" access, and customers must explicitly grant it (Microsoft Learn). The customer can remove partner admin roles at any time from Partner relationships (Microsoft Learn). Tell the practice that, in writing.
5. Logged reveals and rotation on change
Every time someone views a password, it should be logged. Rotate when people leave or on evidence of compromise, not on a calendar: NIST says verifiers shall not require periodic password changes but shall force a change if there's evidence of compromise (NIST SP 800-63B-4). HIPAA's workforce security standard includes termination procedures for ending access when someone leaves, an addressable specification (45 CFR 164.308).
Which credentials should be in the vault?
| System | Owner account | MSP access |
|---|---|---|
| Microsoft 365 or Google Workspace | 2 emergency admins, practice-held | Delegated, time-bound |
| Domain registrar and DNS | Practice is registrant (ICANN) | Named user or none |
| Firewall and switches | Owner admin, unused day to day | Named admin with MFA |
| PMS and imaging server | Practice admin | Named support account |
| Backup console | Practice admin | Named operator |
| Camera NVR or cloud | Practice admin | Named, limited |
| Phone system portal | Practice admin | Named, limited |
| Wi-Fi controller | Practice admin | Named admin |
Defaults go first: CISA lists changing default passwords among baseline steps (CISA). For a full audit, see who owns dental office passwords.
What about the one-time handoff at go-live or offboarding?
Hand over vault ownership, not a document. If you must deliver a static export, encrypt it, send the passphrase by a separate channel and delete your copy once the practice confirms. Then walk the owner through logging in to each critical system with their own account, while you're on the call. The steps for a full transition are in switching dental IT providers and taking over a client from another MSP.
Which free tools help with this?
The credential ownership checklist (free tool, coming soon) is planned to list every login, license and account the practice should own, with a "password hostage" letter template. FloorStack Studio (live, free plan) places every device on your floor plan and gives you a device schedule with rooms, ports and cable lengths (FloorStack FAQ).
How FloorStack helps
FloorStack is a dental build-out platform with a credential vault built for this model. Logins are stored with the device they open, encrypted, revealed only to the people the practice chooses, and every view is logged; the practice can grant, limit or revoke MSP and vendor access, including expiring vendor access (FloorStack). The vault and a signed BAA come with the Shared Stack plan (FloorStack). Start by mapping devices in Studio (live, free to start), then run the free Credential ownership checklist (coming soon), which includes a "password hostage" letter template for practices whose current provider won't cooperate. Visit the Own Your Dental Passwords hub.
Free tools for this step
- Credential ownership checklist: system-by-system audit plus letter template (free tool, coming soon).
- Studio: map devices so each credential has a home (live).
Frequently asked questions
Should the MSP or the practice own the password manager account?
The practice. Your firm should have scoped, revocable access inside it.
Do we still need to change passwords every 90 days?
Not for its own sake. NIST says verifiers shall not require periodic changes but must force a change on evidence of compromise (NIST SP 800-63B-4). Rotate when staff or vendors leave.
How do we give Microsoft 365 access without Global Admin?
Through GDAP, which gives partners granular, time-bound access that the customer grants (Microsoft Learn).
What if the client loses their emergency account?
Recover it through the platform's own process with the client present, then document a new one. Microsoft recommends validating emergency accounts at least every 90 days so this is caught early (Microsoft Learn).
Sources
- FloorStack: Frequently asked questions
- Microsoft Learn: Manage emergency access admin accounts
- Microsoft Learn: Granular delegated admin privileges (GDAP) introduction
- Microsoft Learn: Manage partner relationships
- NIST SP 800-63B-4: Authentication and Authenticator Management
- CISA: Use Strong Passwords
- CISA et al., Advisory AA22-131A: Protecting Against Cyber Threats to MSPs and their Customers
- CISA: #StopRansomware Guide
- HHS FAQ 2074: May a business associate block or terminate access to PHI?
- 45 CFR 164.308, Administrative safeguards (LII)
- 45 CFR 164.312, Technical safeguards (LII)
- ICANN: Registrants' Benefits and Responsibilities
- FloorStack home page
More in Own Your Dental Passwords
- Taking Over a Dental Client From Another MSP: Credential Handoff PlanA 2026 credential handoff plan for MSPs taking over a dental client: owner-led requests, domain, Microsoft 365, firewall, backups, BAAs and old-MSP offboarding.5 min read
- Dental IT Contract Clauses: Own Your Passwords and Data (2026)What a dental IT contract should say in 2026 about passwords, admin accounts, data return and offboarding, so your practice is never held hostage.6 min read
- BAA With Your Dental IT Company: What It Must CoverDoes your dental IT company need a BAA? Yes, if it can access ePHI. What a 2026 BAA must cover under 45 CFR 164.504 and 164.314, plus terms worth adding.5 min read
- Who Owns Your Dental Office Passwords and IT Accounts?Your practice owns its passwords, domain and admin accounts, not the IT company that set them up. See what HIPAA requires in 2026 and how to take inventory.6 min read
- Can Your IT Company Refuse to Give You Your Passwords?An IT company holding your patient data can't lock you out over a billing dispute, HHS says. What to do in 2026 if your dental IT provider withholds access.6 min read
- How to Switch Dental IT Providers Without Losing Access (2026)A 2026 step-by-step plan for switching dental IT providers: inventory, owner admin accounts first, credential handover, BAA data return, and a 30-day checklist.6 min read