Inviting a Tenancy to Join an Organization

• Console
• CLI
• API

• You can attach governance rules to the invited tenancy when you create the invitation, or you can attach rules later. To attach governance rules before sending the invitation, you can create governance rules first on the Governance Rules page, so they're available for selection during the invite tenancy process.

  To invite a tenancy, follow these steps:

  1. Sign in to the sender tenancy (the one that will send the invitation), as a user that has permissions to manage Organization Management functions.
  2. Open the navigation menu and select Governance & Administration. Under Organization Management, select Tenancies.
  3. Select Invite tenancy.
  4. On the Invite tenancy panel, in Invitation name, enter the name of the invitation that will be visible to the recipient. Avoid entering confidential information.
     Note
     
     For the invitation name, it can be helpful to use notation that signifies the direction and number of sending invitation attempts. For example, entering a1 to b1 v1 can signify that tenancy a1 is sending an invitation to tenancy b1, and v1 as the first try. Such a convention allows the invitations to be more readable to the Console user, without needing to access the invitation details page to view sender and recipient details. For more information, see Listing Sender Invitations and Listing Recipient Invitations.
  5. In Recipient tenancy OCID, enter the recipient's OCID. You can find the OCID on the tenancy details page.
  6. In Recipient email, enter and confirm the recipient's email address.
     Note
     
     To accept the invitation, the recipient must have the correct permissions to manage subscription sharing in the recipient tenancy. For more information, see Required IAM Policy.
  7. Select Show advanced options and enter any tagging details. For more information, see Resource Tags.
  8. Select Next.
  9. In the Governance rules step, you can select governance rules to attach to the tenancy, or skip this step and attach them later. By default, the Require tenancy to join organization governance option is selected for the tenancy. If this option is cleared, a message indicates that you haven't selected organization governance for this tenancy. To attach governance rules to this tenancy in the future, you must request the invited tenancy to use governance rules, and have the tenancy accept (opt in to) the request.
  10. If you want to select governance rules now, select them from the table. You can filter the table by the rule type (All, Allowed regions, Quota policies, Tags), or the targeted tenancy. You can expand any rule entry and view its details.
      Note
      
      Some rules are set by the entire organization. Such rules are already selected, and can't be cleared.
  11. Select Next.
  12. Review the summary step to verify the invited tenancy settings.
      • Tenancy details shows the invitation name and recipient tenancy OCID.
      • Governance rules shows the rule names, rule type, and targeted tenancies if governance rules were attached. Whether rules were attached or not, the Require tenancy to join organization governance field indicates whether the invited tenancy is required to join organization governance with Yes or No. Governance rules can be created, attached, and detached later.
  13. Select Invite tenancy.
      The invitation is sent to the recipient tenancy. A notification is displayed that you have successfully requested to invite a tenancy (with the associated OCID) to join the organization. If the request completes successfully, then the recipient tenancy receives an invitation to accept. The invitation expires in 30 days.
  14. After the invitation is accepted and processed, its Status field changes to Accepted. The recipient tenancy then becomes a child tenancy under the parent tenancy in the organization.

      After the invitation is accepted, it takes one to two hours for metering to start flowing to the subscription in the parent tenancy. After that, all usage in the child tenancy is metered against the parent tenancy's subscription. In addition, after the tenancy joins the organization, we recommend that you wait a few hours before creating resources (that is, if you want to be sure that all spending accrues against the subscription of the parent tenancy).

      If a remaining subscription balance exists, contact your sales representative to move it to a primary subscription in the sending tenancy.

      Note
      
      After the tenancy becomes a child tenancy in the organization, it can't invite another tenancy to become a child tenancy. Also, when a tenancy joins your organization, its subscription is managed by the parent tenancy. To map a child tenancy back to the original subscription, use Subscription Mapping.

  On the Tenancies list page for the child tenancy and the parent tenancy both tenancies are listed. On the parent tenancy's Tenancies list page, you can view the child tenancy and parent tenancy, and other child tenancies that are being metered against the organization's subscription. The following information is shown:

  • Tenancy name: Displays the name of the tenancy and whether it's a parent or child tenancy.
  • Tenancy OCID: Displays the OCID of the tenancy.
  • Status: (Parent tenancy only) Displays the invitation status.
  • Organization governance: Specifies whether the tenancy is using governance rules (Joined) or not (Not joined).
  • Join Date: (Parent tenancy only) The UTC date and time that the tenancy joined the organization and subscription sharing began.

  See Accepting an Invitation to Join an Organization for more information on accepting an invitation to join an organization.

• Use the oci organizations sender-invitation create command and required parameters to create a sender invitation and asynchronously send the invitation to a recipient:

  Command

  CopyTry It

  oci organizations sender-invitation create --compartment-id, -c [text] [OPTIONS]

  For a complete list of parameters and values for CLI commands, see the CLI Command Reference.

• Run the CreateSenderInvitation operation to create a sender invitation and asynchronously send the invitation to a recipient.