Skip to content
English - United States
  • There are no suggestions because the search field is empty.

Getting Started Part 4: Connecting Additional Integrations

Connecting Additional Integrations

Published Date: May 1, 2026 | Last Updated: October 9, 2026

About: This article covers connecting SaaS applications and other integrations after the IDP is in place. By the end, the Administrator will have all target applications connected, verified, and syncing into Seasoft Identity.

Why additional integrations come after the IDP and HR system

The IDP and HR integrations connected in Part 2 established the User directory — the people Seasoft Identity manages. Additional integrations are the applications those Users will be provisioned into. Connecting them now, before Role Templates are configured, ensures that when User records are reviewed in the next step, they reflect the complete picture of every permission each User holds across every connected system. That complete picture is what makes Role Template design accurate in Part 5.

Important: Connect all integrations before designing Role Templates. If an integration is missing at the time a Role Template is built, the template will not include that application — and any permissions copied from a User's detected access will be incomplete.

Integration types

Seasoft Identity supports 2 primary integration connection methods. The method required depends on the application being connected:

  • OAuth — the Administrator authorizes Seasoft Identity to connect by signing in to the target application and granting permissions. No API key is required. Microsoft Entra ID, Microsoft 365, and Google Workspace are examples of OAuth integrations.
  • API key / credentials — the Administrator provides an API key or service account credentials generated in the target application. HubSpot and Slack are examples of API-based integrations.

The connection method and specific requirements for each integration are documented in the Integrations reference library. Refer to the relevant guide before beginning each connection.

Connect each additional integration

The Add Integration flow is the same process used in Part 2. For each integration:

  1. Navigate to Integrations in the left navigation.
  2. Select + Add Integration.
  3. Locate the application in the catalog and select it.
  4. Follow the on-screen setup steps. Refer to the corresponding integration guide for credentials and configuration details specific to that application.
  5. Complete the setup. Seasoft Identity begins an initial sync with the connected application.

Repeat this process until all applications the organization uses are connected. The goal is to have every system Seasoft Identity will manage represented before proceeding to Part 5.

Verify each connection

After connecting each integration, confirm it is active and syncing before moving to the next.

On the Integrations page, each connected application displays a current status and the timestamp of its most recent sync. A status of Active indicates the integration is connected and syncing correctly. If a newly connected integration does not show as Active, select Sync Now to trigger a manual sync. If the status does not update to Active, review the integration's authorization settings and consult the corresponding integration guide.

Review detected permissions

Once all integrations are connected and syncing, User records on the Users page update to reflect detected permissions across every connected application. The Access column displays icons for all applications each User has been detected in.

Review a sample of User records and confirm that detected permissions are appearing as expected across the newly connected integrations. If a User's access in a specific application does not appear, confirm that the sync completed and that the User's account exists in that application.

With all integrations connected, each User record now reflects a complete view of that User's existing access across every system Seasoft Identity manages. This is the data used to design Role Templates in Part 5.

Confirmation

The Administrator is ready to proceed when all of the following are true:

  • All target applications are connected and display a status of Active on the Integrations page
  • Each connected integration shows a recent successful sync timestamp
  • Detected permissions across all integrations are visible on User records in the Users page

Next Steps

This article is Part 4 of the Getting Started with Seasoft Identity series.

Next: Getting Started Part 5: Planning Your Role Template Structure

Previous: Getting Started Part 3: Managing User Permissions

Getting Started series

  1. Platform Overview
  2. Connecting Your IDP & HR Integrations
  3. Managing User Permissions
  4. Connecting Additional Integrations (current)
  5. Planning Your Role Template Structure
  6. Configuring Role Templates
  7. Configuring Teams
  8. Monitoring Access