What is the difference between a hub and a workspace?

The hub is the area: Finance, People, Sales. It holds instructions, documents, team and a default target. The workspace is a project or process inside the hub — the month's closing, a client onboarding — and is born inheriting the hub's instructions. Every workspace belongs to a hub.

Who sees what is inside a hub?

It depends on the visibility chosen by whoever created it. Private: only the owner and the invited people or groups. Public: anyone in the organization can view and access the documents, but editing, uploading files and managing members stays restricted to the invited. In a private hub or in a workspace, an explicit block denies access to a specific person.

Does the answer inside a workspace use the hub's documents?

Yes. A conversation in a workspace searches the published documents of the company, the hub, the workspace itself and the personal documents of whoever asks — always within what that person can see. Documents from another hub do not come in.

If I invite a group, does whoever joins the group later already have access?

When you add a group, all current members get in with the chosen role, and removing the group removes that access. Whoever joins the group later is not included automatically: add the group again or invite the person.

How many hubs and workspaces can I create?

Any user can create hubs; creating a workspace requires being owner or editor of the hub. The number of hubs per user and workspaces per hub varies by plan — the larger plans have no limit. The numbers are in each plan's offer.

What happens when someone leaves a workspace or a hub?

They stop seeing the documents and conversations of that place. Being removed from the workspace holds even if they stay in the hub. In a public hub, reading stays open to the whole organization; to restrict reading, make the hub private. The hub owner is never left out.

Platform · Hubs and Workspaces

Organized the way your company is organized.

One hub for every area, one workspace for every project or process. The instructions, documents and permissions of a place apply to what lives inside it — and every conversation happens in a chosen place, not in the whole company mixed together.

Try it free Book a demo

See how it works

HUB › WORKSPACE › CONVERSATION

the area, the project and the conversation that happens inside them

PRIVATE OR PUBLIC

whoever creates it decides who sees it; editing always stays with the invited

OWNER · EDITOR · VIEWER

roles per person or per group, with a block when needed

INHERITED CONTEXT

the hub's instructions and documents apply inside the workspace

Where this helps in your work

Three situations where the place of the conversation changes the answer.

The right information usually exists. The problem is that it belongs to an area, and a generic chat does not know that.

Whoever runs an area

“HR asks and the answer comes from HR.”

The People hub holds the policies, instructions and agent of the area. Whoever asks there gets an answer built on People's knowledge — not with Finance's procedure mixed in.

Every area with its own context

Whoever runs a project

“September closing: everything in one place.”

A workspace inside the Finance hub gathers the month's documents, the team and the agent that answers. It is born with the hub's rules; only what belongs to that process changes.

One workspace per process

Whoever manages access

“He left the project. Now what?”

Remove the person from the workspace and they stop seeing its documents and conversations, even while staying in the hub. Invite a whole group at once and remove the group when the project ends.

Access with an owner and a record

How it works

From the area to the conversation, in five steps.

The structure is the same for a company of ten or two hundred people: hubs per area, workspaces per project or process, and the conversation happening inside one of them.

01
Create the hub
One hub per area: Finance, People, Sales, Operations. Name, icon, description and the instructions that apply to everything that happens there. If you prefer, answer three questions and Skyller proposes the draft.
02
Decide who gets in
Private (only you and whoever you invite) or public (the whole organization reads; the invited edit). Invite people or groups as owner, editor or viewer.
03
Open workspaces
Inside the hub, one workspace per project or process: the month's closing, a client onboarding, the audit. It inherits the hub's instructions and, if you want, the team.
04
Add knowledge and a target
Documents live in the hub or in the workspace, with the same review as always. Choose the agent, team or workflow that answers by default in that place.
05
Talk in context
The conversation is born inside the hub or the workspace. Skyller reads the place's instructions and searches the published documents of the company, the hub, the workspace and your own.

Live proof

The same question in two hubs.

This is what separates a workspace from a chat: the answer depends on where the question was asked, because each place has its own instructions and its own documents.

Input
Someone asks “until when do I submit the month's invoices?” inside the Finance hub. Then asks the same question in the People hub.
What Skyller does
1. 01Reads the hub's instructions — and the workspace's, if any — before answering. They are the guidelines of that place.
2. 02Searches only the published documents the person can see: the company's, the hub's, the workspace's and their personal ones. Another hub's procedure does not come in.
3. 03Answers with the source and shows, in the conversation header, in which hub and workspace it happened.
Result
In Finance: “by the 5th, per the Closing Procedure · PRO-021 v2”. In People: Skyller says it found no such rule in that place's documents.

What this scene does not promise

The search reaches what the person can see. A private hub does not come in for whoever was not invited; the exact wording of an answer without a source depends on the configured agent.
The workspace always inherits the hub's instructions; the team, only if inheritance is on. Whoever was removed from a workspace does not come back through inheritance.
Without its own target, the workspace uses the hub's; with neither, the conversation uses the company's or the platform's default agent.

Illustrative scene with fictional data · the mechanism is the product's

Relevant capabilities

What you find when you open Hubs.

Select a topic to see its capabilities, conditions, and limits.

Hub per area: Name, icon, color, description and its own instructions. It is the unit that organizes an area's documents, workspaces, team and conversations.
Workspace per project or process: Always inside a hub. It inherits the hub's instructions and adds its own; it inherits the team if you leave inheritance on.
Create with AI, archive, restore: Three questions generate a hub or workspace draft that you review before creating. Archive what is over, restore if needed, pin favorites.

Application

A Finance hub, a closing workspace, a question with context.

Complete scenario with fictional data. Each step matches a real product action; what depends on configuration is indicated.

01Manager
Creates the Finance hub by answering the assistant's three questions: what to organize, who will use it, what Skyller should follow. Reviews the draft and saves.
Creating with AI is optional; the manual form is the same.
02Manager
Sets the hub as private and adds the Finance group as editor. The People group is not invited.
Visibility and roles are decided by whoever creates the hub.
03Manager
Opens the “September closing” workspace with team inheritance on and the finance agent as default target.
Inheritance can be turned off per workspace; without its own target, the hub's applies.
04Analyst
Publishes the Closing Procedure in the hub's documents tab, after the configured review.
Depends on configuration: governed types and governance mode (see Documents).
05Team
Asks in the workspace “until when do I submit the invoices?” and gets the rule with the procedure as source. Whoever belongs only to the People hub sees neither the hub, the documents nor the conversation.
Private hub: whoever was not invited sees nothing from there.

Comes ready

Hierarchy hub → workspace → conversation, with the header showing where the conversation happens
Visibility, roles, groups, block and ownership transfer
Instruction inheritance, documents tab per place and search across the hierarchy
Create with AI, search, pin favorites, archive and restore

The company decides

Private or public, and who gets in with which role
Inheritance of the hub's team in each workspace
Default target of each hub and workspace
Hub and workspace instructions, and which document types require approval

Straight questions

What teams ask before organizing.

Next step

Start with the area that answers the most questions.

Create a hub for it, add the documents that already exist, invite the team and ask the question that today circulates in the messaging group. Or book a demo: the team sets up the structure with fictional data.