Answer · Published Nov 18, 2026
Is Slack HIPAA Compliant? The BAA, the Plan and the Limits
For practice managers and owners whose staff already chat in Slack. You will leave knowing which plan carries the BAA, what Slack still forbids under it, what each plan costs a small team, and where patient conversations should live instead.
Not on the plans most practices use. Slack supports HIPAA only on its enterprise tier, marked on Enterprise+ alone, with a signed business associate agreement (Slack pricing, Nov 2026). Free, Pro and Business+ cannot hold patient information. Even with the BAA, Slack bars patient messaging and limits where PHI may appear.
Key takeaways
- Slack's compare table marks support for HIPAA compliance only on Enterprise+; Pro ($7.25) and Business+ ($15 per user per month, paid yearly) have none (Slack, Nov 17, 2026).
- Under the BAA, PHI may appear only in messages, files, file names and private channel or DM names, and Slack may not be your system of record (Slack Help Center).
- You must monitor use with Slack's data loss prevention or its Discovery APIs, and both are Enterprise+ features.
- Slack signs no BAA with Marketplace apps, and email into Slack is switched off in HIPAA organizations.
- If you already run Microsoft 365 or Google Workspace, Teams and Google Chat are on those vendors' BAA service lists (Microsoft; Google).
The short answer, from Slack's own pages
Slack can hold protected health information (PHI) only on its enterprise tier, after you sign Slack's BAA and agree to implement its guide for HIPAA entities. Slack's help center says "You must be using a Slack Enterprise plan" and "You must execute a Business Associate Agreement" (Slack Help Center, Nov 2026). On the pricing page, the row "Support for HIPAA compliance" is ticked for Enterprise+ and for no other plan; Slack's HIPAA resource page names Enterprise Grid (Slack), so ask sales to name the exact plan your BAA covers.
| Plan | List price (per user per month) | Support for HIPAA | What that means for patient data |
|---|---|---|---|
| Free | $0; 90 days of message history | No | No patient details |
| Pro | $7.25 paid yearly; $8.75 paid monthly | No | No patient details |
| Business+ | $15 paid yearly; $18 paid monthly | No | No patient details |
| Enterprise+ | Contact sales | Yes, with a BAA | PHI in messages and files only, under Slack's rules |
Source: Slack pricing and compare table, opened Nov 17, 2026. Promotional discounts for paying monthly are left out.
No BAA on any listed price: Slack per user per month, paid yearly
Gray: no HIPAA support. Dashed teal: HIPAA support with a BAA, no list price. Bars scaled to Business+.
What Slack still forbids under the BAA
Slack's BAA covers far less than "everything in Slack." Its help center lists the limits (Slack Help Center), and its resource page adds the tools you need (Slack HIPAA resource page):
- No messaging patients or their families.
- PHI only in messages, files, file names, and names of private channels or DMs. Not in canvases, lists, workflow forms, profile fields or public channel names.
- Channels where PHI may be shared should be private.
- You monitor use yourself, with Slack's data loss prevention or an outside DLP tool on Slack's Discovery APIs.
- Slack is not the designated record set and should not be the system of record.
- Slack has no BAA with any Marketplace app. You decide, app by app, whether you need one.
- Email into Slack does not work in HIPAA organizations.
- Slack lists other tools you will need: a DLP solution, an SSO solution and backup or archiving.
These sit on top of HIPAA's own rule that a cloud service storing PHI for you is a business associate, encrypted or not; using one without a BAA "is in violation of the HIPAA Rules" (HHS OCR cloud guidance).
Deciding where patient conversations live, writing the chat rule and training the team is part of our Practice Controls work. See what an operations consultant costs before you decide to do it in-house.
Book the free 20-minute Chaos AuditIf you go enterprise: the settings and tools
On the BAA tier, map each HIPAA technical safeguard in 45 CFR 164.312 to a Slack control before the first patient message.
| Safeguard | Slack control | Plans that have it |
|---|---|---|
| Person authentication | Two-factor authentication; SAML single sign-on | 2FA on all plans; SAML on Business+ and Enterprise+ |
| Automatic logoff | Session duration | All plans |
| Audit controls | Audit logs (in Slack, CSV or API); access logs | Audit logs Enterprise+ only; access logs Pro and up |
| Monitoring required by Slack | Native data loss prevention; Discovery API | Enterprise+ only |
| Access control | Private channels for any PHI; remove apps you do not need | All plans |
| Retention | Data retention policies | Paid plans; Free deletes after one year |
Slack also asks for a list of every Slack org or workspace where you plan to use PHI (Slack). Store the signed BAA and that list in your BAA tracker, and note that a business associate must report a breach within 60 days of discovering it (45 CFR 164.410).
Worked example: an eight-person office
Eight users on Business+ cost $1,440 a year at list price, and none of it buys a BAA. Worked example: a three-physician family practice with an office manager, two front-desk staff and two medical assistants.
| Plan | Inputs | Per year | Patient details allowed? |
|---|---|---|---|
| Pro | 8 x $7.25 x 12 | $696 | No |
| Business+ | 8 x $15 x 12 | $1,440 | No |
| Enterprise+ | Quote, plus a DLP tool, SSO and archiving | Not published | Yes, within Slack's limits |
For most small practices the cheaper compliant answer is a chat tool already under a BAA they hold. Microsoft lists Microsoft Teams among the services in its HIPAA BAA (Microsoft Learn, updated Sep 11, 2026), and Google lists Google Chat in the Workspace services its BAA covers (Google Cloud, Oct 28, 2026). The setup for each is in the Microsoft 365 HIPAA setup guide and the Google Workspace answer.
Decision table: where patient conversations should live
| Option | Best when | Cost or time | Main risk | Our verdict |
|---|---|---|---|---|
| Slack Pro or Business+, no patient details | Chat covers shifts, supplies, IT and huddle logistics | $7.25 to $15 per user per month | Someone types a patient detail in a hurry | Fine with a written rule and training |
| EHR or portal messaging for patient matters | Your EHR has staff messaging | Already paid for | Staff drift back to Slack | The default home for patient conversations |
| Teams or Google Chat under your suite's BAA | You already run Microsoft 365 or Google Workspace | Often already in your license | Defaults left open: guests, sharing | Usually the cheapest compliant chat |
| Slack Enterprise+ with a BAA | Large groups with IT staff | Quote plus DLP, SSO and archiving | PHI in canvases, apps or AI features | Rarely the right fit for 1 to 10 providers |
If you keep Slack on Pro or Business+
Write a one-line rule and enforce it: no patient names, chart numbers, dates of birth, dates of service, photos or symptoms in Slack. A chart number counts, because HIPAA lists medical record numbers among its 18 identifiers (45 CFR 164.514). "Need a callback on the 2:40 add-on, details in the EHR task" works; "Chart 48213 wants her MRI results" does not.
The same request, two ways (sample data)
No identifiers
PHI: chart number and date
Pin the rule in every channel, add it to the new-hire onboarding checklist, and check a sample of messages monthly. Delete anything that breaks the rule and retrain the person.
Mistakes to avoid
- Assuming Business+ is "the secure plan." It has SAML sign-on, not HIPAA support.
- Putting PHI in canvases or lists on the BAA tier. Slack allows it only in messages, files and private channel names.
- Adding Marketplace apps to a PHI workspace. Slack signs no BAA for them.
- Using Slack to reach patients. It is barred even with the BAA.
- Skipping the risk analysis. OCR announced 21 HIPAA settlements and civil money penalties in 2025 (HIPAA Journal compilation of OCR actions, 2026; full list at HHS OCR).
- Check your Slack plan. If it is not Enterprise+, search for chart numbers, surnames and "DOB", and delete what you find.
- Pin the no-patient-details rule in every channel and require 2FA.
- Move patient conversations to your EHR messaging, or to Teams or Google Chat under a BAA you hold.
- List your Slack apps and remove any you do not need.
- Record the decision and the date in your BAA tracker.
Next steps
- Medical practice operations: the system library
Every system guide for a 1 to 10 physician practice, in one place.
- Microsoft 365 HIPAA setup for medical offices
Teams and email under Microsoft's BAA, with the setup checklist.
- HIPAA-compliant texting for medical practices
Where patient-facing messages should go instead of Slack.
Not sure where your team's patient conversations belong?
Score your practice in three minutes, or book a free 20-minute Chaos Audit and we will look at your chat, your EHR messaging and your BAAs. You leave with the decision written down, whether or not you hire us.
Frequently asked questions
Is Slack HIPAA compliant?
Only on Slack's top enterprise tier, with a signed business associate agreement (BAA) and Slack's HIPAA requirements in place. Slack's pricing table marks support for HIPAA compliance on Enterprise+ alone (Slack, Nov 2026). Free, Pro and Business+ cannot hold protected health information.
Does Slack sign a BAA?
Yes, for enterprise customers. Slack's help center says you must be on a Slack Enterprise plan and must execute a BAA, after agreeing to implement its guide for HIPAA entities (Slack Help Center, 2026). You request the guide and the BAA from Slack sales.
Is Slack Business+ HIPAA compliant?
No. Slack's compare table shows support for HIPAA compliance only in the Enterprise+ column, not Business+ (Slack pricing, Nov 2026). Use Business+ for staff logistics with no patient details, and keep patient conversations in a tool covered by a BAA.
Can we message patients through Slack?
No. Even with a BAA, Slack says you may not use it to communicate with patients or their families (Slack Help Center). Use your patient portal or a texting tool that signs a BAA.
Where can PHI go in Slack under the BAA?
Only in messages, files, file names, and the names of private channels or DMs (Slack Help Center). Everything else, such as canvases, lists, workflow forms, profile fields and public channel names, must stay free of PHI, and email into Slack is switched off.
Is Slack AI covered by the BAA?
Slack's HIPAA article does not say. It limits PHI to messages, files, file names and private channel or DM names, and says nothing about AI summaries or recaps (Slack Help Center, checked Nov 17, 2026). Ask Slack in writing before anyone uses AI features near patient conversations.