# Integrations

Find, connect, and disconnect every system that Risotto works with, from the Integrations catalog and each integration's page

The **Integrations** page lists every system that Risotto connects to, with its connection state. Go to **Settings > Integrations**. Only an Admin or a Manager sees this page.

*Product example: Settings, Integrations on the Overview tab: Slack, Microsoft Teams and Email under Request sources, and Confluence, Guru and Slack under Knowledge.*

## Find an integration

The page has three tabs:

- **Overview**: the integrations in groups: **Request sources**, **Knowledge**, **Identity**, **Device management**, **HRIS**, **Access governance**, **Ticketing**, and **Custom**. Each group shows only when it has an integration. An integration that has more than one use shows in each group. The **Request sources** group has a **Manage request sources** link, and the **Knowledge** group has a **Manage indexes** link.
- **All**: every integration, with a category filter.
- **Connected**: only the integrations that your organization connected. If there are none, the tab shows "No integrations found".

To show one category:

1. **Choose a category**

   Click **All categories** and choose a category, for example **HRIS**. The
   filter also has **Observability**, which is not a group on the **Overview**
   tab.

   *Product example: The Integrations All tab with the category menu open and HRIS highlighted.*

To find an integration by name, type in **Search integrations**. The search covers all integrations, whatever the tab or category, and shows the number of results.

Each card shows the name, a short description, and a status:

- **Connect**: the integration is not connected.
- **Connected**: the integration is connected.
- **Built in**: the integration needs no connection (for example, **Email**).

Some cards also show an **Experimental** badge. In a group, the status applies to that use only. For example, the **Slack** card shows **Connected** under **Request sources** when the Slack app is installed, and **Connect** under **Knowledge** until you index a Slack channel or connect Slack AI search.

## Open an integration page

Click a card to open the integration's page.

*Product example: The Integrations All tab filtered to HRIS: Workday connected, and HiBob, BambooHR and Rippling with Connect.*

The header shows the integration's name and status: **Connected**, **Not connected**, or **Built in**.

- If nothing is connected, the page shows each connection card with its button, for example **Connect**, **Install** (HiBob and Rippling), or **Install App** (Confluence). An integration whose indexes carry their own credentials also shows a row to start the first index, for example **Index a space** for Confluence.
- When the integration is connected, the page has tabs. The **Connections** tab is first. The other tabs depend on the integration: **Requests**, **Knowledge**, **Departments**, **Tools**, **Verification**, or **Access rules**.
- An integration that is built in, or whose indexes carry their own credentials, has no **Connections** tab. For example, **Email** opens on **Requests**, and **Notion** opens on **Knowledge** once it has an index.

If a tab needs a connection that is missing, the tab shows **Not connected**, with the card to connect it.

For the setup steps of each system, see [Integrations overview](https://www.tryrisotto.com/docs/integrations/overview) and the page of each integration.

## Connect an integration

1. **Open the integration's page**

   In **Settings > Integrations**, click the integration's card.

2. **Start the connection**

   On the connection's card, click **Connect** (or **Install**, or **Install
   App**).

   *Product example: BambooHR's integration page, Not connected, with Connect on the API access card.*

3. **Finish in the dialog or in the other system**

   Enter what the dialog asks for, or sign in to the other system and allow
   access. The steps depend on the integration: see its page in
   [Integrations](https://www.tryrisotto.com/docs/integrations/overview).

When the connection is made, the header shows **Connected** and the page shows its tabs.

## Manage a connection

On the **Connections** tab, each connected card shows a **Connected** button. If the connection has a problem, the button shows **Error** or **Disconnected** instead. Click the button to see the actions for that connection, for example **Configure...**, **Refresh**, or **Disconnect...**.

The card shows the facts of the connection, and a footer with when it was installed and, if known, who installed it.

### Disconnect an integration

1. **Open the connection's menu**

   On the **Connections** tab, click **Connected** on the card.

2. **Choose Disconnect**

   Click **Disconnect...**.

   *Product example: BambooHR's page once connected, with the API access card's Connected menu open on Disconnect....*

3. **Confirm**

   In the **Disconnect from \<integration>?** dialog, read what stops working,
   then click **Disconnect**. The message "Disconnected from \<integration>"
   appears.

   *Product example: The Disconnect from BambooHR? confirmation, with Disconnect.*

For HiBob, Risotto also opens the HiBob Marketplace, where you remove the app from HiBob.

## Add a custom integration

1. **Open the menu**

   In **Settings > Integrations**, click **New custom integration**.

2. **Choose the kind**

   Choose one:

   - **MCP server**: give agents the tools of a remote MCP server. See [External MCP Servers](https://www.tryrisotto.com/docs/integrations/tools/external-mcp-servers).
   - **API source**: turn an API definition into agent tools. See [Custom API Tools](https://www.tryrisotto.com/docs/integrations/tools/custom-api-tools).

Each server or source then has its own card in the **Custom** group. If you have none, the **Custom** category on the **All** tab shows "No custom integrations", with a **New custom integration** button.

> **Note:** The **Credential Vault** is its own item in the Settings menu. See [Credential
> Vault](https://www.tryrisotto.com/docs/dashboard/settings/credential-vault).

## Slack

Go to **Settings > Integrations** and click the **Slack** card. The **Chat app** card manages the Slack connection that receives requests and sends replies. To connect, click **Connect**, then choose **Marketplace app** or **Custom app...**. See [Slack App Setup](https://www.tryrisotto.com/docs/guides/initial/slack-app). The same page also has the **AI search** card (see [Slack AI search](https://www.tryrisotto.com/docs/dashboard/knowledge/connect)) and the **Tools app** card.

When the Slack app is connected, the **Chat app** card shows these rows:

- **Install type**: **Enterprise Grid (org-wide)** for an install across the whole Slack organization, or **Workspace** for an install in one workspace. A workspace that joins an Enterprise Grid organization keeps its **Workspace** install, which keeps working in that workspace. To reach every workspace of the organization, connect again for the whole organization. See [Enterprise Grid](https://www.tryrisotto.com/docs/guides/initial/slack-app#enterprise-grid)
- **Workspaces**: Each Slack workspace that the install reaches, with its icon. An org-wide install lists every workspace it was granted. If Risotto cannot read the list from Slack, the row shows **No workspaces**. Risotto keeps the list for 24 hours. After an admin grants or removes a workspace in Slack, click **Connected** and choose **Refresh** to read the list again now. Refresh does not disconnect the app or change the install type, and it is limited to 5 per minute for an Admin or Manager. On Enterprise Grid, each workspace opens in Slack admin, which only Slack org admins and owners can see. An org-wide install also shows a **Manage workspaces** link at the end of the row (or **Add workspace** when the row shows **No workspaces**). The link opens the app's installations page in Slack admin
- **Bot user**: Shows the Risotto bot user information. If you rename the bot in Slack, click **Connected** and choose **Refresh**. Refresh reads the bot from Slack again and updates its name on this card and in the messages Risotto sends, for example approval requests and synced comments. Until you refresh, the card and messages keep the old name. On a custom Slack app, messages show the name of the bot user, which is a different setting from the app's name. If the two names differ after a refresh, the row shows **App name mismatch**. Click the info icon to see both names and links to the Slack pages where you change the bot's name:

  - In the Slack app settings, set the name in **App Home**, then change the app's name under **Basic Information**. Slack applies the **App Home** name when you change the app's name.
  - Or open the workspace app page in Slack, click **Configure**, and edit the name at the bottom.

  Then click **Connected** and choose **Refresh** again. Some teams give the app and the bot different names on purpose, so the label is not an error.

The card also shows when the app was installed and who installed it. On a custom Slack app, the **Connected** menu also has **Update manifest...**. It shows the current Risotto manifest to copy into your app's **App Manifest** page in Slack.

When the Slack Tools app is connected, the **Tools app** card shows these rows:

- **Install type**: The same values as on the **Chat app** card
- **Workspace**: The Slack workspace of the install. On an org-wide install, the row is **Organization** and shows the name of the Slack organization. The row shows only when Slack gave Risotto the name
- **Bot user**: The bot user of the Tools app

The card footer shows when the Tools app was installed and who installed it. Risotto reads the bot user and the installer through the **Chat app**, so these show only when the Slack Chat app is connected.

> **Warning:** Each Risotto organization allows only one chat integration. If Microsoft Teams
> is connected, you cannot connect Slack, and the other way around.

For Microsoft Teams, see [Microsoft Teams App Setup](https://www.tryrisotto.com/docs/guides/teams/teams-app).

## Ticketing

Ticketing systems are in the **Ticketing** group: Airtable, Asana, Datadog, Freshservice, GitHub, Jira, Linear, ServiceNow, and Zendesk.

- **Jira**: click the **Jira** card. On the **Jira app** card, click **Connect** and follow the **Install Jira Forge App** dialog. See [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira).
- **Freshservice**: click the **Freshservice** card. On the **Freshservice API key** card, click **Connect**. See [Freshservice](https://www.tryrisotto.com/docs/integrations/ticketing/freshservice).

You set up [ticket sync for each department](https://www.tryrisotto.com/docs/dashboard/settings/departments) and [Jira projects as request sources](https://www.tryrisotto.com/docs/dashboard/settings/request-sources). On the Jira and Freshservice pages, the **Departments** tab lists the departments that sync tickets to that system, and the **Requests** tab holds its request sources.

## Knowledge

Knowledge sources are in the **Knowledge** group. Each one's page has a **Knowledge** tab with its indexes. Before anything is connected, the page shows a row to start the first index, for example **Index a space** for Confluence, **Index a project** for Jira, or **Share pages** for Notion. The **Manage indexes** link in the **Knowledge** group opens **Knowledge > Indexes**, which lists the indexes of every source and has its own **Create index** button (see [Create an index](https://www.tryrisotto.com/docs/dashboard/knowledge/indexes#create-an-index)).

Some knowledge sources also have a connection on their integration page:

- **Confluence**: the **Page updates** card reindexes a page when it changes in Confluence. If the app is not installed, click **Install App** on the card and follow the installation process in your Confluence instance. See [Confluence](https://www.tryrisotto.com/docs/integrations/knowledge/confluence).
- **Guru**: the **Card updates** card reindexes a card when it changes in Guru. Click **Connect** on the card. In the **Connect Guru** dialog, enter the **User Email** and the **User Token**, then click **Connect**. Risotto sets up the webhook in the same step. See [Guru](https://www.tryrisotto.com/docs/integrations/knowledge/guru).
- **OneNote**: the **Notebook access** card connects the Microsoft account that the OneNote index reads with. The **Knowledge** tab needs it. See [OneNote](https://www.tryrisotto.com/docs/integrations/knowledge/onenote).

## Identity, devices, and HR systems

Identity providers (Okta, Microsoft Entra ID, Google Workspace, JumpCloud), license servers (Zoom, JetBrains, Tableau), Opal, and device management platforms (Iru, Jamf, Microsoft Intune, Workspace ONE, Fleet) each have their own integration page. There is no separate **Identity**, **Devices**, or **People** connect page.

- Identity providers: see [Okta](https://www.tryrisotto.com/docs/integrations/idp/okta), [Microsoft Entra ID](https://www.tryrisotto.com/docs/integrations/idp/microsoft-entra), [Google Workspace](https://www.tryrisotto.com/docs/integrations/idp/google-workspace), and [JumpCloud](https://www.tryrisotto.com/docs/integrations/idp/jumpcloud). The Okta page also has a **Verification** tab.
- License servers are in the **Identity** group. Each license server's page has an **Access rules** tab. See [License servers](https://www.tryrisotto.com/docs/dashboard/applications/license-servers).
- Opal is in the **Access governance** group. See [Opal](https://www.tryrisotto.com/docs/integrations/access-governance/opal).
- Device management: see [Jamf Pro](https://www.tryrisotto.com/docs/integrations/device-management/jamf-pro), [Iru](https://www.tryrisotto.com/docs/integrations/device-management/iru), [Microsoft Intune](https://www.tryrisotto.com/docs/integrations/device-management/microsoft-intune), [Workspace ONE](https://www.tryrisotto.com/docs/integrations/device-management/workspace-one), and [Fleet](https://www.tryrisotto.com/docs/integrations/device-management/fleet).
- HR systems (Workday, HiBob, BambooHR, Rippling) are in the **HRIS** group. See [Workday](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/workday), [HiBob](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/hibob), [BambooHR](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/bamboohr), and [Rippling](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/rippling).

Source: https://www.tryrisotto.com/docs/dashboard/settings/integrations
