Organization Administration > Organizations > Organization settings
  

Organization settings

You can configure general properties for your organization and view organization history on the Organization Settings page.
To access the Organization page, in Administrator, select Organization.
The following image shows the Organization Settings page:
The Organization page displays details about the organization that include the name and address properties, authentication properties, and Data Integration service properties.
The general properties include the following information:
Overview information
The following table describes the overview properties:
Property
Description
Name
Name of the organization.
If you change the organization name, the new name appears on the Organization menu after you log out and log back in.
ID
ID assigned to your organization when it was created. You cannot change an organization ID.
Environment Type
Environment type for the organization, either Development, Production, QA, or Sandbox.
When you create your organization by starting your free trial, the environment type is Production.
There is no difference in functionality among the environment types.
Important: Validate the value periodically to ensure it matches your organization's deployment environment. If the value is incorrect and you are unable to change it, contact Global Customer Support.
Description
Optional description of the organization.
Number of Employees
Number of employees in the organization.
Address information
Use the address properties to specify the street address, zip code, state, and country of the organization.
History information
The organization history information displays the date and time that the organization was created, the user who created the organization, the date and time that the organization was last updated, and the user who last updated the organization. IDMC updates the history information when you make changes to the organization.

Organization general properties

You can configure general properties for your organization. General properties include information such as the organization name, ID, description, address, and number of employees. History information for the organization is also displayed in the general properties.
The general properties include the following information:
Overview information
The following table describes the overview properties:
Property
Description
Name
Name of the organization.
If you change the organization name, the new name appears on the Organization menu after you log out and log back in.
ID
ID assigned to your organization when it was created. You cannot change an organization ID.
Environment Type
Environment type for the organization, either Development, Production, QA, or Sandbox.
When you create your organization by starting your free trial, the environment type is Production.
There is no difference in functionality among the environment types.
Important: Validate the value periodically to ensure it matches your organization's deployment environment. If the value is incorrect and you are unable to change it, contact Global Customer Support.
Description
Optional description of the organization.
Number of Employees
Number of employees in the organization.
Address information
Use the address properties to specify the street address, zip code, state, and country of the organization.
History information
The organization history information displays the date and time that the organization was created, the user who created the organization, the date and time that the organization was last updated, and the user who last updated the organization. IDMC updates the history information when you make changes to the organization.

Authentication properties

You can configure authentication properties for your organization. Authentication properties control password restrictions and IP address filtering.
Password restrictions are enforced when users create or change their passwords. If you change the password expiration date from "never" to a number of days, then users with passwords that are older than the number of days will be required to change their passwords the next time that they log in to IDMC.
The following table describes the authentication properties:
Property
Description
Minimum Password Length
Minimum password length required for a valid password. Must be a number between 4 and 12 characters.
Minimum Character Mix
Minimum number of character types required for a valid password.
Passwords can contain a mix of the following character sets:
  • - Lowercase alphabetic characters
  • - Uppercase alphabetic characters
  • - Numeric characters
  • - Special characters
For example, if you set Minimum Character Mix to 1, then passwords must contain at least one of the character sets. If you set Minimum Character Mix to 2, then passwords must contain at least two of the character sets.
Password Reuse
Controls whether users can reuse passwords.
Password Expires
Determines how often users must reset their passwords.
Enable Multi-Factor Authentication
Enables multi-factor authentication for native human users.
When multi-factor authentication is enabled, native human users receive a verification code through email when they log in to the user interface. The email address for each human user must be valid.
Categorize users as human or non-human users on the Users page. For more information, see User Administration.
Session Idle Timeout
Amount of time before a user's session times out due to inactivity. IDMC displays a warning message to the user 60 seconds before the user is logged out.
Default is 30 minutes.
Authentication Type
Authentication type used after a user logs in. Default is Session ID.
For JWT authentication, select a duration for tokens to expire. Default is 30 minutes.
When you change the authentication type, the new type takes effect at the next login. The change doesn't affect sessions that are in progress.
Before you use the JWT authentication type, modify custom scripts to refresh the tokens before they expire.
For more information, see the JWT Support Knowledge article.
Note: Don't use the JWT authentication type if your organization uses API Manager or uses REST V2 Connector to call IDMC APIs.
Use Trusted IP Ranges
Enables IP address filtering.
IP address filtering uses trusted IP address ranges in addition to account passwords to prevent unauthorized users from accessing your organization. When you enable IP address filtering, a user with a valid login must also have an IP address within the range of trusted IP addresses, or the user can't log in to your organization.
When you enable this option, you must also enter one or more trusted IP address ranges.
Note: If you create a serverless runtime environment when trusted IP ranges are enabled, you must add the IP addresses of the DMZ NAT gateway to the list of trusted IP addresses. For a list of the DMZ NAT gateway addresses, see Runtime Environments.
Allowed Trusted IP Ranges
The trusted ranges of IP addresses from which users can log in to access the organization. IDMC supports IP address formats in IP version 4 (IPv4) and version 6 (IPv6).
Fields for the trusted IP address range appear when you enable IP address filtering. To enter additional address ranges, click +.
To ensure seamless communication between resources across both IPv4 and IPv6 networks, enable a dual stack configuration. For example, if your virtual machine uses one network type, IPv4 or IPv6, and the servers that host the connectors use another network type, enable dual stack on your virtual machine to ensure seamless communication regardless of their network type.
Note: If you enter an invalid IP address range, users cannot access your organization. Contact your network administrator for valid IP address ranges.

Connection Credentials storage location

You can configure where to store the connection properties for your organization. To specify where to store the connection properties, configure the Connection Credentials on the Settings page in Administrator.
You can store connection properties in either of the following locations:
Informatica Cloud
When you store connection properties on the cloud, the connection properties are stored in the IDMC repository and are always available. The connections are encrypted by the IDMC key management service.
IDMC backs up connection properties regularly as part of standard backup procedures.
Local Secure Agent
You might store connection properties with a local Secure Agent if you need the connection properties to reside within your firewall. When you enable this option, the properties for all connections that are listed on the Connections page are stored with the local agent.
If you choose this option, you can store connection properties with one Secure Agent. Connection properties are stored in the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data
When you store properties with a local Secure Agent, the Secure Agent must be running so that tasks can run and users can work with connections. Back up connection properties regularly to prevent loss of data. A best practice is to back up connection properties after you change the location or the encryption key for connection properties.
The connections are encrypted by the IDMC key management service. IDMC uses CBC (Cipher Block Chaining) mode 256 AES encryption to store the connections.
You can change where you want to store connection properties. When you do this, IDMC moves the connection properties to the appropriate location.

Data Integration service properties

Data Integration service properties are used by Data Integration. Configure these properties to set the time zone and default email addresses for job notifications.
You can set the following Data Integration service properties:
Jobs properties
The following table describes the jobs properties:
Property
Description
Schedule Offset
A small amount of time that is added to schedule start times to help prevent server overload at standard schedule start times. An organization has a single schedule offset that is applied to all schedules. The schedule offset does not affect the start time of manually started tasks or taskflows. You cannot change the schedule offset.
Even though it is not displayed in the schedule details, the schedule offset for your organization is added to the time range configured for all schedules. This ensures that scheduled tasks run as often as expected. For example, you configure a schedule to run every hour from 8:00 a.m. to 12:00 p.m., and the schedule offset for your organization is 15 seconds. Your schedule runs at 8:00:15, 9:00:15, 10:00:15, 11:00:15, and 12:00:15.
Time Zone
Time zone used to display job execution time stamps in email notifications.
Default email notifications properties
Configure the default email notifications properties to set the default email addresses to use for job failure, warning, and success messages. Enter one or more valid email addresses. Separate email addresses with a comma (,) or semicolon (;).
You can also set email notification properties at the task level. When you set email notifications in a task or taskflow, IDMC sends email to the addresses in the task or taskflow instead of the addresses configured for the organization.

CLAIRE recommendation preferences

Enable CLAIRE recommendations to allow in-product recommendations for mapping design based on analysis of metadata from your organization's assets and assets from other IDMC organizations. The metadata collected and processed by the CLAIRE engine is anonymous.
By default, CLAIRE recommendations are enabled. When you disable CLAIRE recommendations, recommendations are disabled for all users within your organization. You can enable or disable recommendations for your organization at any time.
When you enable CLAIRE recommendations, Data Integration users can disable recommendations for individual mappings in the mapping designer.