> Source: https://builder.ema.ai/v2/groups/group-integrations
> Title: Integrations in a Group

# 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.
-   **Data sources**, the Workspace data-source 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**, or **Configure** on a connection that already exists, which opens a dialog to name the connection, fill in its authentication fields, and connect in one step.

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.

> [INFO]
> **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.

> [WARNING]
> **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.

## Data sources

The Workspace data-source 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 data sources from Integrations, and **Manage data sources** links there.

An empty section means no data source has been assigned yet. Ask a Workspace admin.

## What's next

-   [Integrations Hub](/builder/v2/integrations-data/integrations-hub) for connecting and assigning at Workspace level.
-   [Data Connectors](/builder/v2/integrations-data/data-connectors) for the source types available.
-   [Group-Owned AI Employees and Knowledge Bases](/builder/v2/groups/group-owned-resources) for the knowledge bases that consume these sources.