Integrations in a Group
The Integrations tab of a group answers one question: what can this group reach? It has two sections, and they are managed by different people.
- Apps and tools, the shared connections assigned to this group, which a group admin configures and connects.
- Knowledge Bases, the Workspace Knowledge Base connections assigned to this group, which only a Workspace admin changes.
Apps and tools
Each row is a shared connection a Workspace or integration admin has assigned to this group, with four columns:
| Column | What it tells you |
|---|---|
| Integration | The service, for example Jira or Salesforce |
| Auth | How it authenticates: OAuth 2.0, API key, Basic auth, No auth, or Ema Platform Tool |
| Tools | Which tools the group may call, either All tools or a count |
| Status | Connected, Per-user connections, Not connected, or Error |
Nothing appears here until an admin assigns it. An empty tab reads "No shared connections yet", and the fix is to ask an integration admin to assign one, not to create one here.
Connecting one
A group admin selects Connect on a row that is not yet connected. The flow that opens depends on the integration's authentication scheme: OAuth integrations launch the OAuth consent flow, while credential-based integrations open a dialog to fill in authentication fields. Both complete the connection in one step.
For a row that is already connected, a group admin can select Disconnect to remove the connection, or Configure to update its settings.
If a connection attempt was started but never completed (for example, an OAuth flow that was abandoned), the row shows an Incomplete status. Selecting Remove on that row opens a confirmation dialog ("Remove this incomplete connection?") and removes the incomplete attempt. Nothing was connected yet, so no tools are affected. You can start again with Connect at any time.
The tool list is read-only. Which tools a group may call is set by the integration admin who assigned the connection, and it is not a group-level decision.
Saved credentials are never shown again. To change them, choose Replace details and enter all of them again. There is no partial edit of a stored credential.
Shared and per-user connections
A shared connection authenticates once for the whole group. Everybody in the group calls the tools through the same credential, which suits a service account.
A per-user connection asks each person to connect their own account. Status shows Per-user connections for these. Use them where the tool must act as the individual, for example reading somebody's own mailbox.
The credential a tool call uses is always bound explicitly to one connection. There is no fallback and no guessing between a shared and a per-user connection.
Revoking an assignment disables what was built on it. If an admin removes this group's assignment, the connections created from it stop working. The rows are not deleted, so restoring the assignment restores them.
Trial workspaces
In trial workspaces, HCM integration templates are seeded automatically for every personal group. Members invited to the workspace are provisioned with access to those seeded integrations. An operator can re-seed the group integrations at any time if the initial seeding needs to be repeated.
Knowledge Bases
The Workspace Knowledge Base connections assigned to this group, listed read-only with the source, its type, and its visibility: Shared, Private, or Private · you.
The knowledge bases in this group can use everything listed here. A Workspace admin connects and assigns Knowledge Bases from Integrations, and Manage data sources links there.
An empty section means no Knowledge Base has been assigned yet. Ask a Workspace admin.
What's next
- Integrations Hub for connecting and assigning at Workspace level.
- Data Connectors for the source types available.
- Group-Owned AI Employees and Knowledge Bases for the knowledge bases that consume these sources.