Hub — Overview

The Hub is SquadOS’s internal workspace. In it, people in the same organization talk in rooms and direct messages, while people and agents work together in internal conversations. The admin panel is the separate area where authorized people configure agents, bases, inboxes, tools, and other resources.

Before you start

SquadOS rolls out collaborative navigation gradually. Two organizations may therefore see different layouts without having different data or resources:

in the new experience, a global rail switches among Rooms, Agents, Direct, Meetings, and the Admin panel;
in the legacy experience, the sidebar brings together My Agents, My Conversations, Meetings — when available in the plan — and the admin-panel entry.

On a computer, the new experience’s rail is a narrow column on the left. On smaller screens, open the side menu: the same areas appear in a strip at the top of the drawer. The adjacent column shows only the selected area’s content, not every list at once.

Hub areas

Area	What you find	Access required in the new experience
Rooms	Topic-based conversations with participating people and agents	Access Rooms (`rooms.access`)
Agents	Internal agent conversations and the New Conversation button	Access Hub (`hub.access`) and access to the selected agent
Direct	Private conversations between two people in the organization	Access Rooms (`rooms.access`)
Meetings	Permanent meetings, link meetings, and records, depending on the plan and gradual rollout	Access meetings (`meetings.access`), plus the Calls feature in the plan
Admin panel	The first admin area the person is allowed to use	At least one compatible admin or support capability

In organizations with no other active person, the new experience may show only Agents among the collaborative areas. Meetings appears in the new rail only when its navigation is enabled, the plan offers Calls, and the person has the required permission. During coexistence, the legacy sidebar determines the Meetings entry from Calls availability.

See Rooms for participants, mentions, threads, and direct conversations.

Under Rooms, the sidebar lists active rooms you participate in; archived rooms are in a separate group.
Under Agents, the sidebar lists recent conversations, not the complete agent catalog. Use New Conversation and select the agent in the composer.
Under Direct, the sidebar lists conversations between you and one other person.
Under Meetings, the sidebar lists the groups available in the enabled meetings experience.

The Search button (Ctrl+K on a computer) searches room names, direct-conversation participants, available agents, and recent conversations. It does not search message text.

Notifications and unread items

Numbers in the rail have different meanings:

under Rooms, the number totals only mentions of you in active rooms; a room with ordinary unread messages is still emphasized in the sidebar without increasing this number;
under Direct, the number totals unread messages;
Agents, Meetings, and the Admin panel do not use this counter.

Archived rooms do not contribute to the rail’s mention total.

Agent conversations

You do not need to connect an inbox to use an agent internally. Open Agents, choose New Conversation, select an allowed agent, and send the first message. The conversation is only persisted on that first send.

The catalog offers active agents allowed for the organization and for your individual access. Older conversations with an archived agent may remain in history. Conversations with no current agent also exist, so the history must not be treated as the list of available agents.

During a conversation, the composer selector can change the allowed agent or model. If a transfer changes the current agent, the conversation remains grouped in history under the agent it started with.

For a quick, controlled test while configuring an agent, use the test panel inside the agent editor. Use the Hub when you want to keep the internal conversation in history and work with the agent day to day.

Hub and admin panel

Access is not defined by a fixed ladder of roles. Each Function grants specific capabilities, and one person may accumulate more than one Function. Someone may therefore use Rooms without opening Agents, chat with agents without administering their configuration, or access only part of the admin panel.

The AI Agents, Attendant, and Collaborator templates include the three basic collaboration permissions: Hub, Rooms, and Meetings. Collaborator does not mean complete admin access. A Custom Function starts with Rooms access and may receive other permissions separately. Owners retain broad organization access.

See Users and roles to configure Functions and understand compatibility with legacy roles.

Agent memory

Under Memory, you can review what agents have retained about you across conversations. Items are separated into profile facts and facts learned by each agent. You can pause, resume, correct, or delete your own items; superseded items remain available under See what changed. Administrators can inspect another person’s memory, but the interface only lets the owner edit those items.

This page requires Access Hub. The address belongs to the application, so it does not carry the documentation’s /en prefix.

Account, reading, and active organization

At the top right, Hub controls open:

Adjust reading, for size, font, spacing, and — in rooms — message layout;
the light or dark theme;
the account menu, whose Account entry leads to Profile and Preferences.

Administrative settings entries appear separately and depend on the person’s capabilities. See User settings.

In the legacy experience and admin areas, the switcher at the top of the sidebar lists only organizations you belong to; switching organizations invalidates and reloads the active context’s data. The new collaboration sidebar shows the active name but currently does not offer the switcher. If it is not visible, open Organizations directly to choose another organization. See Multiple organizations.