Workspaces

Workspaces let you divide Horizon the way your organization is divided: by area, country or unit, with real data separation between each one. Each team works in its own space and sees only what belongs to it. Leaders who need the full picture get a consolidated view. Permissions are defined separately: which data you see is set by your workspace; what you can do is set by your role.

The problem

Separating one area's data from another's used to mean running two Horizon companies: two logins, two setups, no shared view. Workspaces do it inside a single organization, with a consolidated view for whoever needs the full picture.

How it's structured

Company is the full organization, and also where anything cross-cutting lives. Workspaces are partitions defined by the company (by area, country or unit), and every piece of operational data lives in exactly one. Roles define what a person can do; workspaces define which data they can do it to.

What a workspace is

A workspace is a container with a name and a description. Horizon never forces it to be an area or a country. Each organization picks the dimension that matches how it actually runs.

Workspaces are flat. They do not nest and there are no sub-workspaces. When separation is needed across two dimensions, intersection workspaces cover it.

Where data lives

A piece of data lives in exactly one place: a workspace or the Company level. Never in both.

The two views

A workspace selector sits in the sidebar. What it offers depends on the person's access.

Someone with access to a single workspace lands there directly and never sees the selector. Selection is one at a time: either the consolidated view or one workspace.

Roles

Two roles cover most cases. When all or nothing is too coarse, custom roles cover the rest.

Core roles

Custom roles

A role can be assembled from about 30 granular permissions: viewing Insights, editing Processes, launching Deep Dives, reading Conversations, managing collaborators, and more. Custom roles can be created at the organization level (across every workspace) or at the workspace level (only there).

Four editable starter templates

Who can grant access

• A company admin can create workspaces, create roles and invite anyone with any role.

• A workspace admin can add members to their workspace with custom roles scoped to that workspace, but cannot create another workspace admin and cannot create new workspaces.

• Managing roles and access cannot be delegated. A custom role can never include it, so access administration stays at the organization level.

Anonymization

Horizon can show employee data without identifying the people behind it. Area leaders see what is being reported without attributing it to a specific person.

• Anonymization is a property of the role. It is turned on when defining a custom role, and everyone with that role sees employee data without identities. The Limited access template ships with it on.

• An anonymized role also has no access to raw Conversations or to the collaborator list. The two were designed together.

• Company admins are never anonymized.

Credits per workspace

People across areas

Examples

Four common structures, and the workspace layout that fits each one.

Why it matters

No more separate accounts per area. One Horizon account, multiple workspaces, connected data when you need it. If your company was operating with separate accounts by area, our team can help you consolidate everything into a single account without losing any data.