Partner administrators must obtain approval from customer organization administrators when adding Webex for Wholesale services to unmanaged existing Webex customer organizations.

You must obtain organization administrator's approval for the following criteria's:

• The existing customer organization has 100 users or more.

• The organization has a verified email domain.

• The organization domain is claimed.

Automatic attachment scenario

In an Automatic Attachment scenario, a Webex for Wholesale subscription is added to an existing customer organization without notifying the existing org administrator or end user. Usually your Partner Org are given Provisioning Admin rights. However, if the customer org has no licenses or only suspended/canceled licenses, you will be made a Full Admin.

With Provisioning Admin access, you will have limited visibility in the Control Hub to the users in the existing org. It is recommended that you contact the customer admin and request Full Admin access to the org.

Adding Wholesale services to a preexisting customer organization through API

Partner administrators can follow these steps to add Wholesale services to an existing Webex organization through API:

1. If you do not already manage the customer, ask the customer admin to add you as an external administrator with full admin rights. This step is not mandatory at this stage but simplifies the process. The customer admin may have to do this later if the provisioning attempt is not eligible for an automatic attachment.
2. Ensure that the onboarding template has the "Allow admin-invite emails when attaching to existing orgs" toggle set to true (located in Common Settings of template details).
3. Collect the parameters needed to use the POST Wholesale Customer API:
   • provisioningId, packages, orgId, externalId, address.
     • The orgId can be obtained from the Account Section of the Control Hub.
     • The provisioningId can be found in the Onboarding templates section in Partner Hub by viewing a Wholesale template's details.
     • The provisioningParameters are required when any calling packages are being provisioned.
4. Provision the Wholesale services using the POST Wholesale Customer API, ensuring all required parameters are provided.
5. If the request is successfully accepted, a 202 response will be returned. This does not mean provisioning has succeeded, as wholesale provisioning is done asynchronously. Use the status attribute returned by the GET Wholesale Customer API to check if provisioning succeeded.

Adding Wholesale Services to a preexisting customer organization through Partner hub

Partner administrators can follow these steps to add Wholesale services to an existing Webex organization through the Partner hub:

1. Sign in to Partner Hub.

2. Click Create wholesale customer.

3. Enter the email address of the customer administrator in the Customer email screen.

4. Select the desired organization from the list, which lists the suggested one on the top.

5. Click Confirm and next.

   

6. In the Customer information screen, enter the company name, the template you want to apply, and click Next.

   The administrator email field is pre-populated with the email address entered in step 3.

7. Enter the customer headquarters location details in the Headquarter's location screen.

   If the headquarters is in a Webex supported location, click on I verify that this customer is in a Cisco Webex supported location check box.

8. Click Next.
9. Review the customer summary and click Create customer.

Limitations and unsupported use cases

1. After attaching wholesale services to a partner's own customer org, further provisioning must be done via the Public APIs, not through Partner Hub.
2. Organization approval is required from the customer admin in certain scenarios when adding wholesale services to a customer that is not currently managed by a Wholesale partner:
   • The existing customer organization has 100 users or more.
   • The organization has a verified email domain.
   • The organization domain is claimed.
3. Conversion of trial organizations to Wholesale customers is not supported.

Conditions of organization attachment

1. The first user from the existing org who is provisioned for Webex for Wholesale is not provisioned as an admin user. Settings and entitlements from the existing org are retained.
2. The organization’s existing authentication settings take precedence over what is configured on the Webex for Wholesale provisioning template. As a result, there is no change to how existing users log in.
3. If the existing customer organization has basic branding enabled, after the attach occurs, the Partner's Advanced branding settings will take precedence. If the customer wants the basic branding to remain intact, then the partner must configure the customer organization to override branding in the Advanced Branding settings.
4. The name of the existing organization will not change.
5. Restricted Admin Mode (set by the Restricted by Partner Mode toggle) is turned off for the attached org.