Skip to main content
Sign in

Creating an extended user integration for Ironclad App

  • May 28, 2026 16:17
  • Updated

Create an integration to sync Ironclad App with Oomnitza to gain visibility of user data.

Before you start

To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application. 

small_blue_link.svg Creating integration users 

You need the following information to create credentials in Oomnitza and to connect to the vendor application's API:

  • Client ID and client secret
  • Scope. The following values for scope are automatically added when you create the integration: scim.users.readUsers scim.users.createUsers scim.users.updateUsers scim.users.deleteUsers. The provided scopes are required for the presets to work

small_blue_link.svg Retrieve Oauth 2.0 credentials from Ironclad

small_blue_link.svg Adding credentials to Oomnitza

Adding your credentials

By default authorization code is used but both auth code and grant are supported.

  1. Click Configuration > Security > Credentials.
  2. Click Add new credential.
  3. Search for Ironclad.
  4. Click the arrow next to Ironclad App.
  5. Enter your client ID, and client secret. The scope values are populated by Oomnitza..
  6. Save your credentials.

Creating the integration

  1. In Oomnitza, click Configuration > Integrations > Overview.
  2. Click Block view block_view.PNG.
  3. On the Integrations page, scroll down to the Extended section for user integrations.
  4. Click NEW INTEGRATION.
  5. In the sidebar, search for the integration.
  6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

  • User only. Add user records.
  • User plus SaaS user. User records and SaaS user records are retrieved. User records are displayed on the People page and SaaS user records can be accessed when you open the SaaS application record on the SaaS page and click the Users tab. In addition to retrieving information about the SaaS application such as usernames, you also retrieve key information such as the user's SaaS role and last activity which will enable you to reduce costs by monitoring SaaS usage and removing users who aren't using the SaaS application. To maintain data hygiene, you can enable the deactivate feature.
  • Software SaaS Selection. Link the vendor application to the Oomnitza Software Catalog which is a repository of supported vendor applications and services. If an entry for the vendor application is not shown in the list, it means that the vendor application has not been added to the SaaS page in Oomnitza and linked to the catalog. See SaaS details overview. You can ignore this field because the vendor application is automatically linked to the catalog when the integration is saved.

Important
Now that user information can be retrieved and users deactivated when the integration is run, you can deactivate or remove the workflows that were added to retrieve SaaS user information and deactivate SaaS users. (The block that is used to complete these actions in workflows is the SaaS User Role Retrieval block.)

When you enable the Deactivate feature, the following actions are completed when the integration runs:

  • If a user record is missing from the data source - the vendor application - or if the record is marked as inactive in the data source, the user record is deactivated in Oomnitza.
  • If a user record was deactivated and is now available in the data source, for example, the user logs into the SaaS application, the user record becomes active in Oomnitza. 

Installation types

  • Cloud. Store credentials in the Oomnitza cloud.
  • Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAuth authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication. 

Integration preferences

  • Create & Update. Add and update records.
  • Create only. Add records.
  • Update only. Update records.

Editing the integration details

TipBulb_Icon_small.svg When you edit the Integration details section, you can select the name or names of integration contacts.  Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.

  1. Click Edit edit_black_pencil_icon.svg.
  2. Make your changes.

Editing the credential details

If you selected Cloud as the installation type, choose one of the following options:

  • Select the credentials that were created for the integration.
  • Edit the credentials that were created for the integration.
  • Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

  1. Click Edit edit_black_pencil_icon.svg.
  2. Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit edit_black_pencil_icon.svg.

 cog_red_dot_small_icon.svg Select Edit integration to add rules for syncing data. small_blue_link.svg Filtering integration results.  
 

You can add new fields to your integration by selecting Add new field  add_grey_rectangel_icon.svg on the mapping page. 
small_blue_link.svg Creating custom API fields. 

Custom mappings

Connect: Credentials
Connector Sync Time
Email
Family Name
Given Name
Name
Time Zone
Title
User Id
Username
Username in 0365
Verified
Verified Time

Tracking information

When the integration is run, you can track the name of the credentials that were used and the sync time. To do this, you map the following fields to Oomnitza:   

  • Connect: Credentials
  • Connector: Sync Time

To do this, you map the fields to custom Oomnitza fields. 

Mapping fields to Oomnitza

  1. Right-click the field, and select Add new Oomnitza field.
  2. Change the name of the field.
  3. Save your changes.

 

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration. 

small_blue_link.svg If you selected Cloud as the installation type when creating the integration, see Running an extended integration

small_blue_link.svg If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab. 

Related Links

Do you know
When Oomnitza syncs with the 3rd party vendor's API, it automatically retrieves user role information. And, you also have the option —if you select Deactivate when you create or edit the integration —  to automatically deactivate missing or inactive user records. This means that you don't have to create workflows that use the SaaS User Role retrieval block to get user role information or deactivate users! 

Related articles

Comments

0 comments

Please sign in to leave a comment.