# Integrations Overview

Learn which integrations are core to Risotto, when to connect external ticketing, and how runbook tools act on your systems

Risotto connects to the tools your organization already uses. Six integration categories are core: connect them to let Risotto answer and act on most employee requests.

> **Note:** Chat is the only integration you must connect before you start. Connect the
> other core integrations as early as you can, because each one adds requests
> that Risotto can resolve without a person.

## Core integrations

- [Chat](https://www.tryrisotto.com/docs/guides/initial/slack-app): Where employees ask for help and get answers
- [Knowledge Bases](https://www.tryrisotto.com/docs/integrations/knowledge/confluence): The documentation Risotto uses to answer questions
- [Identity Providers](https://www.tryrisotto.com/docs/integrations/idp/okta): Group membership, access grants, and account resets
- [Device Management](https://www.tryrisotto.com/docs/integrations/device-management/jamf-pro): Device details and device actions
- [HRIS](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/workday): Employee details, time off, and HR events
- [Access Governance](https://www.tryrisotto.com/docs/integrations/access-governance/overview): Access requests sent to your approval and fulfillment platform

## Other integrations

- [External Ticketing (optional)](https://www.tryrisotto.com/docs/integrations/ticketing/overview): Sync Risotto tickets to the ticketing system your team works in
- [Runbook Tools](https://www.tryrisotto.com/docs/integrations/tools/slack/create_channel): Run automated actions in your systems

---

## Chat

Chat is the front door to Risotto. Employees ask questions and make requests in Slack or Microsoft Teams, and Risotto replies in the same conversation.

**Supported**: [Slack](https://www.tryrisotto.com/docs/guides/initial/slack-app) and [Microsoft Teams](https://www.tryrisotto.com/docs/guides/teams/teams-app).

---

## Knowledge Bases

Knowledge base integrations give Risotto the documentation it uses to answer questions. The quality of the answers depends on these sources, so index current documents and remove old ones.

**How it works**: Risotto indexes content from your documentation platforms. When an employee asks a question, Risotto searches all connected sources and answers in plain language.

**Primary benefits**:

- One search across many platforms
- Answers to questions in natural language
- Permission-aware results
- Automated knowledge discovery

**Supported**: [Confluence](https://www.tryrisotto.com/docs/integrations/knowledge/confluence), [Notion](https://www.tryrisotto.com/docs/integrations/knowledge/notion), [Google Drive](https://www.tryrisotto.com/docs/integrations/knowledge/google-drive), [SharePoint](https://www.tryrisotto.com/docs/integrations/knowledge/sharepoint), and the other sources in the **Knowledge Bases** section.

---

## Identity Providers

Identity Provider (IdP) integrations connect Risotto to your organization's source of truth for users and group memberships. Risotto uses this data to make access decisions based on your existing groups.

**How it works**: Risotto queries your IdP to check group memberships and permissions. When access is granted, Risotto updates group memberships directly in your IdP.

**Core functions**:

- Check group memberships for access rules
- Manage group assignments for provisioning
- Import applications and their associated groups
- Sync user attributes and profiles

**Supported**: [Okta](https://www.tryrisotto.com/docs/integrations/idp/okta), [Google Workspace](https://www.tryrisotto.com/docs/integrations/idp/google-workspace), [Microsoft Entra ID](https://www.tryrisotto.com/docs/integrations/idp/microsoft-entra), and [JumpCloud](https://www.tryrisotto.com/docs/integrations/idp/jumpcloud).

---

## Device Management

Device management integrations connect Risotto to your MDM platform. Risotto uses them to answer device questions and to run device actions in a request.

**How it works**: Risotto finds the requestor's device in your MDM platform and reads its details. Depending on the platform and the permissions you grant, Risotto can also lock a device or get a recovery key.

**Supported**: [Jamf Pro](https://www.tryrisotto.com/docs/integrations/device-management/jamf-pro), [Iru (formerly Kandji)](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). SimpleMDM is available as [runbook tools](https://www.tryrisotto.com/docs/integrations/tools/simplemdm/find_user_device).

---

## HRIS

HRIS integrations connect Risotto to your HR system. Risotto uses them for employee self-service and to start automations when HR data changes.

**How it works**: Risotto looks up employee information, such as time off balances, in your HR system. To check balances, request time off or look up a home address, start a runbook from the HR templates in **Runbooks > Templates** (see [Runbooks](https://www.tryrisotto.com/docs/dashboard/runbooks#create-a-runbook)). Events from Rippling, BambooHR, and HiBob, such as a new hire or a departure, can start an [automation](https://www.tryrisotto.com/docs/dashboard/automations#rippling-triggers).

**Supported**: [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).

---

## Access Governance

Access governance integrations let Risotto send an access request to an external **approval and fulfillment** platform, instead of granting the access directly. This is different from an Identity Provider. An IdP is *directory sync and group membership*. Access governance is *delegated approval and fulfillment*.

**How it works**: A user requests access in chat. Risotto collects the fields the provider requires, then submits the request to the governance platform for the user. Approval and the grant happen in that platform, which stays the system of record. Risotto shows the result in the chat conversation.

**Why it matters**: You can use Okta for identity *and* Opal for fulfillment at the same time. See the [Access Governance Overview](https://www.tryrisotto.com/docs/integrations/access-governance/overview) to choose a provider.

**Supported**: [Opal](https://www.tryrisotto.com/docs/integrations/access-governance/opal) and [Okta Identity Governance](https://www.tryrisotto.com/docs/integrations/access-governance/okta-identity-governance).

---

## External Ticketing (optional)

Risotto has its own [tickets](https://www.tryrisotto.com/docs/dashboard/tickets/all), so you do not need an external ticketing system. Connect one if your team already works in an external ticketing platform and wants to keep it as the system of record.

**How it works**: When users make requests through chat (Slack or Microsoft Teams) or the dashboard, Risotto syncs them to your ticketing system. Updates in either system show in both.

**Key capabilities**:

- Automatic ticket creation from chat conversations
- Two-way status sync
- Comment and resolution tracking
- Reports across both platforms

**Supported**: Jira, Freshservice, ServiceNow, Zendesk, Linear, Airtable, Asana, GitHub, and email. See the [Ticketing Integrations Overview](https://www.tryrisotto.com/docs/integrations/ticketing/overview) for the sync type of each system.

---

## Runbook Tools

Runbook tools are automated actions that Risotto runs as part of a workflow. When a request starts a workflow, these tools do specific tasks, such as create resources, send notifications, or configure services.

**How it works**: When a workflow starts, Risotto runs the configured runbook tools in sequence. The tools act for the requestor without manual work.

**Example use cases**:

- Create communication channels for new projects
- Generate and send access credentials
- Configure user environments based on role

---

## How integrations work together

1. **User makes a request**

   A user asks for help or access through chat or the dashboard.

2. **Permission check**

   The **Identity Provider** integration checks the user's current group
   memberships and permissions.

3. **Knowledge search**

   The **Knowledge Base** integration finds relevant information or policies.

4. **Action**

   **Device management**, **HRIS**, **access governance**, and **runbook tools**
   do the work that the request needs.

5. **Ticket tracking**

   Risotto records the request as a ticket. If you connect **external
   ticketing**, Risotto also syncs the ticket to your ticketing system.

## Getting started

Connect the integrations in this order:

1. **Chat**: required before you start.
2. **Knowledge bases**: so Risotto can answer questions from your documentation.
3. **Identity provider**: so Risotto can handle access requests and account resets.
4. **Device management**, **HRIS**, and **access governance**: for each system your organization uses.
5. **External ticketing**: only if your team works in an external ticketing platform.

See [Pre Work](https://www.tryrisotto.com/docs/guides/initial/pre-work) for the admin access each integration needs.

Source: https://www.tryrisotto.com/docs/integrations/overview
