Groups
A group is a team with a page of its own. It appears in the GROUPS section of the sidebar and opens at /groups/{id}, where six tabs hold everything the group works with.
Ask Autopilot instead. Everything on this page can be done by asking Autopilot in plain language. It creates teams and groups, adds and removes people, changes roles, nests teams, and archives and restores, all without opening a form. See Doing All of This with Autopilot.
Use a group when a set of people share more than a name: a support function with its own knowledge and ticket queue, a finance team with its own AI Employees and integrations, a project that should not see the rest of the Workspace's resources.
The sidebar GROUPS section
The section lists the groups you are in, whichever way you reached them, and each row opens that group's page. Only groups appear here. Teams do not, because a team has no page to open.
The + in the section header creates a group. It appears only for Workspace admins, since creating a group needs the group.manage capability.
The section is hidden when you are in no groups and cannot create one.
Creating a group
- Select the + in the sidebar GROUPS header.
- Give the group a Name. It must be unique within the Workspace, compared without regard to case.
- Add a Description if it helps somebody else understand what the group is for. This is optional.
- Select Create group.
Ema opens the new group's page, and the group appears in the sidebar. You are its first admin, and it starts with one person: you.
Fill it from the tabs on this page: add people on Permissions, and create the group's first AI Employee or knowledge base on their tabs.
Pick the type carefully. This dialog always creates a group. Create team on the Teams tab always creates a team. The type is permanent: a group cannot become a team, and a team cannot become a group. To change it, archive the one you have and create the other.
The tabs
| Tab | What is on it | Shown when |
|---|---|---|
| AI Employees | The AI Employees this group owns, and the ones shared with it | Always |
| Tickets | The group's ticket queue | Ticketing is enabled and the group has a queue, or you can set one up |
| Knowledge | The knowledge bases this group owns, and the ones shared with it | Always |
| Integrations | Shared connections and data sources the group can reach | Always |
| Permissions | People and teams with access, and their roles | Always |
| Settings | Name, description, and deleting the group | Always. Read-only unless you are a group admin. |
The active tab is in the URL as ?tab=, so a group tab can be linked to and survives a refresh.
AI Employees
Every AI Employee the group owns, plus every one explicitly shared with it, as the same cards the main AI Employees page uses.
Create AI Employee opens the template picker with this group already set as the owner, so an AI Employee created here belongs to the group from the start. The button appears for group admins and builders, which matches the rule the backend applies, so a plain member is not offered an action that would be refused.
See Group-Owned AI Employees and Knowledge Bases.
Tickets
The group's ticket queue: one queue per group, taking the group's name, worked by the people in the group. Membership of the group is what grants access to the queue.
See Ticketing.
Knowledge
The knowledge bases the group owns and the ones shared with it, with an Access column that says which is which: Owned for the group's own, and Shared with this group for a knowledge base granted from elsewhere.
Add knowledge base creates one owned by this group. It appears for group admins and builders.
A group-owned knowledge base is a searchable knowledge base in its own right rather than something attached to an AI Employee, and Autopilot can search it for the people in the group. See Knowledge Bases.
Integrations
Two sections answer "what can this group reach?"
- Apps and tools, the shared connections an integration admin assigned to this group, each with its authentication type, its tools, and its connection status. A group admin can configure and connect one.
- Data sources, the Workspace data-source connections assigned to this group. Read-only here. A Workspace admin manages them from Integrations.
Permissions
People with direct access, teams nested into the group, and the role each holds. Everybody with access can read this tab. Only group admins and Workspace admins see the buttons that change it.
See Sharing and Access.
Settings
General renames the group and edits its description. Danger zone deletes it. Both are read-only unless you are a group admin, and the tab says so rather than showing controls that will not work.
Deleting a group is not just about people. It removes the group for everyone and archives the AI Employees and knowledge bases it owns. Members keep their Workspace access and every other group. Deleting is reversible by restoring the group, but treat it as a change to the resources, not only to the roster.
When you cannot open a group
A group page you have no access to reports "You don't have access to this group, or it doesn't exist." Ask a group admin or a Workspace admin to add you.
What's next
- Group-Owned AI Employees and Knowledge Bases for what ownership by a group means.
- Sharing and Access for inviting people and teams.
- Integrations in a Group for shared connections.
- Teams for managing people and nesting.