The April 2026 release of Administrator includes the following changed behavior.
Permission-based connection access
Informatica enforces connection-level permissions for listing and selecting connection assets. You can now granularly control who can view, edit, or delete specific connections based on the permissions. This update improves security and access control by restricting visibility and access to connection assets based on your assigned permissions, preventing unauthorized users from viewing or using connections.
Previously, you could see the names of all connections in the organization, even if you didn't have specific permissions for those connections.
For more information about the required permissions, see Permissions in the Administrator help.
Bitbucket source control repositories
Bitbucket has deprecated app passwords and replaced them with API tokens. Bitbucket will no longer accept app passwords for repository access starting June 9, 2026.
After you switch to the new authentication method in Bitbucket, update the following source control authentication fields on the IDMC user settings page:
•User name. For cloud-hosted repositories, enter the email address associated with the Bitbucket repository. Previously, you entered a Bitbucket user name.
For on-premises repositories, enter your Bitbucket username as usual.
•App password. For cloud-hosted and on-premises repositories, enter the Bitbucket API token. Previously, you entered the Bitbucket app password.
The field labels in the IDMC user interface will change accordingly in an upcoming release.
Note:
When you create a Bitbucket API token for
IDMC
, be sure to select the following scopes:
•read:workspace:Bitbucket
•read:project:Bitbucket
•read:pullrequest:Bitbucket
•read:repository:Bitbucket
•read:user:Bitbucket
•write:pullrequest:Bitbucket
•write:repository:Bitbucket
For more information about Bitbucket API tokens, see the Bitbucket documentation.
Advanced configuration asset privilege
The asset privilege that allows users to create, read, update, delete, or run advanced configurations has been renamed to Advanced Configuration.
Previously, the privilege was named Elastic Configuration.
Critical notifications
Administrators can't opt out of notifications from the Critical Notifications category. Critical notifications include updates for the organization and network, operational changes that impact service availability, and release information that requires user action.
Previously, administrators were encouraged to stay opted in to these notifications but had the ability to opt out.
Support for dynamic dispatch queue configuration on Secure Agents
If Process Server runs on a Secure Agent, you can enable the dispatch service to dynamically create dispatch
queue configurations and avoid deadlocks.
To enable dynamic dispatch queue configuration, in the Custom Configuration Details section of the agent
details page, add the useDynamicDispatchService property and set the value to true.
Previously, you used the dispatch service to manually create dispatch configurations that throttle requests
made to the Process Server.
For more information, see Secure Agent Services in the Administrator help.
Elastic runtime environments
Elastic runtime environments have the following changes:
•The environment variables in the config.txt file have been updated to improve cluster deployment.
•You need sudo access to install and uninstall the cluster on the master node. Previously, you could run commands to install and uninstall the cluster without sudo access.
•To install the cluster, you now run sudo ./cluster-installer.sh instead of ./create_cluster_nodes_ha.sh.
•You need to run the cluster installer in the foreground. Previously, you could run the cluster installer in the background if you didn’t configure proxy server settings.
•When you run the cluster installer, it prompts you for your IDMC user name, IDMC password, certificate path, and proxy password. Previously, it prompted you for only the proxy password if you configured proxy server settings.
For more information, see Runtime Environments.
IPU consumption alerts
You can now assign the metering.admin privilege to allow users to edit IPU consumption alerts.
Previously, only users with the Administrator role could edit the IPU consumption alerts.
REST API getting Secure Agent basic information
When using the /api/v2/agent API call to get agent details, the information returned no longer includes package and configuration details by default. To include this information, add the request parameter basicinfo=true to the API call.
For example, the following API call returns details for all Secure Agents in the organization, including package and configuration information:
/api/v2/agent?basicInfo=true
Resetting a user with SAML single sign-on
The Reset option on the Users page is no longer available if Intelligent Data Management Cloud is configured to use SAML single sign-on. For password assistance in this instance, contact your SAML administrator.
Organization settings
In Administrator, the following settings have been moved from the Organization page to the General tab of the Settings page:
•Authentication
•Data Integration Service
•Enterprise Data Catalog
For more information, see the Organization Administration guide.
Authentication type
Users with a role that includes the privilege to view organization information in Administrator can view the authorization type on the Settings page. Previously, only users with the Admin role could view the authorization type.