Skip to main content

Understanding Workspaces

A workspace is a connection between Octopods and your customer platform — Intercom or HubSpot — and it holds the channels you add.

Written by Tarek Khalil

What a workspace is

In Octopods, a workspace represents one connected customer platform account. When you connect Octopods to your customer platform, Octopods creates a workspace that:

  • Authenticates and stays linked to a single Intercom workspace or a single HubSpot portal.

  • Holds the messaging channels (WhatsApp, SMS, Telegram, Messenger, and so on) you connect for that platform.

  • Tracks who connected the workspace and when it was last updated.

Think of a workspace as the bridge between Octopods and the inbox your team already uses. Inbound customer messages flow through the workspace into that inbox, and replies sent from the inbox flow back out through the workspace to the customer’s original channel.

One workspace, one customer platform account

Each workspace links to exactly one customer platform account:

  • An Intercom workspace in Octopods links to one Intercom workspace.

  • A HubSpot workspace in Octopods links to one HubSpot portal.

If your team uses both Intercom and HubSpot, you can connect each to your Octopods account by creating one workspace per platform. If you operate multiple Intercom workspaces or HubSpot portals — for example, one per brand or region — you can connect each as its own Octopods workspace under the same account.

What a workspace contains

Every workspace you connect contains:

  • Channels. The messaging channels (WhatsApp, SMS, Telegram, and others) you’ve added to that workspace. Each workspace keeps its own channel list, so brands and teams stay isolated.

  • Connection metadata. The provider type (Intercom or HubSpot), the linked account name (Intercom app name, or HubSpot portal ID), the admin who connected the workspace, and the last-updated timestamp.

  • Connection status. Whether the workspace is currently connected to the customer platform.

Channel-level configuration — welcome messages, out-of-office replies, signatures, templates, and other per-channel options — lives on the channel itself, inside the workspace.

How a workspace fits into Octopods

The hierarchy in Octopods is straightforward:

  1. Account — your Octopods account, which can hold one or more workspaces.

  2. Workspace — one connection to Intercom or HubSpot.

  3. Channels — the messaging channels you’ve added to that workspace.

Your team members sign in to your Octopods account once and gain access to every workspace under it, subject to their role. Admins can connect new workspaces and manage channels; non-admin team members can use the connected workspaces but cannot connect new ones.

When you need more than one workspace

Most teams start with a single workspace — one Intercom workspace or one HubSpot portal — and add channels to it. Create additional workspaces when:

  • Your business runs multiple brands and each brand has its own customer platform account.

  • You operate in multiple regions with separate customer platform accounts per region.

  • You use both Intercom and HubSpot and want to connect each.

Each workspace you add stays isolated from the others: its channels, its team activity, and its inbox routing are independent.

What a workspace doesn’t do

A workspace doesn’t replace your customer platform inbox — your team still works in Intercom or HubSpot for replies. Octopods doesn’t send messages from a separate UI by default; instead, it makes the connected channels usable from within the inbox you already use.

A workspace also isn’t where you store contacts. Contact records and conversation history live in your customer platform; Octopods routes messages and (where possible) attaches them to the matching contact.


What’s next

Did this answer your question?