Workspaces

A workspace is one business in ImpelLabs. All data belongs to a workspace, and a person can only read the data of workspaces they belong to.

What a workspace holds

Members, their roles and their departments.
Agents, channels, contacts and conversations.
Knowledge, the wallet of credits and the approval rules.
Business details: name, website, phone, address, business hours, language, time zone and region.

The region is set when the workspace is made and does not change. It says where the data lives. The time zone sets how business hours read.

Members and roles

A member has one role.

Role	What it means
`owner`	Holds every capability at workspace scope.
`admin`	Holds every capability at workspace scope.
`manager`	Holds the same preset set as `member`. Department scope applies to the departments they manage.
`member`	Holds the preset set: see and use shared things, and manage what they own.

A workspace can also make custom roles. A custom role replaces the preset role, and a member can have overrides on top. A deny override always wins. Every capability is held at one scope: own (what the member owns or added), department (what belongs to a department they manage, plus their own) or workspace (everything). See access and keys.

Departments

A department groups members. A department agent belongs to a department. You can share an agent or a channel with a whole department.

Workspace and token

An API token names its workspace, so a request with a token needs no workspace header. The token cannot reach other workspaces, and it cannot list or make workspaces. Those actions need a signed-in session in the app.

Pause all agents

A workspace can pause every customer-facing agent. While paused, agents, workflows and broadcasts send nothing to customers. A message a person writes still goes out.

Closing a workspace

While a workspace is closing, only its owner can sign in, to export data or to reopen it.

Get started

Concepts