Your messages go where you go — across every coaching space
If you work with more than one coach, or run a coaching business while also being enrolled as a client somewhere else, you've probably wondered: does each organization get its own chat, or does everything mix together? The answer matters — both for privacy and for keeping your conversations organized. Here's exactly how chat works across multiple coaching organizations on Coachful, and why it's built this way.
TL;DR — The quick answer
- Each coaching organization on Coachful is a fully isolated chat environment. Messages in one org are never visible in another.
- Coachful uses Stream's team-based multi-tenancy architecture, which enforces hard boundaries between organizations at the infrastructure level — not just the UI.
- A single Coachful account (email + password) lets you belong to multiple organizations simultaneously — you switch contexts, not accounts.
- Squads, direct messages, and group calls each live inside the organization where they were created.
What "multi-tenant chat" actually means
Coachful is a multi-tenant SaaS platform — meaning hundreds of coaching businesses run on shared infrastructure, each one completely walled off from the others. Chat is powered by Stream Chat, one of the most widely used real-time messaging APIs in the industry. Coachful implements Stream using team-based multi-tenancy, where every coaching organization maps to its own Stream "team."
In practice, this means the isolation isn't just a permissions check on the Coachful side — it's enforced at the Stream layer too. A channel that belongs to Organization A literally cannot be queried by a user whose active context is Organization B. There's no admin override, no workaround, and no accidental data bleed.
For coaches who are serious about client confidentiality, this architecture matters. Your clients' conversations with you are not accessible to any other business on the platform — ever.
How organizations, roles, and chat contexts work together
When you sign up for Coachful, you create a user account. That account can then be associated with one or more organizations. Inside each organization, you hold a specific org role:
- super_coach — the owner of the coaching business (you, if you created the org)
- coach — a team member who delivers coaching
- member — a client enrolled in the organization
- virtual_assistant — an editor/admin who helps manage the business without coaching
Your chat permissions within each organization are determined by that org-level role. A coach who is also a client at a different coaching business holds a coach role in one org and a member role in the other. The chat experience adapts accordingly — seeing the full coach dashboard in one context, and the client-facing squad view in the other.
Pro tip: If you coach clients and are simultaneously enrolled in your own mentorship or mastermind, Coachful keeps these workspaces completely separate. Switch between them from the organization selector in the top navigation — no logging out and back in required.
The two types of squads and where they live
Most chat in Coachful happens inside Squads. There are two kinds, and both are scoped to a single organization:
Cohort squads
A cohort squad is automatically created when clients enroll in a Program. If you run a 12-week weight-loss program, every client who joins that cohort gets added to a shared squad channel for that program. The squad exists inside your organization — clients from another coach's organization are never mixed in, even if they happen to be on the same underlying Coachful infrastructure.
Community squads
Community squads are always-on group chat spaces inside an organization — think of them as your coaching community's Slack-style home base. Coaches create them manually, invite specific members, and they persist independently of any program enrollment. Like cohort squads, they are fully scoped to the organization they belong to.
Both squad types support real-time messaging powered by Stream, with features like threads, reactions, file attachments, and @mentions. None of that content crosses organizational lines.
Direct messages across organizations: what's possible
Direct messages (1:1 chats) between a coach and a client also live inside the organizational context where that relationship was established. If Sarah is your client in your "Elite Performance Coaching" org, your DM thread with her lives in that org. If Sarah also happens to be enrolled in a completely separate nutrition coaching business on Coachful, her conversations with that coach are in a different org and are invisible to you — as they should be.
There is currently no cross-organization direct messaging. This is intentional. Allowing arbitrary cross-org DMs would create serious privacy and compliance headaches. If you need to contact someone outside of a shared organizational context, use email or an external channel.
Want to centralize all your coaching communication in one place? Coachful gives every coach a custom-branded workspace — including a subdomain like yourname.coachful.co or your own custom domain — so clients always know exactly where to go. Start your free trial and see how it works.
Switching between organizations as a user
If your Coachful account is linked to multiple organizations — which is common for coaches who are also clients, or coaches who run more than one brand — switching is straightforward:
- Open your Coachful app or browser workspace.
- Click your profile avatar or organization name in the top navigation bar.
- Select Switch organization from the dropdown.
- Choose the organization you want to move into.
- Your entire workspace — programs, squads, bookings, and chat — reloads in the context of the selected org.
Notifications are also org-aware. A badge on the app icon or browser tab may aggregate unread counts across all your orgs, but tapping into a notification takes you directly to the correct organizational context and the specific channel where the message lives.
Video calls and how they relate to chat
Coachful's HD video (also powered by Stream) follows the same organizational boundaries as text chat. When a coach schedules a 1:1 session, a group call, or an instant call, that call exists within their organization. Clients receive booking links and notifications tied to that org's context.
Video call history — including any recordings or session notes — is stored within the organization where the call was created. You won't see call logs from a different org bleed into your coaching dashboard.
For coaches running group calls inside a cohort program, the call is surfaced inside the relevant cohort squad so participants can jump in from their chat feed. This keeps the experience seamless: conversation, documents, and live sessions all in one place, all within the right organizational boundary.
Best practices for coaches managing multiple brands or orgs
Some coaches run more than one coaching business — a personal brand and a corporate training arm, for example, or a group program and a high-ticket 1:1 practice under separate identities. Here's how to keep things clean:
- Create a separate organization for each brand. Each org gets its own subdomain (or custom domain), its own client roster, its own programs, and its own isolated chat environment.
- Use descriptive squad names. Since squad names only need to be unique within an org, keep them descriptive so your team doesn't confuse which program a squad belongs to when they switch contexts.
- Assign virtual assistants per org. A virtual_assistant granted access to Org A cannot see anything in Org B. If you want help in both, they need to be added to both orgs explicitly.
- Don't rely on workarounds for cross-org communication. If two of your brands genuinely need to share channels, consider merging them under one organization with well-named community squads, rather than trying to bridge two separate orgs.
Best practice: Use the Michelle AI assistant inside your coach dashboard to quickly look up squad membership, find client conversations, or navigate between programs. Michelle can answer questions and take actions across your current org context — a big time-saver when you're juggling multiple programs and clients.
Troubleshooting: common chat issues across organizations
I can't find a squad I was part of before
Check which organization you're currently viewing. Navigate to the org selector and confirm you're in the right one. Squads are org-scoped — if you're in Org B, you won't see squads from Org A. Switch orgs and the squad should reappear.
A client says they're not receiving my messages
First, confirm the client is enrolled in the correct organization and has accepted their invitation. Then check that the squad they should be in exists and that their account was added to it — either automatically via program enrollment (cohort squad) or manually (community squad). If the client is in multiple orgs, they may be viewing the wrong one on their end.
Chat notifications are showing for an org I'm no longer active in
If you've been removed from an organization but still see stale notifications, sign out and back in to force a token refresh. Notification tokens are scoped per org, and a full re-authentication cycle clears lingering references. If the issue persists, contact support@coachful.co.
My coach role in one org isn't carrying over to another
Roles are explicitly set per organization. Being a coach in Org A doesn't grant you any elevated permissions in Org B. An admin of the second organization needs to assign you the correct org role there. This is by design — it protects both organizations' data and access controls.
Video calls appear in the wrong squad
Calls are surfaced in the squad associated with the program or booking context they were created under. If a call appears in an unexpected squad, check whether the booking was accidentally created under the wrong program. You can edit session details from Coach → Bookings within the correct org.
I can see two organizations but chat only loads in one
This is usually a browser caching issue or a slow connection during org switching. Do a hard refresh (Ctrl+Shift+R / Cmd+Shift+R), or try switching organizations again. If Stream Chat doesn't reconnect after switching, closing and reopening the app resolves it in most cases.
How Coachful keeps your data private between organizations
Beyond the technical isolation provided by Stream's multi-tenancy model, Coachful enforces organization-level data separation at the database layer too. Client profiles, session notes, program progress, and billing details are all partitioned by organization ID. A query issued in one organizational context is structurally incapable of returning records belonging to another.
For coaches operating in regulated industries — health coaching, mental performance, financial coaching — this architecture supports confidentiality requirements without needing any custom configuration. The isolation is on by default, for every organization, always.
You can learn more about how Coachful handles data in our Privacy Policy and explore messaging-specific details in our Stream Chat overview.
Ready to simplify your multi-org coaching setup?
Whether you're a solo coach building your first program or running multiple brands with a team of coaches underneath you, Coachful's architecture grows with you. Isolated chat environments, flexible org roles, and a single login that spans every organization you belong to — it's the infrastructure serious coaching businesses need, without the IT overhead.
If you're not yet on Coachful, start your free trial and see how programs, squads, video calls, and billing work together in one clean workspace. Already a member? Sign in to your Coachful workspace and explore your organization settings today. For more guides like this one, browse the full help center.