Organization Administration

Back Next

Sub-organizations

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.

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.

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.; For more information about bundles, see Bundle management.
You can view aggregated IPU consumption metrics.: 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:

A diagram that shows the preferred way to set up sub-organizations. There are three parent organization: Development, Testing, and Production. Under each parent organization are two sub-organizations.

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.

Organizations

Adding a sub-organization

Removing a sub-organization

Disabling or enabling a sub-organization

Switching to a different organization

Denying parent organization access to a sub-organization

Add-on connectors in sub-organizations

Exporting and importing assets in sub-organizations

Sub-organization capability and service support matrix

Download Guide

Watch

Comments