Addigy supports connecting multiple Identity Providers (IdPs) to End User Management, allowing you to sync users from different organizations and IdPs into a single Addigy tenant.
- Multi-Org User Sync – Connect separate IdPs for each client organization and sync all users into Addigy
- Filtered Views – Filter the End Users list by connection to quickly find users from a specific organization
- Independent Credentials – Each connection generates its own SCIM URL and Bearer Token, keeping client environments isolated
How It Works
- Open the Connections panel from the End Users page
- Add a new connection to generate a unique SCIM URL and Bearer Token
- Name the connection to identify the client and IdP
- Configure SCIM provisioning in the IdP using the generated credentials
- Users sync into Addigy and appear under the corresponding connection
- Filter the End Users list by connection to view users from a specific organization
Before You Begin
- Existing End User Management Setup: You must have End User Management enabled for your Addigy organization. If you haven't set it up yet, see End User Management.
- IdP Admin Access: Admin access to each Identity Provider you plan to connect (e.g., Okta, Microsoft Entra ID).
- IdP SCIM Support: Your IdP must support SCIM provisioning. Currently supported providers include Okta and Microsoft Entra ID.
Step 1: Open the Connections Panel
Purpose: Access the connection management interface to add a new IdP connection.
- Log in to Addigy as an administrator.
- Navigate to End Users from the left-hand navigation.
- Click the Connections button in the top-right corner of the page.
Note: If you have not yet connected any IdP, you will see the initial setup flow instead. Complete your first IdP connection using the standard setup process — see Integrating Okta via SCIM or Integrating Entra ID via SCIM. Once your first connection is active, the Connections button will appear for adding additional IdPs.
Step 2: Add a New Connection
Purpose: Generate a unique set of SCIM credentials for the new IdP connection.
- In the Connections panel, click Add Connection.
- You will be presented with:
-
SCIM URL — The endpoint for this connection (e.g.,
https://***.addigy.com/scim/v2) - SCIM Token — A Bearer Token for authenticating SCIM requests
- Connection Name — An editable name field (pre-filled with a default)
-
SCIM URL — The endpoint for this connection (e.g.,
- Edit the Connection Name to clearly identify the client and IdP.
Naming Best Practices
Use a naming convention that includes the client/organization name and the IdP type:
| Example Name | Use Case |
|---|---|
| Company A - Okta | Client "Company A" using Okta |
| Company B - Entra | Client "Company B" using Microsoft Entra ID |
| Acme Corp - Okta | Client "Acme Corp" using Okta |
This makes it easy to identify connections at a glance, especially when managing many client organizations.
- Copy the SCIM URL and SCIM Token and store them securely.
⚠️ Security Note: Each connection generates its own unique credentials. Treat each Bearer Token like a password — do not share it publicly or commit it to version control. If a token is compromised, regenerate it immediately.
Step 3: Configure SCIM in Your Identity Provider
Purpose: Set up SCIM provisioning in the IdP using the credentials from Step 2.
Follow the setup guide for your Identity Provider, using the SCIM URL and Token generated in Step 2:
- Okta — See Integrating Okta via SCIM
- Microsoft Entra ID — See Integrating Entra ID via SCIM
Step 4: Verify Users and Filter by Connection
Purpose: Confirm that users are syncing correctly and learn how to filter the user list by connection.
- Wait 5–10 minutes after completing the IdP configuration for the initial sync to complete.
- Navigate to End Users from the left-hand navigation.
- Verify that users from the newly connected IdP appear in the End Users list.
- Use the Connections dropdown to filter the user list by a specific connection.
- Select a connection name to view only users from that organization
- This is useful for quickly locating users when managing multiple client environments
Managing Connections
You can edit or delete existing connections at any time.
Editing a Connection
- Navigate to End Users → Connections.
- Locate the connection you want to modify.
- Edit the connection name or other details as needed.
- Save your changes.
Deleting a Connection
- Navigate to End Users → Connections.
- Locate the connection you want to remove.
- Delete the connection.
⚠️ Warning: Deleting a connection will stop syncing users from that IdP. Review the impact on device assignments and policies before removing a connection.
Adding More Connections
There is no limit to the number of IdP connections you can add. To connect additional IdPs, repeat Steps 1–4 for each new organization or IdP.
Notes
- Each connection generates its own unique SCIM URL and Bearer Token — credentials are not shared across connections.
- Users from different connections appear together in the End Users list but can be filtered by connection.
- All End User features — device assignment, user attributes in MDM profiles, Flex policy conditions — work the same regardless of which connection a user was synced from.