Skip to main content

Groups and modules

Groups decide what people see: which parts of the app (modules), which agents and which documents. Someone in several groups gets everything their groups have. Admins always see everything.

The Groups page

Creating a group​

  1. Groups → Create.
  2. Name it and say who it is for (Quality: SOPs, deviations and audits).
  3. Pick its modules and agents, then add members.

Modules​

Modules are the parts of the app a group's members see.

ModuleGives
ChatThe web chat and the floating assistant: ask agents, search knowledge.
MailThe team's mailboxes: read, sort and answer them, with agents drafting replies.
CustomersThe workspace's customers, kept here or synced from your system; their mail is marked in Mail.
SuppliersThe same for suppliers.
MCPConnect Claude Desktop, Claude Code and other AI apps with an access token: they search the workspace as the person and can ask agents set up for MCP.

Three levels decide who sees a module:

  1. The workspace (the ⚙ on the Groups page): the modules your workspace uses at all. Switching one off hides it from everyone.
  2. Each group: the modules its members see.
  3. People in no group: their own set, on the same ⚙ page.

Modules decide what people see, not what agents know: an agent answering in Slack still searches with that person's access.

Agents​

  • Agents for all users (on the Users page): agents every user may use, in a group or not.
  • A group's agents: on top of everyone's, for its members.
  • One person's: on the Users page.

Documents​

Uploaded documents can be shared with groups: members find them, others don't. Open a group's Articles to assign documents. A document assigned to groups is visible to those groups and its uploader only; unassigned from every group, it becomes private to its uploader.

Documents from integrations keep their source's own sharing (Drive, SharePoint, mailboxes), whatever the groups.