Chanty's admin and access controls are on the Business plan: customizable roles, SSO, two-factor authentication, retention settings and a signed BAA for HIPAA. Enterprise adds SAML SSO, SCIM provisioning, DLP and an audit trail of AI agent actions. This page lists what is on each plan, what the audit trail records, and how each control maps to a HIPAA risk assessment. For the rest of the product, see all Chanty features for healthcare teams.
- Which access controls Chanty includes, by plan
- Roles and permissions: who can see and do what
- Sign-in and identity: SSO, 2FA, SAML and SCIM
- Audit trail and audit logs: what is recorded
- Retention and data controls
- How these controls map to a HIPAA risk assessment
- Choosing a plan: small practice, multi-location group or small hospital
- Get started
- FAQ
Which access controls Chanty includes, by plan
On the Business plan, Chanty includes:
- customizable roles with 120+ permission settings
- SSO
- two-factor authentication
- one-time-code login
- IP allowlisting
- admin-set retention
- a signed BAA for HIPAA
SAML SSO, directory sync, SCIM provisioning, DLP and governance controls, and unlimited custom roles are Enterprise only.
| Control | Free | Business | Enterprise |
|---|---|---|---|
| Roles and permissions | Not listed | Customizable roles, 120+ settings | Unlimited custom roles, 120+ settings |
| SSO | No | Yes | Yes, plus SAML |
| SAML SSO | No | No | Yes |
| Two-factor authentication | No | Yes | Yes |
| One-time-code login | Yes (chanty.com) | Yes | Yes |
| IP allowlisting | No | Yes (listed as IP Allowlist / location-based access) (chanty.com) | Yes |
| Retention controls | No | Yes | Yes |
| Directory sync and SCIM | No | No | Yes |
| DLP and governance controls | No | No | Yes |
| Audit trail of AI agent actions | No | No | Yes |
| Signed BAA | No | Yes | Yes |
BAA row: On Business and Enterprise, the BAA covers all data in the team space: messages, files, voice notes, tasks and Teambook. Enterprise also includes a negotiated MSA. See what the Chanty BAA covers.
The Free plan has no BAA. Do not use it for protected health information (PHI), including patient names in a front-desk chat.
Roles and permissions: who can see and do what
Chanty has 120+ permission settings. They control what each person can see and do in the workspace. Business includes customizable roles, and Enterprise allows unlimited custom roles.
The roles below are examples a practice might build. You set them up yourself. They are not shipped presets. Chanty ships four base roles (Owner, Admin, Member, Guest/Multi-guest), each with default or customizable permissions. It does not ship named role templates or presets. (chanty.com)
| Example role | Typical configuration |
|---|---|
| Front desk | Front-desk and scheduling-coordination conversations for their location. No access to HR or billing conversations. |
| Clinic manager | All conversations for their site. Can post announcements and assign tasks to site staff. |
| Billing | Billing and payer-follow-up conversations and shared billing files. |
| HR | HR conversations and onboarding materials. Restricted from clinical-operations conversations that may contain PHI. |
| IT admin | Workspace settings, user management, SSO and retention configuration. |
| Location lead | Their own location's conversations plus a cross-location leads conversation. |
Guests. External people stay separate from internal staff. This includes contractors, vendors, outside billing staff and outside providers. A guest sees only the conversations they are added to. Business includes 3 free guest seats per paid member. More detail: guest access for contractors and outside providers.
AI agents (Enterprise only). On Enterprise, the same permission model applies to AI agents. Per-role interaction levels define who each agent takes orders from. Admins can see every agent and revoke it.
Two points apply to agents:
- They are outside the standard BAA. Using them on PHI needs a separate written agreement covering the models you connect.
- Conversations are not used to train outside models.
Move staff chat off personal phones
Chats, calls, announcements and assigned tasks for clinic staff in one workspace. HIPAA-compliant with a signed BAA on the Business and Enterprise plans.
The Free plan has no BAA: do not use it for protected health information.
Sign-in and identity: SSO, 2FA, SAML and SCIM
SSO and two-factor authentication are on the Business plan. They are not reserved for Enterprise.
Business:
- one-time-code login
- 2FA
- SSO
- Duo, a listed SSO and authentication integration
Front-desk and field staff often sign in on their phones, so include the iOS and Android apps when you roll out 2FA. See the mobile app for frontline staff.
Enterprise:
- SAML SSO
- directory sync
- SCIM provisioning
With SCIM, accounts are created and removed from your identity provider. When a medical assistant leaves one of six locations, disabling them in the identity provider also removes their Chanty access. Nobody has to remember a second offboarding step.
If you already use Microsoft 365: Chanty is a separate staff chat. It does not replace Teams. If your organization wants Teams-native meetings and telephony, Teams is the better fit.
Audit trail and audit logs: what is recorded
Chanty keeps an audit trail of user actions and admin activity:
| What is recorded | Examples |
|---|---|
| User actions | Message reads, exports, permission changes, file downloads |
| Admin activity | Users added or removed, role changes |
| AI agent actions (Enterprise) | A real-time trail of every agent action |
Chanty does not publish which plan includes the user and admin audit trail, who can view it, how long entries are kept or how they are exported. Ask the Chanty team to confirm these points in writing before you rely on the log for 45 CFR §164.312(b) (chanty.com/pricing).
Retention and data controls
Retention is set at two levels on Business and Enterprise.
| Level | Who sets it | Range |
|---|---|---|
| Workspace-wide | Admins | For example 30, 90 or 365 days, or unlimited |
| Per conversation | Users and admins | From 1 minute up to 90 days, or unlimited |
Retention applies to messages, files, voice notes, tasks and Teambook. For how files are shared and stored under the BAA, see HIPAA-compliant file sharing.
A common setup:
- a short conversation-level retention for a front-desk conversation where schedule changes are discussed
- a longer workspace default for policies and procedures
On Enterprise, more data controls are available:
- DLP and governance controls. Chanty describes these only in general terms (data loss prevention, retention policies and governance controls). It does not publish specific detection or blocking rules. (chanty.com)
- Data residency in the US, EU or APAC. Other plans have no regional commitment.
- An on-premise option.
- Call recording, with customer-controlled compliance settings for HIPAA.
How these controls map to a HIPAA risk assessment
Chanty supports HIPAA compliance with a signed BAA on Business and Enterprise. It does not make a practice compliant by itself. Your risk assessment still has to cover how you configure and govern it.
| Risk-assessment question | Chanty control | Customer responsibility | Reference |
|---|---|---|---|
| Does each user have a unique identity? | Individual accounts. SSO on Business, SAML SSO on Enterprise. | One account per person, no shared logins | 45 CFR §164.312(a)(2)(i) (unique user identification) (ecfr.gov) |
| Is access limited to what each role needs? | Roles and 120+ permission settings. Guest separation. | Design roles and review them periodically | 45 CFR §164.308(a)(4) (information access management) and §164.312(a)(1) (access control) (ecfr.gov) |
| How is a person authenticated? | 2FA, one-time-code login, SSO | Enforce 2FA for all staff | 45 CFR §164.312(d) (person or entity authentication) (ecfr.gov) |
| Is system activity recorded and reviewable? | Audit trail of user actions and admin activity; a trail of AI agent actions on Enterprise. Plan availability is confirmed by the Chanty team. | Define who reviews logs and how often | 45 CFR §164.312(b) (audit controls) (ecfr.gov) |
| Is data protected in transmission? | TLS 1.2+ in transit. Calls over encrypted WebRTC (DTLS-SRTP) between participants and Chanty's media servers. | Keep devices and networks secured | 45 CFR §164.312(e)(1) (transmission security) (ecfr.gov) |
| Is access removed when staff leave? | SCIM on Enterprise. Removal by an admin on Business. | Include Chanty in offboarding checklists | 45 CFR §164.308(a)(3) (workforce security), with termination procedures at §164.308(a)(3)(ii)(C) (ecfr.gov) |
| Is data kept only as long as needed? | Workspace and conversation retention | Set retention to match your policy | HHS: the Privacy Rule sets no medical-record retention period, so state law governs, and safeguards apply for as long as the data is held (45 CFR §164.530(c)). The 6-year rule in §164.316(b)(2)(i) covers Security Rule documentation, not chat messages. (hhs.gov) |
Chanty is not end-to-end encrypted. Data is encrypted in transit, and file storage is encrypted.
Customer responsibilities under the shared-responsibility model:
- signing the BAA before any PHI enters the workspace
- configuring roles and permissions
- managing user access and offboarding
- device security
- staff policies and training
- on Enterprise, choosing which AI models and agents connect and what they can access
Scope reminders:
- The BAA covers all data in the team space.
- It does not cover third-party integrations such as Google Drive, Zapier, Make or n8n. Each integration that touches PHI needs its own BAA with that vendor.
- AI agents used on PHI need a separate written agreement.
For the full trust overview, see the security, HIPAA and BAA overview. For the product itself, see HIPAA-compliant chat for staff.
Choosing a plan: small practice, multi-location group or small hospital
| Situation | Plan | Why |
|---|---|---|
| Single clinic or small practice | Business | BAA, SSO, 2FA, customizable roles, retention. $3 per user per month billed annually ($4 billed monthly). (chanty.com) |
| Multi-location group with an identity provider | Enterprise | SAML SSO, directory sync, SCIM, DLP, data residency. Sales-led. (chanty.com) |
| Small hospital administrative and operations teams | Business or Enterprise, depending on audit-log needs | Get audit-log scope confirmed by the Chanty team first (see the audit trail section above) |
Small hospitals. Chanty fits the coordination work of administrative and operational staff, alongside your clinical systems. Examples:
- HR announcements
- IT requests
- facilities issues
- billing follow-ups
It is not a clinical handoff, urgent clinical alerting, patient messaging or clinical documentation tool. For how these teams work together day to day, see team collaboration for healthcare.
Evidence for reviewers:
- SOC 2 Type II and ISO/IEC 27001:2022 reports are available on request.
- The Business and Enterprise terms include a 99.9% monthly uptime commitment.
To check costs, compare Business and Enterprise pricing. To see how other staff chat tools handle BAAs, see team chat tools compared on HIPAA.
Get started
Review the security, HIPAA and BAA overview with your privacy or IT lead. Then create your Chanty workspace on the Business plan.
Sign the BAA before any PHI enters the workspace.
Move staff chat off personal phones
Chats, calls, announcements and assigned tasks for clinic staff in one workspace. HIPAA-compliant with a signed BAA on the Business and Enterprise plans.
The Free plan has no BAA: do not use it for protected health information.
FAQ
Does Chanty have audit logs?
Yes. Chanty keeps an audit trail of user actions (message reads, exports, permission changes, file downloads) and admin activity logs (users added or removed, role changes). On Enterprise, a real-time trail also records every AI agent action. Chanty does not publish which plan includes the user and admin audit trail or how long entries are kept, so ask the Chanty team to confirm before you rely on it (chanty.com/pricing).
Is SSO available without Enterprise?
Yes. SSO and 2FA are on the Business plan. SAML SSO, directory sync and SCIM are Enterprise only.
Can I restrict what each staff role can see?
Yes. Business has customizable roles with 120+ permission settings. Enterprise allows unlimited custom roles.
Is Chanty HIPAA compliant on the Free plan?
No. The Free plan has no BAA and should not be used for PHI. The BAA is available from the Business plan.
Does the BAA cover integrations like Google Drive or Zapier?
No. Each integration that touches PHI needs its own BAA with that vendor.
Can we set message retention?
Yes, on Business and Enterprise. Admins set workspace-wide retention, and users and admins can set it per conversation. Retention covers messages, files, voice notes, tasks and Teambook.
Is Chanty end-to-end encrypted?
No. Data is encrypted in transit with TLS 1.2+, and file storage is encrypted.
Is Chanty suitable for clinical alerts in a hospital?
No. Chanty is for operational and administrative staff coordination alongside clinical systems.