Introduction
This guide provides a step-by-step walkthrough for setting up both OEM Vendor accounts and OEM End-User accounts within the CCH system. It is divided into two sections:
OEM Vendor Account Setup: Covers the initial setup, configuration, and billing setup for OEM Vendors.
OEM End-User Account Setup: Details the steps for OEM Vendors to create and manage end-customer accounts.
Each section includes specific roles and tasks involved in the setup, along with SQL commands and portal actions where applicable.
| Expand | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Section 1: OEM Vendor Account Setup
Introduction
This section outlines the process for setting up an OEM Vendor 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 Vendor Account
The following are the steps required to set up a new CCH OEM Vendor that requires database access:
SALES: Create a new Account in CCH Production (account_status = DEMO). Note the account_ID value. The vendor 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:
...
| Code Block | ||
|---|---|---|
| ||
update ch_account set reseller_id=99999, reseller_status=2, account_status='oem_vendor' where account_id=99999; |
...
2. Authority Document Access Configuration
SALES: Sales to provide DEV the list of Authority Document ID’s as specified in OEM Vendor 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:
| Code Block | ||
|---|---|---|
| ||
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
3. Billing Information Setup
OEM VENDOR:
...
Navigate to the Billing
...
tab in the Partner Portal (https://partner.unifiedcompliance.com)
OEM VENDOR: Complete the required Admin/Billing user
...
details and submit.
Section 2: OEM End-User Account Setup
1. End Customer Account Creation
OEM VENDOR:
...
VENDOR: Enter the first & last name of the end customer, their email address, and their organization name and press CONTINUE:
...
Log into the Partner Portal and select Add Customer > Create New Account.
OEM VENDOR: Provide end-customer details (first and last name, email, organization name), and select Continue.
2. Select Subscription
OEM VENDOR: Fill out the street address, city, state, county, and zip code. If applicable, add a PO Number.
...
OEM VENDOR: Choose the base subscription
...
and
...
appropriate Add-On
...
. Select
...
Checkout to complete the subscription setup.
| Info |
|---|
Base subscription may autoselect. |
| Note |
|---|
Only 1 add on can be selected |
3. Manager Lists
OEM VENDOR:
...
In the Partner Portal, select View Customer > Manage Lists.
OEM VENDOR:
...
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.
| Note |
|---|
NOTE: |
...
Once a list has been added, it cannot be removed (as a security measure). Contact Development should a list need to be removed. |
...
4. Final Configuration
OEM Vendor: can now use the end customer’s API Key to make API calls for content
...
.