Model: view/GlobalSettings

When enabled, dial plan workflows enforce HCS Rules when provisioning Customers, Countries, Site and so on. Default = Inherit.

If your deployment uses a custom or specific dial plan that does not conform to the HCS rules, this setting should be set to No (False).

This setting displays only at hierarchies above site or or linked site levels, and only when Microsoft is enabled for your system (via the Enabled Services tab in Global Setting). When available, the setting is enabled only when Enforce HCS Dialplan Rules is set to No (disabled), else, the field is read-only.

In Microsoft environments, defines whether to allow the creation of duplicate numbers at sites in Automate when syncing in and provisioning users, or when creating number ranges. Default is No (duplicate numbers are allowed).

The system checks the setting for Enforce HCS Dialplan Rules before applying the Prevent Duplicate Numbers logic. When enabled, the system enforces unique number validation throughout the hierarchy.

Defines whether descriptions for the numbers (which can be added when the number inventory is managed via Number Management), display along with the numbers in the drop-down lists. For example, let's say you have a number and its description as follows: 1000 - CEO Internal. When this setting is enabled (Yes), both the number (1000) and its description displays in the lists (when using features such as Quick Add User).

The default is No.

Defines whether vendor names for the numbers show in number dropdown as an option.

For example, a number 982017206 (which is from Microsoft vendor) will display as 982017206 [Microsoft] in the drop-down list.

Defines whether number types for the numbers show in number drop-down as an option.

For example, a number 982017206 (which is from Microsoft vendor and is of type OperatorConnect will display as 982017206 [OperatorConnect] in the drop-down list.

Defines the availability of numbers in the system when a phone, user, or service associated with the number is deleted, and the number is no longer associated with these entities. Options are:

• Inherit:

  When set to True, number inventory cooling is enabled or disabled based on the setting defined for number inventory cooling at a higher level in the hierarchy.

• Yes (True)

  Enabled at the current hierarchy. Numbers associated with deleted entities are kept in a cooled state for a specified number of days (based on the value defined in the Number Inventory Cooling Duration (Days) field.

  Numbers in a cooled state are unavailable in the system until the cooling period end date is reached, unless they are manually released before the "end cooling period" end date.

• False (No)

  Default. Number inventory cooling is disabled by default.

When number inventory cooling is enabled (Yes/True), this field defines the period (number of days) the number is kept in a cooled state and unavailable for association with a phone user, or service.

The default is 30 days.

Enables/disables custom number inventory filters at the current hierarchy. Shipped inventory filters can't be enabled or disabled as these reside at sys level. When enabled, custom and shipped inventory filters display in a drop-down list on forms such as Quick Add User, Onboard User (to add a user from a profile), Multi vendor service user move, Cisco Advanced User, Phones, Extension Mobility, and Single Number Reach. Options are:

• Inherit (default):

  When set to True, custom inventory filters are enabled or disabled based on the setting defined at a higher level in the hierarchy.

• Yes (True)

  Enables custom inventory filters at the hierarchy. When set to True, select the inventory filters to make available for selection in relevant drop-down lists, either shipped and custom inventory filters or all enabled inventory filters. You can view the available filters at a hierarchy via Manage Filters. When enabled, you can enable or disable specific filters at specific hierarchies via Manage Filters.

• False (No)

  Custom and/or cloned shipped filters are disabled at the hierarchy.

When Enable Filters is set to Yes, the selected filter defines the number inventory filters available in the the drop-downs for choosing a number inventory filter. Options are:

• Inherit
• Shipped Enabled Filters
• Custom Enabled Filters
• All Enabled Filters (default)

When set to Inherit, the value displays for the filter group that will be used from a higher level in the hierarchy.

Custom enabled filters will only display in the drop-downs if these exist and are enabled at the hierarchy you're working at.

All Enabled Filters includes all custom and shipped filters, provided they are enabled at the hierarchy you're working at.

Choose a hierarchy level at which the aggregate of available numbers should be calculated (Provider, Reseller, Customer, Site), and displayed in the body of the alert.

The shown data in the body for this hierarchy level is:

• Hierarchy node name
• Hierarchy node type
• Hierarchy full path
• Total numbers available
• Total numbers
• Total percent available

Data is also included for lower hierarchies (as tables and in CSV format). For details, see the following topics:

• Email in the Core Feature Guide
• Number Inventory Alerts in the Core Feature Guide

When enabled, alerts will be raised and optionally emailed if the Microsoft license availability threshold is reached at the hierarchy. Default = Inherit.

Note that this setting requires that Enable Microsoft User License Enforcement is enabled under the User tab.

Refer to Availability Threshold Percentage below.

Defines a percentage of remaining Microsoft licenses at which an alert is raised.

Percentages are available in the drop-down lists: 10, 15, 20, 25. Default = Inherit.

Defines whether an email group will receive alerts. Default = Inherit.

If set to Yes at the hierarchy, the Alert Email Group drop-down list provides available email groups.

Defines whether to enable retrieval and display of Cisco Webex Contact Center device model references from the Webex Control Hub.

It is recommended that you enable this setting in the Global Settings only for any customer where you want to retrieve the reference details. This is to prevent a performance impact on customers where the setting is not required.

Defines whether an email is sent to a user when added via Quick Add User. The default is No.

When set to Yes, and a SMTP server is set up via Apps Management), then selecting the option to send an email when using Quick Add User, a welcome email is sent to the new user.

Defines whether to delete an existing, unassigned phone (a phone without an owner), when re-adding a phone with the same name and product type (duplicate phone).

Default is Inherit (No, inherited from the hierarchy above), which triggers a transaction failure if you try adding a duplicate phone, for example, in a Quick Add User bulk load or when updating a user.

When set to Yes, a system check verifies whether the phone exists and/or if it is already assigned (whether ownerUserName field is populated):

• If the phone exists and is assigned to a different user, the transaction fails.
• If the phone exists and is unassigned, the existing phone is deleted, the phone is re-added, and is assigned to the user you're adding or updating.
• If the phone exists and is already assigned to the user you're working with. The system performs an update.

Defines whether a user's associated desk (hard) phones (phones prefixed with SEP or BAP) are deleted or retained when that user is deleted.

When set to Yes:

• The deleted user's hard phones are retained.
• The deleted user's soft phones (such as Jabber devices) are deleted.
• An additional field displays (Update the Retained Desk Phone with Configuration Template), which allows you to define whether retained phones are updated via a CFT once the user is deleted.

Default is Inherit (set to No).

This setting defines hard phone delete/retain behavior for any method of deleting a user, for example, delete user via the User's list view, or delete user in LDAP import, purge or sync (where delete or purge mode is automatic).

You can view the hard phones associated with the user on the Phones tab in the user settings.

This field displays only when Retain Desk Phones when user is deleted is set to Yes (True).

Defines whether to update retained hard phones via a configuration template (CFT) when the associated user is deleted.

This feature ships with a default CFT (RemoveOwnerFromPhoneCFT), which clears the phone's Owner User ID if the phone is retained when deleting the associated user. You can choose a different CFT for the update step, if required.

Options are Yes, No, Inherit. Default is Inherit (inherited from the hierarchy above)

Set to Yes to enable. You will need to save this update then refresh the tab to display an additional configuration field (Additional information in Phone dropdowns).

Options are Yes, No, Inherit. Default is Inherit.

Additional information options are Description, First Line, and Description + First Line.

The default, Description, means that the phone description (if defined) displays in the phone selection drop-downs on the Replace Phone configuration page (Existing Phone tab, Device Name drop-down), and on Quick Add User, allowing you to search by phone description when choosing a phone from the drop-down.

In the same way, when the additional information option is set to either First Line or Description + First Line, you can search for or choose phones based on this criteria.

Options are Yes, No, Inherit. Default is Inherit.

For any transaction adding a Cisco phone, if this setting is enabled, the transaction will fail with a message:

Phone already exists with name:

if any phone is found containing the same MAC address within all clusters in a customer or reseller.

The default authentication method to use when a user is synced in or added manually.

The default is Local (inherited).

Maps the Microsoft Azure UserPrincipalName (UPN) attribute to CUCM userIdentity attribute - used in Cisco-Microsoft hybrid configurations where the same user ID is on every user account (MS Teams, CUCM, etc.).

If enabled, the CUCM user's userIdentity attribute is used for the import of MS teams CsOnlineUser and MS 365 Msol user instances.

The default is No (inherited).

Defines the user groups (one or more) that admins will not be allowed to assign to user.

This is to prevent users being incorrectly assigned elevated permissions to system resources that are reserved for users in the groups you specify here.

Fill out the user group names in a colon-separated format, for example, Standard CUCM SuperUser:MyGroupName

Defines whether to convert CUCM users that would normally be automatically deleted by the CUCM, to be converted into CUCM Local users during a data sync of CUCM.

When disabled (default), users that have been in status "Inactive LDAP Synchronized User" for more than 24 hours are automatically deleted by the CUCM. These users and their services are then deleted from Automate on the next CUCM data sync.

When enabled, users that have changed their status to "Inactive LDAP Synchronized User" are converted to "Enabled Local Users" on the next CUCM data sync. The data sync of the CUCM must occur within 24 hours of the users becoming inactive otherwise, CUCM will still delete them.

Defines whether to retain a user at a site instead of moving the user back to customer level when performing the task: Quick Offboard User.

The default is No (inherited).

Enabled only when Enable Move & Flow Through Provisioning is enabled.

Defines whether move and flow through provisioning on Add sync is enabled. The default is No.

Enabled only when Enable Move & Flow Through Provisioning is enabled.

Used only for adding and onboarding users. Defines the default criteria applied in an Add sync when moving and provisioning a user with flow through provisioning. The user is synced in, moved to a site, and provisioned with relevant serves in one step, based on the flow through provisioning criteria.

Microsoft users only. Allows the system to automatically move an existing non-hybrid, Microsoft-only user, from one site to a new site, with their services and a new line, in a scheduled or manually triggered sync.

When set to Yes, triggers display of these additional fields to apply controls for move using between sites, and provisioning in an update sync:

• Number Assignment Control (Update Sync)
• User Profile Control (Update Sync)

Displays only when Enable Move & Provisioning after Update Sync is set to Yes.

Update sync only. Defines whether a user keeps their existing number or is assigned a new number when moved from one site to another site. Options are Inherit (from the hierarchy settings above this one), Keep Existing Number (default), or Assign New Number.

Note that this is a global setting at the hierarchy where you're applying the setting so all users updated in this move and sync will either inherit settings, or keep their numbers, or be assigned new numbers.

Displays only when Enable Move & Provisioning after Update Sync is set to Yes.

Update sync only. A single default profile used only in update syncs with flow through provisioning to apply criteria for moving the user. In an update sync, only this user profile applies for the move. The Flow Through Provisioning Criteria setting on this tab/panel applies only for add syncs.

Enables/disables Cisco CUCM services. The default is Yes.

When set to Yes, allows an admin user to provision a user with new CUCM services, such as a Cisco phone, Jabber, and Extension Mobility, provided the server is installed, and the entitlement profile and field display policy pass a verification check.

Enables/disables Cisco/Microsoft hybrid services. The default is No.

When enabled, Automate allows for provisioning users and services from both Cisco and Microsoft devices, and makes available an admin user parent menu called Hybrid Cisco-Microsoft Management, and associated access profiles. For details, see Hybrid Cisco-Microsoft Management in the Core Feature Guide.

Specifies the hierarchy level up to which Quick Add Groups and user profiles will be searched for. The default is Provider level. (sys and hcs levels are not available.)

When a lookup level is set, selections of available QAGs and user profiles will be restricted upwards to this lookup level.

If you have hybrid customers (customers using both Cisco and Microsoft, for example), you can create hybrid-specific user profiles for those hybrid customers, then set the lookup level for those customers to Customer level so that they will have available a hybrid user profile in the drop-down at that customer hierarchy.