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 separate sub-organizations to represent your development, testing, and production environments.
You can create a sub-organization from the production organization, an additional production organization, or 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.
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.
When you manage licenses individually, administrators for the parent organization can disable, enable, and modify the expiration dates for the licenses that the sub-organizations inherit. They configure the licenses separately for each sub-organization. Therefore, disabling a license in one sub-organization does not disable the license in other sub-organizations.
Alternatively, if you have the appropriate license, you can automatically synchronize sub-organization licenses with the parent organization. When this license is enabled, each time a license is changed in the parent organization, all sub-organizations inherit the license change.
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 data integration 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.
Share a Secure Agent group when all agents in the group run only the Data Integration Server service. You cannot run non-data integration jobs on a shared Secure Agent group.
For more information about shared Secure Agent groups, see
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
You need separate environments for
task development, testing, and production to ensure that the tasks are tested before they are run in the production environment.
Log in to the parent organization as an administrator and create a sub-organization for task development, a sub-organization for testing, and a sub-organization for production. Add users to the sub-organizations, and ensure that the Data Synchronization license is enabled for each organization.
When task development is complete, export the tasks from the development sub-organization, and then log in to the testing sub-organization and import the tasks. When testing is complete, export the tasks from the testing sub-organization, and then log in to the production sub-organization and import the tasks.