.. _create_a_customer: Create a Customer ------------------ .. _18.1-Patch-Bundle-3|VOSSSOL-10561: .. _21.1|EKB-7504: 1. Log in as provider or reseller administrator, depending on which organization manages the customer. Log in with the provider or reseller administrator's email address, which is case-sensitive. The provider administrator can find the reseller administrator's email address on the **Admins** form (default menu **User Management > Admins**) by clicking the reseller. #. If logged in as provider, and the customer is to be added under a reseller, set the hierarchy path to the reseller. #. On the **Customers** form (default menu **Customer Management > Customers**) click **Add**, or to modify select a customer. #. Complete or modify the following fields: .. tabularcolumns:: |p{2.5cm}|p{11.5cm}| +---------------------------+--------------------------------------------------------------------+ | Field | Description | +===========================+====================================================================+ | | The name of the customer. This field is | | | mandatory. | | | | | | Note: | | | | | Customer Name | Any spaces in the customer name are converted | | | to underscores in the customer local | | | administrator name and email, if the **Create | | | Local Admin** check box is selected. | +---------------------------+--------------------------------------------------------------------+ | Description | Customer description | +---------------------------+--------------------------------------------------------------------+ | | Customer domain. This field is used to create | | | email addresses for: | | | | | | * The customer default local administrator, | | | for example: Customer1Admin@customer1.com | | | | | | * Site default local administrators under | | Domain Name | the customer, for example: | | | Site1Admin@customer1.com | | | | | | If the customer domain is omitted, the | | | provider domain (or reseller domain, if the | | | customer is under a reseller in the hierarchy | | | and the reseller domain was provided) is used | | | instead. | +---------------------------+--------------------------------------------------------------------+ | Public Sector | Set the Customer as a Public Sector customer. | | | Used for License Reporting. | +---------------------------+--------------------------------------------------------------------+ | Inactive Billing | Exclude customer from billing (for testing). | | | Used for License Reporting. | +---------------------------+--------------------------------------------------------------------+ | Create Local Admin | Controls whether a default local | | | administrator is created for the customer. | +---------------------------+--------------------------------------------------------------------+ | | The Provider or Reseller role used to create | | | a new role prefixed with the customer name. | | Cloned Admin Role | The created customer role, shown in the | | | **Default Admin Role** field, is assigned to | | | the default local administrator user. This | | | field appears only if the **Create Local | | | Admin** check box is selected. | +---------------------------+--------------------------------------------------------------------+ | | The created customer role that is assigned to | | Default Admin Role | the default local administrator. This field | | | is read-only, and appears only if the **Create | | | Local Admin** check box is selected. | +---------------------------+--------------------------------------------------------------------+ | | The password to assign to the default local | | Default Admin | administrator. This field appears and is | | Password | mandatory only if the **Create Local Admin** | | | check box is selected. | +---------------------------+--------------------------------------------------------------------+ | Repeat Default | Confirm the default local administrator | | Admin Password | password. This field appears and is mandatory | | | only if the **Create Local Admin** check box | | | is selected. | +---------------------------+--------------------------------------------------------------------+ | Prime Collaboration | Prime Collaboration is the application which monitors | | | equipment used by this customer. Available Prime | | | Collaboration applications must first be configured | | | using the HCM-F User Interface. Then HCM-F synchronization | | | must be executed on VOSS Automate. After the HCM-F data syncs | | | into VOSS Automate, available Prime Collaboration applications | | | will appear in this drop-down. Select an available Prime | | | Collaboration application to monitor Unified Communications | | | applications and customer equipment configured for this customer. | | | | | | To unassociate Prime Collaboration for this customer, choose None. | +---------------------------+--------------------------------------------------------------------+ | Shared UC Applications | Indicates whether the customer can use Shared UC Apps. | | | If selected, the customer sites can use Network Device Lists | | | that contain Shared UC Apps. Shared UC Apps are UC Apps that | | | are defined above the Customer hierarchy level. | +---------------------------+--------------------------------------------------------------------+ | Disable Number Management | Enable or disable Number Management for this customer. | | | | | | * If selected, you cannot add Directory Numbers and E164 | | | Numbers to inventories for this customer. | | | | | | * If *not* selected, you can add Directory Numbers and E164 | | | Numbers to inventories for this customer. | +---------------------------+--------------------------------------------------------------------+ If you enable Number Management for a customer after it was disabled, run the DN Audit Tool - see :ref:`run_the_directory_number_inventory_audit_tool`. 5. Click **Save**. .. note:: When deleting a customer, remove any entities associated with the customer like LDAP, SSO providers, Devices, and NDLs.