Answer · Published Nov 18, 2026
Is Asana HIPAA Compliant? The BAA, Enterprise+ and the Rules
For practice managers and owners who track work in Asana. You will leave knowing the one plan that carries the BAA, the use rules Asana attaches to it, the settings to switch on, and how to run patient work on any other plan.
Only on Enterprise+. Asana lists HIPAA compliance as an opt-in on Enterprise+ alone, under its Business Associate Addendum (Asana pricing, Nov 2026); Personal, Starter, Advanced and Enterprise carry no BAA. Even on Enterprise+, Asana bars using it as a system of record for PHI, and your settings decide compliance.
Key takeaways
- HIPAA is opt-in on Enterprise+ only; legacy Enterprise customers must move to Enterprise+ to enable it (Asana Help Center).
- Before any PHI goes in, every user needs two-factor authentication, SSO or Google sign-in, and a work email domain: personal email domains are not permitted (Asana HIPAA Use Requirements, Aug 29, 2025).
- Asana may not be used as a system of record for PHI or to communicate directly with patients, even with the BAA.
- Switching HIPAA on turns integrations and personal access tokens off by default for anything new; apps already enabled stay on until a super admin reviews them, and some Asana AI tools may be unavailable.
- A chart number is a medical record number, one of HIPAA's 18 identifiers, so a chart-number project on Advanced holds PHI (45 CFR 164.514).
The short answer, from Asana's own pages
Asana supports HIPAA-regulated work on one plan, Enterprise+, after a super admin accepts its Business Associate Addendum and switches HIPAA on. Asana's Help Center says HIPAA compliance "is governed by Asana's Business Associate Addendum (BAA)" and that legacy Enterprise customers must move to Enterprise+ to enable it (Asana Help Center, Nov 2026). The pricing table marks HIPAA "Opt-in" in the Enterprise+ column and nowhere else.
| Plan | List price (per user per month, billed yearly) | HIPAA | What that means for patient data |
|---|---|---|---|
| Personal | US$0, 2 users | Not available; PHI barred from free versions | No patient identifiers |
| Starter | US$10.99 | Not available | No patient identifiers |
| Advanced | US$24.99 | Not available | No patient identifiers |
| Enterprise | Contact sales | Not available | No patient identifiers |
| Enterprise+ | Contact sales | Opt-in, with the BAA | PHI allowed in set places, under Asana's use rules |
Source: Asana pricing and its compare table, opened Nov 17, 2026. Asana describes Enterprise+ as adding SIEM integration, data residency, audit logs and dedicated workspaces.
The BAA sits two tiers above the last list price: Asana per user per month, billed yearly
Gray: no BAA. Dashed teal: BAA available, no list price. Bars scaled to Advanced, the highest listed price.
The rules that come with Asana's BAA
Asana's BAA comes with written use rules, and a practice that breaks them is outside what Asana agreed to. The HIPAA Use Requirements and Limitations (Asana, last updated Aug 29, 2025) say you must:
- Move every Workspace or Division into a single Organization, because HIPAA works domain-wide.
- Keep two-factor authentication, SSO or Google Authentication on for every user.
- Give every user a dedicated work email domain. Personal email domains are not permitted.
- Limit who sees PHI on a need-to-know basis, using private tasks and private projects.
- Watch for unusual activity yourself with Asana's APIs and audit log.
- Sign separate BAAs with any integration vendor, including apps in Asana's App Directory. Asana does not sign them for you.
Three limits matter most in a practice. You "shall not use the Asana SaaS Services as a system of record for PHI", so the chart stays in the EHR. You may not use Asana to talk to patients or give them accounts. And PHI may go through no other Asana channel, such as support tickets or email to Asana staff. Asana's Help Center adds where PHI may sit: task titles, project or task descriptions, custom fields on tasks, comments and attachments on tasks. Goals should not hold PHI.
Turning it on, and the settings that matter
A super admin turns HIPAA on in the Admin Console under Security, then HIPAA compliance, reviews the BAA and the use rules, and waits up to 24 hours for it to apply across the domain (Asana Help Center). Then map each HIPAA technical safeguard in 45 CFR 164.312 to Asana:
| Safeguard | What Asana requires or offers | Who does it |
|---|---|---|
| Unique user identification | One account per person on a work email domain; no personal domains | Your admin, required by Asana's rules |
| Person authentication | 2FA, SSO or Google Authentication for every user | Your admin, required before any PHI |
| Access control | Private projects and private tasks for patient work; need-to-know only | Project owners |
| Audit controls | Audit log and APIs; Asana makes monitoring your job | Your admin, on a schedule |
| Integrations | Integrations and personal access tokens off by default; new apps need super admin approval; apps enabled before HIPAA stay on until reviewed | Super admin, plus a BAA from each app vendor |
| AI features | Some Asana AI tools unavailable or off by default; turning them on is at your own risk | Leave off unless covered |
Log the BAA acceptance date in your business associate agreement tracker and list Asana as an asset in your security risk assessment. HIPAA itself requires a BAA to bind the vendor to safeguards and breach reporting (45 CFR 164.504(e)); Asana's use rules are the price of that promise.
Choosing the setup, writing the project rules and locking down access 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 AuditPatient work on a plan without the BAA
On Personal, Starter, Advanced or Enterprise, a project can track patient work only if nothing in it identifies the patient. HIPAA lists 18 identifiers, including medical record numbers and every date element except the year for dates tied to a patient (45 CFR 164.514(b)(2), eCFR current as of Nov 13, 2026). HHS says a cloud service that stores PHI is a business associate even if it holds only encrypted data, and using one without a BAA "is in violation of the HIPAA Rules" (HHS OCR cloud guidance).
The workable option is a random reference code per case, such as K7Q2M9, with the key kept only in the EHR. HIPAA allows such a code when it is not derived from information about the patient and the mapping is never disclosed (45 CFR 164.514(c)). The method is in the BAA route or reference codes guide, and the full Asana build is in the Asana setup guide for a small practice.
One callback task, two compliant ways (sample data)
Assignee: front desk
No identifiers in the task
Assignee: front desk
PHI under the BAA, EHR stays the record
Worked example: a six-person office
Six users on Advanced cost about US$1,799 a year at list price with no BAA; Enterprise+ is a quote. Worked example: a two-physician pediatric practice with an office manager, three front-desk staff and two medical assistants.
| Plan | Inputs | Per year | BAA |
|---|---|---|---|
| Starter | 6 x US$10.99 x 12 | US$791.28 | No |
| Advanced | 6 x US$24.99 x 12 | US$1,799.28 | No |
| Enterprise+ | Ask sales for a six-seat HIPAA quote | Not published | Opt-in |
Before you ask for that quote, check the fit: Enterprise+ still bars Asana from being the system of record, so it suits practices that need chart numbers and dates on tasks, not ones hoping to move charting out of the EHR.
Decision table: which setup fits
| Option | Best when | Cost or time | Main risk | Our verdict |
|---|---|---|---|---|
| No patient work in Asana | Projects run SOPs, hiring, onboarding, equipment and staff tasks | Any plan | A name slips into a comment | Fine on any plan; still require 2FA |
| Reference codes on Advanced or below | Tasks need an owner and a status, not dates or diagnoses | Plan price plus a minute per case | Staff type chart numbers from habit | Best fit for most 1 to 10 provider offices |
| Enterprise+ with HIPAA on | Tasks must carry chart numbers, dates or clinical context | Enterprise+ quote | Personal email logins, unapproved apps, PHI in goals | Right when the work needs PHI and you can follow every use rule |
The three tools' plan ladders sit side by side in ClickUp vs Monday vs Asana, and Slack, which many Asana offices pair it with, is covered in the Slack HIPAA answer.
Mistakes to avoid
- Buying Enterprise and assuming HIPAA. It is Enterprise+ only.
- Letting staff sign in with personal email. Asana's rules forbid personal email domains once HIPAA is on.
- Leaving old integrations running. Apps enabled before HIPAA stay on; review each one, and keep only those whose vendor signs its own BAA.
- Putting PHI in project names or goals. Keep it to task titles, descriptions, task custom fields, comments and attachments.
- 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 Asana plan in the Admin Console. If it is not Enterprise+, search projects for chart numbers and surnames and clear them.
- Require two-factor authentication or SSO for everyone, and remove personal email accounts.
- Decide: reference codes on your current plan, or an Enterprise+ quote with HIPAA.
- List every connected app and ask each vendor whether it signs a BAA.
- Record the plan, the BAA status 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.
- The BAA route or reference codes, for every project tool
The method behind the two setups on this page.
- Is ClickUp HIPAA compliant?
The same answer for ClickUp, where the BAA sits on Enterprise and Max.
Not sure which setup your projects need?
Score your practice in three minutes, or book a free 20-minute Chaos Audit and we will look at what your projects hold and which setup fits. You leave with the decision written down, whether or not you hire us.
Frequently asked questions
Is Asana HIPAA compliant?
Only on Enterprise+, with HIPAA switched on. Asana's pricing table lists HIPAA compliance as opt-in on Enterprise+ alone (Asana, Nov 2026), governed by its Business Associate Addendum (BAA). Your settings, your staff and Asana's own use rules still decide whether your use is compliant.
Does Asana sign a BAA?
Yes, as a Business Associate Addendum that a super admin accepts in the admin console under Security, then HIPAA compliance (Asana Help Center, 2026). Allow 24 hours for HIPAA compliance to activate across the domain.
Is Asana Enterprise enough for HIPAA?
No. HIPAA is opt-in on Enterprise+, not Enterprise, and Asana says existing legacy Enterprise customers who have not enabled HIPAA must move to Enterprise+ to enable it (Asana Help Center, 2026).
Can we put patient information in Asana's free plan?
No. Asana's HIPAA terms say you shall not submit PHI into any free version of its services (Asana HIPAA Use Requirements, Aug 29, 2025). On Personal, Starter, Advanced or Enterprise, keep every patient identifier off the board.
Can Asana be our system of record for patient information?
No. Even on Enterprise+, Asana's terms say you shall not use the service as a system of record for PHI, and shall not use it to communicate directly with patients (Asana, Aug 29, 2025). The EHR stays the record; Asana tracks the work.
Are chart numbers PHI in Asana?
Yes, when they sit next to anything about a patient's care. HIPAA lists medical record numbers among the 18 identifiers that must be removed before information counts as de-identified (45 CFR 164.514(b)(2), 2026). On a plan without the BAA, use random reference codes instead.