Getting Started Part 2: Connecting Your IDP & HR Integrations
Connecting Your IDP & HR Integrations
Published Date: May 1, 2026 | Last Updated: October 9, 2026
About: This article covers connecting an Identity Provider (IDP) and an HR system as the first 2 integrations in a new Seasoft Identity environment. The IDP connection is the required first step in setup — it imports Users and their organizational data, and everything that follows depends on it.
Why the IDP Comes First
Before any User can be provisioned, monitored, or assigned a Role Template, Seasoft Identity needs to know who those Users are. Connecting an IDP is how that happens. When an IDP integration is connected and synced, Seasoft Identity automatically:
- Imports Users — every account in the connected directory is discovered and added to Seasoft Identity.
- Pulls organizational data — department, job title, and other directory attributes are imported with each User record.
- Detects existing permissions — access already granted in the IDP surfaces in Seasoft Identity, giving the Administrator a complete picture before any changes are made.
This data is the foundation for verifying User records, connecting additional integrations, and building Role Templates. None of those steps can be completed accurately without it.
The Integrations Page
All integration management takes place on the Integrations page, accessible from the left navigation. The page lists every connected integration with its current status and last sync time. The following controls appear in the top right of the page:
| Control | Function |
|---|---|
| Schedule: OFF / ON | Configures the automatic sync schedule for all integrations. When enabled, the Administrator selects a sync frequency. When disabled, syncs run manually only. |
| Sync Now | Triggers an immediate sync across all connected integrations. |
| + Add Integration | Opens the Add Integration catalog to connect a new integration. |
Before You Begin
Confirm 2 things before connecting the IDP:
- Directory authorization. Connecting an IDP requires an account with organization-level authorization privileges in the target directory — for example, a Global Administrator in Microsoft Entra ID. If the Administrator does not hold this role, coordinate with the person who does. The connection cannot be completed without it.
- Directory attributes. Seasoft Identity imports User attributes from the IDP, such as Microsoft Entra ID, Active Directory, or another LDAP-based directory. Populate the job title and department for every User in the IDP first so those values sync to Seasoft Identity automatically.
Connecting an IDP Integration
The steps below use Microsoft Entra ID as the example. The fields and authorization steps differ for each IDP — refer to the relevant connection guide, such as Microsoft Entra ID, in the Integrations section of the knowledge base before proceeding.
Add the integration
- Navigate to Integrations in the left navigation.
- Select + Add Integration.
- Locate the IDP in the catalog. Use the Search integrations… field to filter by name if needed.
- Select Add next to the IDP.
Authorize the connection
- Enter the organization's Entra ID tenant domain in the Entra ID Tenant Domain field, in the format
contoso.onmicrosoft.comorcontoso.com. - Select Login to Microsoft Entra ID. Seasoft Identity redirects to Microsoft for authorization.
- Sign in with a Global Administrator account.
- When Microsoft Entra ID requests permissions for the application, select the option to consent on behalf of the organization, then select Accept.
- Seasoft Identity redirects back to the Integrations page and displays a
Connection Establishedmessage. Optionally, select the pencil icon to give the integration a friendly name. - Select Done. Seasoft Identity begins syncing User data from the IDP.
Assigning a Friendly Name
Seasoft Identity assigns a default name to each integration on connection. A friendly name makes the integration easier to identify in lists and reports, particularly when multiple instances of the same application are connected. An integration can be renamed at any time:
- Select the integration row on the Integrations page to open the IAM Connection panel.
- Select Configure.
- Edit the name in the Name field.
- Select Save.
When more than 1 instance of the same application is connected — for example, a production and a development environment — assign each a distinct friendly name, such as HubSpot – Prod and HubSpot – Dev.
Configuring the Sync Schedule
The sync schedule is off by default. Enabling it keeps User data and detected permissions current without manual intervention.
- Select Schedule: OFF on the Integrations page.
- Toggle Enable auto-sync on.
- Select a frequency from the Frequency dropdown: Every 30 minutes, Every hour, Every 6 hours, Every 12 hours, or Daily.
- Close the schedule panel. The control updates to Schedule: ON.
To sync immediately, select Sync Now on the Integrations page to sync all integrations, or open the IAM Connection panel for a single integration and select Sync Now there.
Drift Detection
Drift is a permission change made in a connected application outside of Seasoft Identity. During integration setup, the Administrator chooses how Seasoft Identity handles drift for that integration. The setting applies per integration:
- Flag any user and/or permission discrepancies for manual review (default) — Seasoft Identity tracks access changes made outside the platform. When a permission changes in a connected system without a corresponding action in Seasoft Identity, the change is flagged as drift for the Administrator to review.
- Ignore anomalies, and update Seasoft Identity to match actual permissions — Seasoft Identity accepts the permissions in the integration as they are and updates its own records to match. This works as a learning mode when Seasoft Identity should adopt the permissions currently in a system rather than flag them.
Drift detection is active as soon as an integration is connected unless it is turned off. Drift notifications are routed to Team managers, which are configured in Getting Started Part 7.
Verifying the Connection
After the first sync completes, open the integration's IAM Connection panel and confirm the following:
- Status displays
Active. - Sync Status displays
Synced, along with the time of the most recent sync. - Users discovered matches the expected number of Users in the connected directory.
Then navigate to Users in the left navigation and confirm that User records are present. Detailed verification of User data is covered in Getting Started Part 3.
Connecting an HR System
Connecting an HR system is recommended but not required to proceed. The HR system enriches User records with organizational data that may not be available from the directory alone — such as reporting structure and employment status.
The process is the same as for any other integration: locate the HR system in the Add Integration catalog, select Add, and complete the authorization flow for that application. Each HR system has its own connection requirements — refer to the relevant connection guide, such as BambooHR, before proceeding.
Next Steps
This article is Part 2 of the Getting Started with Seasoft Identity series.
Next: Getting Started Part 3: Managing User Permissions
Previous: Getting Started Part 1: Platform Overview
Getting Started series
- Platform Overview
- Connecting Your IDP & HR Integrations (current)
- Managing User Permissions
- Connecting Additional Integrations
- Planning Your Role Template Structure
- Configuring Role Templates
- Configuring Teams
- Monitoring Access