Skip to main content

Workspaces

A workspace is the container for your organization's meetings, members, teams, integrations, settings, and AI configuration. Most customers use a single workspace; a single user can belong to several workspaces and switch between them.

What lives in a workspace​

Each workspace has its own:

  • Members and teams
  • Roles and custom permissions
  • Conversations (meetings, transcripts, insights, action items)
  • Insight projects, definitions, and project knowledge
  • Integrations and connected apps (Marketplace)
  • AI provider catalog and default models (Intelligence)
  • Org name, logo, handbook, and branding (General)
  • Subscription and billing

Workspaces are isolated from one another — a member of Workspace A does not automatically see anything in Workspace B.

Creating and switching workspaces​

Create a workspace​

A new workspace is normally created during onboarding. To create another, contact Harmony support — there is no fully self-serve "create workspace" flow exposed to most users today.

Switch workspaces​

If you belong to multiple workspaces:

  1. Click your workspace name (or your avatar) in the top-left of the sidebar.
  2. Pick the workspace you want to switch to.
  3. The app reloads in the context of that workspace.

You sign in once with your Harmony account; switching does not require re-authenticating.

Who can manage a workspace​

Harmony does not have a separate "Owner" role. Workspace administration sits with members assigned the built-in Admin role, which has every standard permission at the all scope. Capabilities like changing organization settings, managing roles, configuring integrations, or accessing billing are controlled by individual permissions (organization:update:all, roles:*:all, integrations:*:all, billing:*:all) — not by an Owner persona. See Roles and Permissions for the full model.

For practical purposes, the term "workspace owner" in casual support conversations usually means "a member with the Admin role".

Inviting and managing members​

Workspace members are added under Settings → Users. See Teams and Users for the full add / edit / deactivate flow.

There is no broad guest-access feature for non-members today. Sharing a single conversation through the Share menu generates a link, but the recipient still needs the appropriate permissions to view it (see Sharing meetings).

Cross-workspace behaviour​

Some behaviours that customers commonly assume are not supported today:

  • Cross-workspace data sharing. Conversations, insights, contacts, and accounts are scoped to a single workspace.
  • Cross-workspace insight aggregation. There is no built-in dashboard that aggregates data across multiple workspaces.
  • Per-workspace billing under one organization. Billing is per workspace; there is no parent-organization billing surface.
  • Workspace-level export / import. There is no self-serve "export workspace and reimport into another workspace" flow.

If you have a use case that needs any of the above, contact Harmony support.

Deleting a workspace​

There is no fully self-serve "Delete Workspace" UI today. Two related flows do exist and are sometimes confused:

  • Delete Account — under Workspace Settings → Danger Zone, route /workspace/{workspaceSlug}/settings/delete. This deactivates the user's Harmony account and removes their workspace memberships. It is blocked when the user is the only active admin in any workspace they belong to. The flow requires typing DELETE to confirm. See Deleting your account.
  • Subscription cancellation — cancelling a paid subscription does not delete the workspace or its data.

To remove an entire workspace and the data inside it, contact Harmony support so the request can be tracked and the data retention policy applied correctly.

Branding​

The organization logo and name live on the General settings page (see General Settings). Customer-configurable email branding (for example, custom email templates) is not a self-serve setting today; mention it in your account conversation if you need it.

Best practices​

  • Prefer a single workspace for a single legal entity. Use teams to separate departments rather than spinning up multiple workspaces.
  • Assign at least two Admins per workspace. The Delete Account flow blocks the only active admin from leaving, which can be inconvenient if a single Admin needs to depart.
  • Audit role assignments periodically — Custom Roles can drift from their original purpose.