If your organization has the appropriate license, you can create one or more sub-organizations within your organization. Create sub-organizations to represent different business environments within your company. For example, you might create sub-organizations to represent different clients or different departments in your organization.
You can create a sub-organization from the production organization, from an additional production organization, or from a sandbox organization.
When you create a sub-organization, the organization that you use to create a sub-organization becomes the parent organization. Each sub-organization can have only one parent, and it cannot contain another sub-organization.
Note: Sub-organizations must reside in the same POD (point of deployment) as the parent organization. In a CI/CD (continuous integration/continuous deployment) -oriented approach, all sub-organizations receive feature releases simultaneously, potentially resulting in issues and downtime during the same maintenance window.
Your organization's license controls the number of sub-organizations that you can create. To increase this number, contact Informatica Global Customer Support.
Creating sub-organizations provides the following advantages:
You can manage sub-organization licenses individually or you can automatically synchronize them with the parent organization licenses.
Each sub-organization inherits all feature, connector, and custom licenses from the parent organization except for the license to create sub-organizations and bundle licenses.
Based on your organization's licenses, you can manage sub-organization licenses in the either of the following ways:
- Manage the licenses for your sub-organizations individually. The administrators for the parent organization can disable, enable, and modify the expiration dates for the licenses for each sub-organization. Changes to one sub-organization do not affect other sub-organizations.
- Automatically synchronize sub-organizations licenses with the parent license.
You can manage users and assets separately.
Each sub-organization has its own set of users and assets.
Users whom you create in a sub-organization are unique to the sub-organization. They cannot log in to the parent organization or to other sub-organizations. Only administrators in the parent organization and users in the parent organization that have sub-organization access privileges can access the parent organization and all sub-organizations.
Assets such as mappings and tasks are also unique within an organization. Assets are not shared among sub-organizations or between the parent organization and any sub-organization. If you want to migrate an asset between organizations, export the asset from one organization and import it into a different organization.
You can share runtime environments.
Administrators in the parent organization can share Secure Agent groups with the sub-organizations. When you share Secure Agent groups, users in the sub-organizations can run jobs on the Secure Agents within the group.
Users of a parent organization or sub-organization can use only a Secure Agent that belongs to that organization or sub-organization. Users of a sub-organization cannot use a Secure Agent that belongs to the parent organization.
Note: Share a Secure Agent group when all agents in the group run only the Data Integration Server service. You cannot run other agent services' jobs on a shared Secure Agent group.
For more information about shared Secure Agent groups, see Runtime Environments.
You can share resources using bundles.
The Bundle Deployment feature lets you push bundles seamlessly from your parent organization to your sub-organizations. This ensures a smooth and efficient distribution of resources and features across your organizational structure.
IPU (Informatica Processing Unit) consumption metrics for each sub-organization are aggregated and rolled up to their respective parent organization. This consolidation gives you a clear overview of how your resources are utilized. The consumption data is consolidated and rolled up within the organizational hierarchy until it reaches the main production organization.
You can switch between organizations without logging in to each one.
Users in the parent organization that have privileges to view sub-organizations can switch between organizations without logging out and logging back in to Informatica Intelligent Cloud Services.
Sub-organizations example
To observe CI/CD best practices, you want to create separate sub-organizations to represent different areas of your business, such as development, testing, and production. To achieve this, you first create separate parent organizations for development, testing, and production. Each parent organization should ideally be on a different POD, to safeguard against outages if a POD or organization becomes unavailable. Under each parent organization, you create sub-organizations that represent different clients or departments.
The following diagram shows the recommended hierarchy:
Using this hierarchy ensures a step-by-step flow of updates and improvements between environments, beginning with Development, moving to Testing, and concluding in Production. Isolating the environments in this way reduces the chances of unintended changes impacting other workflow stages.
For OEMs (original equipment manufacturers), the sub-organizations can represent individual clients. The structure allows the OEM to maintain control and oversee licensing, while allowing the individual clients to manage their development, testing, and production processes.
For corporations, the sub-organizations can represent different departmental divisions. This structure simplifies administrative monitoring and allows the parent organization to access assets, processes, and other resources set up by the departments.
Adding a sub-organization
To add a sub-organization, you can either create a new sub-organization or link existing organizations.
You can add a sub-organization in either of the following ways:
Create a sub-organization.
Log in to the organization that you want to be the parent organization and create a sub-organization. The new sub-organization is automatically linked to the parent organization.
Link existing organizations.
The organization that you link from becomes the parent organization and the organization that you link to becomes a sub-organization.
Creating a sub-organization
The administrator of a parent organization can create a sub-organization.
To create a sub-organization, you must be a native user with the Admin role or a native user with the "Suborg - create" and "Suborgs - view" privileges.
To create a sub-organization:
1Log in to the organization that you want to be the parent organization.
2Open Administrator and select Organization.
3Open the Sub-Organizations tab and click New Sub-Organization.
4Enter the properties for the sub-organization and click Save.
After you create a sub-organization, verify the licenses, and configure runtime environments, user accounts, and connections so that other people can use it.
Linking organizations
You can create a sub-organization by linking existing organizations. The organization that you link from becomes the parent organization and the organization that you link to becomes a sub-organization.
Before you link an organization, you need the organization ID for the organization that you want to link. You can find this information on the Organization page.
Note: If you link a sub-organization that has a license that the parent organization does not have, then the sub-organization loses the license.
You can link an organization if all of the following conditions apply:
•You have a user account with the organization.
•The organization is not the parent of another organization or a sub-organization of another organization.
•You are the administrator of the parent organization, and the parent organization has the license to create sub-organizations.
•The organization that you want to link as a sub-organization does not have the license to create sub-organizations.
You can later unlink the organizations.
To link organizations:
1Log in to the organization that you want to be the parent organization.
2Open Administrator and select Organization.
3Open the Sub-Organizations tab and click Link Sub-Organization.
4In the Link Sub-Organization dialog box, enter the following information:
- The organization ID for the organization you want to link.
- The user name and password of an administrator in the organization that you want to set up as a sub-organization.
5Click Link Sub-Organization to link the organization.
The organization displays on the Sub-Organizations page.
Removing a sub-organization
To remove a sub-organization, you can unlink organizations or delete the sub-organization.
You can remove a sub-organization in either of the following ways:
Unlink an existing sub-organization from its parent organization.
An unlinked sub-organization becomes a stand-alone organization. You can link it to a different parent organization or re-link it to the original parent organization. If you obtain the license to create sub-organizations for the unlinked organization, you can make it the parent organization for a different sub-organization.
Delete the sub-organization.
When you delete a sub-organization, you delete all of the assets and data associated with the sub-organization. If you have a usage-based license, after deletion, the sub-organization continues to consume IPUs in the current billing period. For more information, see IPU usage for disabled and deleted sub-organizations.
Unlinking a sub-organization
You can unlink a sub-organization from your parent organization. After you unlink an organization, update the unlinked organization with the required licenses unless you plan to link it to a different parent organization.
You can unlink a sub-organization if all of the following conditions apply:
•You have an administrator account with the sub-organization you want to unlink.
•You are an administrator of the parent organization, and the parent organization has the license to create sub-organizations.
•No asset in the sub-organization that you want to unlink uses a shared Secure Agent group as the runtime environment. If any asset in the sub-organization uses a shared Secure Agent group as the runtime environment, update the asset to use a different runtime environment before you unlink the sub-organization.
Note: This condition does not apply to Application Ingestion and Replication and Database Ingestion and Replication because Application Ingestion and Replication and Database Ingestion and Replication do not support shared runtime environments.
To unlink a sub-organization:
1Log in to the parent organization.
2Open Administrator and select Organization.
3Open the Sub-Organizations tab.
4Expand the Actions menu for the sub-organization that you want to unlink and select Unlink.
5In the Unlink dialog box, enter the user name and password of a user in the sub-organization with the Admin role.
6Click Unlink.
The sub-organization is no longer linked to the parent organization.
Deleting a sub-organization
You can delete a sub-organization. When you delete a sub-organization, you delete all of the associated data. If you have a usage-based license, the sub-organization's metering information is retained in the parent organization.
You can delete a sub-organization if you are the administrator of the parent organization.
1Log in to the parent organization.
2Open Administrator and select Organization.
3Open the Sub-Organizations tab.
4Expand the Actions menu for the sub-organization that you want to unlink and select Delete.
Note: Contact Informatica Global Customer Support to complete the deletion process.
If you have a usage-based license, the sub-organization continues to consume IPUs until the end of billing period in which the deletion was completed. For more information, see IPU usage for disabled and deleted sub-organizations.
Disabling or enabling a sub-organization
If you are the administrator for a parent organization, you can disable or enable a sub-organization.
When you create a sub-organization, the sub-organization is enabled by default. You might want to disable a sub-organization if you have a separate license agreement with the sub-organization and the license agreement expires. You can re-enable the sub-organization after you disable it.
You can disable or enable a sub-organization even if the sub-organization administrator blocks parent organization access to the sub-organization.
You can perform the following actions:
Disable a sub-organization
When you disable a sub-organization, the organization exists, but sub-organization users cannot log in to the sub-organization or access it through the REST API. Scheduled jobs in the sub-organization do not run.
When you enable a sub-organization, sub-organization users can log in to the sub-organization and access assets and perform tasks based on their user roles. Users with the appropriate privileges can access the sub-organization through the REST API. Scheduled jobs resume according to their schedules.
Disable or enable a sub-organization on the Sub-Organizations tab of the Organizations page. In the Actions menu for the sub-organization, select Disable or Enable.
Switching to a different organization
If you are an administrator in a parent organization or a user in a parent organization that has privileges to view sub-organizations, you can switch among organizations. You do not have to log out and log back in to Informatica Intelligent Cloud Services.
Note: If you switch from a parent organization to a sub-organization, you can't perform the following operations in the sub-organization:
•Create or import data transfer tasks
•Create or import dynamic mapping tasks
•Create, validate, publish, and run taskflows
•Export and import taskflows
To switch to a different organization:
From the Organization menu in the upper right corner, select the organization that you want to view.
Denying parent organization access to a sub-organization
If you are the administrator for a sub-organization, you can deny parent organization access to the sub-organization.
When you deny access to the sub-organization, users in the parent organization cannot switch from the parent organization to the sub-organization. Users in the parent organization with the appropriate privileges can make only the following changes to the sub-organization:
•Enable and disable the sub-organization
•Update the sub-organization licenses
•Edit the sub-organization properties such as the organization description and CLAIRE recommendation preferences
To deny parent organization access to the sub-organization, log in to the sub-organization as an administrator. On the Organization page, enable the Deny parent organization access to this sub-organization option.
Add-on connectors in sub-organizations
To use an add-on connector in a sub-organization, you must install the connector in the parent organization. You cannot install add-on connectors in a sub-organization.
Sub-organizations inherit all connector licenses from the parent organization. If a sub-organization should not use a specific connector, disable the connector license for the sub-organization. For more information about editing and disabling licenses for a sub-organization, see Editing sub-organization licenses.
Exporting and importing assets in sub-organizations
Export and import assets in a sub-organization in the following ways:
•Log in to the sub-organization and export or import assets from within the sub-organization.
• Parent organization administrators can log in to the parent organization, switch to the sub-organization, and import or export Data Integration assets.
Note: This condition does not apply to taskflows and Application Integration assets.
Sub-organization capability and service support matrix
The capability of sub-organizations vary based on the Informatica service.
The following table summarizes the capabilities for each service:
Service
Licensing capabilities
Metering capabilities
Bundles
Shared Secure Agents
Asset Access
Cloud Data Integration (CDI)
The parent organization has a license to create sub-organizations.
The parent organization must use feature-based licenses.
Available
Supported
Not supported
Cloud Application Integration (CAI)
The parent organization has a license to create sub-organizations.
The parent organization must use feature-based licenses.
Available
Not supported
Not supported
Cloud Data Governance & Catalog (CDGC)
The parent organization has a license to create sub-organizations.
The parent organization must use feature-based licenses.
Not available
Not supported
Not supported
Master Data Management (MDM)
The parent organization has a license to create sub-organizations.
The parent organization must use feature-based licenses.
Not available
Not supported
Supported
Cloud Data Quality (CDQ)
The parent organization has a license to create sub-organizations.
The parent organization must use feature-based licenses.
From the Organization menu in the upper right corner, select the organization that you want to view.