# Creating a synchronization configuration for the source

Most organizations have a mix of applications. Some integrate through connectors, and others do not. For applications with connector support, review the [connector documentation](/application-onboarding/connectors.md). For applications without connector support, you can import entitlements using a CSV file. OpenIAM provides out-of-the-box templates to simplify this process.

## Loading an application list

{% stepper %}
{% step %}

### Create an application list CSV

The first step in uploading unintegrated applications to OpenIAM is to create an application list. To do this, use a CSV file with the format described below.

| Column name                          | Description                                                                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| MANAGED\_SYSTEM\_NAME                | Name as it will be defined in OpenIAM.                                                                                          |
| DESCRIPTION                          | User-friendly description of this application or service.                                                                       |
| IS\_MANUAL                           | Y - if a connector does not exist. N - if a connector does exist.                                                               |
| IS\_ACTIVE                           | Y - Configuration is available for use. N - configuration disabled and no tasks will be processed for this application.         |
| IS\_VISIBLE                          | Y - Application is visible in the catalog. N - application is not visible in the catalog.                                       |
| PARTICIPATE\_IN\_ACCESSCERTIFICATION | Y - Application is available for use in access certification. N - application is not available for use in access certification. |
| CONNECTOR\_NAME                      | Name of the OpenIAM connector which will be used with this configuration.                                                       |
| URL                                  | URL of the application, service, or tenant.                                                                                     |
| PORT                                 | Port this application is listening on.                                                                                          |
| CATEGORY\_NAME                       | Category under which the application should be listed in the service catalog.                                                   |
| PERMISSIONS\_LIST                    | Permissions which will be used with this application. Example: READ, WRITE, EXECUTE. These can be unique to this application.   |
| APPLICATION\_OWNER\_TYPE             | Type of application owner: User or Group.                                                                                       |
| APPLICATION\_OWNER                   | Name of the application owner.                                                                                                  |
| APPLICATION\_ADMIN\_TYPE             | Type of application admin: User or Group.                                                                                       |
| APPLICATION\_ADMIN                   | Name of the application admin.                                                                                                  |
| APPROVER1\_TYPE                      | Type of first approver: Supervisor, application owner, application admin, entitlement owner, specific user or group.            |
| APPROVER1                            | Name of the first approver (user name or group name).                                                                           |
| APPROVER2\_TYPE                      | Type of second approver: Supervisor, application owner, application admin, entitlement owner, specific user or group.           |
| APPROVER2                            | Name of the second approver (user name or group name).                                                                          |
| APPROVER3\_TYPE                      | Type of third approver: Supervisor, application owner, application admin, entitlement owner, specific user or group.            |
| APPROVER3                            | Name of the third approver (user name or group name).                                                                           |

Example:

{% code overflow="wrap" fullWidth="true" expandable="true" %}

```csv
MANAGED_SYSTEM_NAME,DESCRIPTION,IS_MANUAL,IS_ACTIVE,IS_VISIBLE,PARTICIPATE_IN_ACCESSCERTIFICATION,CONNECTOR_NAME,URL,PORT,CATEGORY_NAME,PERMISSIONS_LIST,APPLICATION_OWNER_TYPE,APPLICATION_OWNER,APPLICATION_ADMIN_TYPE,APPLICATION_ADMIN,APPROVER1_TYPE,APPROVER1,APPROVER2_TYPE,APPROVER2,APPROVER3_TYPE,APPROVER3
Adobe Creative Cloud,,Y,Y,Y,,,,,Enterprise Applications,,,,GROUP,IT_HelpDesk,SUPERVISOR,Reports To,GROUP,Information_Security,,
Salesforce,,Y,Y,Y,,,,,Sales,,,,GROUP,IT_HelpDesk,SUPERVISOR,Reports To,GROUP,Information_Security,,
```

{% endcode %}
{% endstep %}
{% endstepper %}

## Process example

To import organizational data from a CSV file, go to **Webconsole** → **Provisioning** → **Synchronization**. This page lists the available synchronization options.

To import roles, search for and select the **CSV USER Entitlements Sync Example** template. The import process is controlled by a built-in script set in the **Transformation rule** field.

This transformation script imports user entitlements into OpenIAM by populating the corresponding fields. The **CSV file must match the structure defined in the transformation script for the entitlement type**.

The required structure of the CSV file for entitlements is described in the table below.

| Column name       | Description                  |
| ----------------- | ---------------------------- |
| APPLICATION       | The application to import.   |
| TYPE              | The metadata type to import. |
| ENTITLEMENT\_NAME | The entitlement to import.   |
| GROUP             | The group to import.         |
| ROLE              | The role to import.          |

Each entitlement type can also be uploaded separately through the **Synchronization** option. For more details, see [Application onboarding](/application-onboarding.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-beta.openiam.com/automated-user-provisioning/creating-a-synchronization-configuration-for-the-source.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.