Multiple owner organizations

You can create more than one owner organization to exchange information with a trading partner.

Multiple owner organizations enable you to control who exchanges documents with particular trading partners, as defined in exchange profiles. Multiple owner organizations also control who can see information about each owner organization. You can modify and remove owner organizations that you create.

You must be a Master Account Administrator to create an owner organization. System Administrators cannot create owner organizations.

When you create multiple owner organizations, you can set up the following hierarchy of authority:

1. A Master Account Administrator can create exchange profiles for all of the owner organizations that it creates.
2. A Master Account Administrator can create administrators for each owner organization, so that each administrator can create exchange profiles with particular trading partners.

When you create a new user profile, you can create a new owner organization for that user profile. However, an owner organization can be associated with more than one user profile.

Users who are associated with a new owner organization inherit the user group, roles, and privileges of the user who created the organization. For example, you have the privilege to create a thread pool. When you create a new owner organization, a user that is associated with that new owner organization also can create a thread pool.

Users who are associated with a new owner organization always inherit the following resource read and list permissions of the user who created the new owner organization:

• Conformance policy
• AS4 receiver
  • HTTP/S server
  • Thread pool
  • User exits
• Destination
  • Message queue
  • User exits
• Messaging receiver
  • Message queue
  • User exits
• Destination
• Pull destination
• Security policies
• Organizational credential
• Digital certificates
  • Certificate authority (CA)
  • Private/public key pair
• Certificate revocation list
• Retry policies