Section 1: OEM Partner Account Setup

Introduction

This section outlines the process for setting up an OEM Partner account, configuring Authority Document access, and setting up billing information. Follow these steps to ensure that the account is correctly established and equipped for content management.

1. Create a New OEM Partner Account

The following are the steps required to set up a new CCH OEM Partner that requires database access:

• SALES: Create a new Account in CCH Production (account_status = DEMO). Note the account_ID value. The Partner can sign up and create this account themselves, or, Unified Compliance can create it for them.

• DEV: Update the account status to “oem_vendor” and put the account in the Partner Portal. Run the following SQL and change the reseller_id and account_id value to the one from step #1:

update ch_account set reseller_id=99999, reseller_status=2, account_status='oem_Partner' where account_id=99999;

2. Enable Customer Type

In the Partner Portal, a customer type dropdown has been added with these possible values: CCH, CCH OEM, Nextgen, and Nextgen OEM. We need to specify which of these this account will have access to. In the short-term, we expect accounts will only have access to one of these, but it is possible for an account to have multiple of them enabled. A new reseller_enablements table has been added for this and these are the possible TYPE values: cch, cch_oem, nextgen, nextgen_oem. So, for a CCH OEM Partner, run the following insert statement with the correct account_id value:

insert into reseller_enablements (type, account_id) values ('cch_oem', 99999);

3. Authority Document Access Configuration

• SALES: Sales to provide DEV the list of Authority Document ID’s as specified in OEM Partner contract.

• DEV: Configure the account to have access to list of AD IDs provided by Sales. Replace the account_id below with the one from step #1 and the AD ID’s to the ones provided by Sales:

insert into entity_singular_entitlements (class_name, entity_id, account_id)
select 'Db_Entity_AuthorityDocument', ad_id , 99999
from authority_documents where ad_id in (3687,3242,3241,3240,3224,3222,3221,3212,3647,3292,3567,3430,3714,3201,3986,3960,3200,3208,986,985,3946,3134,3417,3416,3438,3415,3420,3419,102,2935,3009,176);

• SALES / SUPPORT: Log in to CCH Manage in production and impersonate the Admin user of the account, and create the Authority Document List(s) that correspond to their contractual list of authority documents. The lists can be created manually OR imported from published lists that UCF may have already created. NOTE: Only lists created via impersonate will appear in the Partner Portal. It is possible to manually update a list that was not created via impersonate (should we need to) by setting ch_authdoc_list.reseller_assignable = 1

4. Billing Information Setup

• OEM Partner: Navigate to the Billing tab in the Partner Portal (https://partner.unifiedcompliance.com)

• OEM Partner: Complete the required Admin/Billing user details and submit.

Section 2: OEM End-User Account Setup

Introduction

Once the OEM Partner account is set up, this section details the process for adding and managing end-customer accounts. It includes steps for subscription setup, list management, and enabling API access to Authority Documents for each end customer.

1. End Customer Account Creation

• OEM Partner: Log into the Partner Portal and select Add Customer > Create New Account.

• OEM Partner: Provide end-customer details (first and last name, email, organization name), and select Continue.

2. Select Subscription

• OEM Partner: Fill out the street address, city, state, county, and zip code. If applicable, add a PO Number.

• OEM Partner: Choose the base subscription and appropriate Add-On. Select Checkout to complete the subscription setup.

3. Manage Lists

• OEM Partner: In the Partner Portal, select View Customer > Manage Lists.

• OEM Partner: Add the applicable Authority Document List based on the purchased Add-On. This will copy the list into the end customer account and grant access to the documents included in that list.

4. Final Configuration

• OEM Partner: can now use the end customer’s API Key to make API calls for content.