[Index]

Model: relation/User

View users

Full HTML Help

The Admins list view displays users at or below the current hierarchy node. Users can be created in the system in various ways, depending on your setup:

• Synced in from LDAP and promoted to a user
• Synced in from applications (for example, Voicemail or Conferencing)
• Added to Automate when creating an end user
• Added to Automate when creating an admin user

User creation can also vary across different hierarchies in the system.

Note the following user details:

• Click on a user to view its details. See also: Check User Provisioning Status.
• Click Add to add a user manually.
• You can filter the Users list view via the toolbar Filter icon, then select the field (attribute), condition, and a filter value. The list view returns only those users matching the attributes you specified. For example, you may want to filter the list to display only users with authorized admin hierarchy set up.

Add admin user

Full HTML Help

Overview

• If you're adding a single role admin user and select an Authorized Admin Hierarchy instance that has been associated with the role, then the hierarchies set in the Authorized Admin Hierarchy override the default hierarchies associated with the role. See: Authorized Admin Hierarchies and Roles.

• If you're adding a multi-role admin user, the user must first reside at site level and then be assigned a self-service Role by a system administrator, and a selected Authorized Admin Hierarchy instance that has an administrator role.

  If needed, this step should also be carried out manually in the case of synced in users or users moved to a site.

Note that enabling the system setting Additional Role Access Profile Validation will restrict Authorized Admin Hierarchy roles to those with linked access profiles that are in the subset of the administrator's own access profile.

If the role is set to an administrator role and an Authorized Admin Hierarchy instance is also specified for the user, the role on Authorized Admin Hierarchy takes precedence. This is NOT a recommended configuration.

Related Topics

• Authorized Admin Hierarchies and Roles

Additional Role Access Profile Validation in Settings topic in the Advanced Configuration Guide.

Manually add an admin user

This procedure manually adds an admin user in Automate.

1. Log in at the hierarchy node where you want to create the admin user.

2. Go to the Users page.

3. Click Add.

4. Fill out details for the admin user on tabs or panels of the Users Page.

   Note

   You'll need to fill out at least the mandatory field values. Note that the read-only User Type field can have the following values:

   • "Admin" - this value is defined by the admin role
   • "End User + Admin" - this value is defined by a data/AuthorizedAdminHierarchy instance associated to the user as well as a self-service role

5. Click Save to add the new admin user.

   You can view transaction progress and details in the Transaction Logs (when adding, updating, or deleting a user).

Related Topics

• Users Page
• User Field Mapping
• Authorized Admin Hierarchies and Roles
• User Login Options by Authentication Method and Server Authentication Scope
• Update a User
• Cisco-Microsoft Hybrid Users
• Introduction to role-based access
• User Authentication

Transaction Logging and Audit in the Core Feature Guide

User settings

On the Users page you can view, add, or update a user.

You can select the following tabs/panels on this page:

• User Details
• Account Information
• Contact Information
• Hybrid Status
• Provisioning Status
• Services
• Custom
• LDAP

Update a user

Full HTML Help

Overview

Users are typically added or updated on Automate from the sync source, for example, LDAP, Cisco UCM, or CUC. See User Sync Source.

Sync source scenarios

Updating an admin user creates a sync with the application highest on the User Sync Source precedence, and according to the field mapping for that source. The sync occurs once you click Save.

• Add User Sync Scenarios
• Update User Sync Scenarios
• LDAP Add Sync Scenarios
• LDAP Update and Delete Sync Scenarios

Related topics

• User Field Mapping

Admin user password updates

If the admin user password is updated, user passwords on Cisco UCM, CUC, and Webex are also updated if these have been provisioned for the user.

User added as Microsoft Active Directory LDAP user

If a user was added as a Microsoft Active Directory LDAP user (see: Add admin user), then:

• Additional fields on the User tabs are exposed that can be saved to the Microsoft Active Directory LDAP server.
• Updates to user details on the LDAP form tab will update the Microsoft Active Directory LDAP server when clicking Save.
• If user updates made directly on the Microsoft Active Directory LDAP server will reflect on Automate once the user is again synced in Automate from the Sync & Purge menu.

The table describes additional actions for managing a user. These may be found in the toolbar overflow menu of the Users Page:

Related Topics

• Add admin user
• Users Page

Local Admins

Full HTML Help

This procedure adds administrators for intermediate nodes, and adds or edits local administrators or operators.

1. Log in as an administrator.

2. Set the hierarchy path:

   • To add or edit an administrator or operator at a level below your current level, set the hierarchy path at the top of the window.
   • If you have signed in as provider administrator and want to create a customer administrator, set the hierarchy path to the customer for which you want to create the administrator.

3. Go to the Admins list view.

   Note

   This menu list makes use of an [OR] condition to filter admins: Admin[OR]End User + Admin. For details on the filter, see: Ordering Lists.)

4. To edit an existing administrator or operator:

   • Click on the relevant user to open the Users[username) form.
   • Make the changes you require.
   • Save your changes.

3. To add a new administrator or operator:
   • Click the plus icon (+) to open the Users/New Record form.
   • Fill out the field values. Mandatory fields are indicated with an asterisk (*):

5. Click Save.

View and update LDAP authentication users

Full HTML Help

LDAP-authenticated users display on the Admins page in Automate. The list view includes users that use LDAP for authentication only, and users that have been synced from LDAP.

1. Log in as provider, reseller, or customer administrator.
2. Go to the Admins page.
3. Filter on the Sync Source column to display LDAP users.
4. Click Add to add a new LDAP user or select an existing LDAP user to update. For each user that uses LDAP for authentication the following information is displayed on the Account Information tab:

5. To disable LDAP authentication for a user, select the user and click Delete. LDAP Authentication for the user is removed from the Users list. Local authentication is used for the user to log in.

6. To update LDAP authentication for a user, select the user, make the updates and click Save.

   Note

   You can update only the LDAP Username field. However, LDAP authentication fails if the corresponding change is not also done on LDAP.

Webex User Details

Full HTML Help

Overview

You can add Cisco Webex App users into Automate in various ways:

• Add Webex App User (relation/SparkUser)

  Webex Contact Center agents can be added if a user is assigned a Contact Center Premium Agent or Contact Center Standard Agent license. Refer to the Assigned Licenses entry below, particularly the Contact Center panel form that allows for Contact Center agent management.

• Add Webex App user via Webex Quick Add User (view/WebexTeamsSubscriberQas)

  Go to Webex Quick Add User

  Note

  In this case, it is recommended you add Webex App users on a Webex Control Hub with the wholesale customer service. See Create Webex App Service and Quick Add Groups.

  In Webex Quick User, choose a Webex Teams User Template from the drop-down, or use the default user template (which is referenced in the Quick Add Groups associated with the user). If you want customized values, clone the Webex Teams User Template via the Configuration Templates page, and edit as required.

• Add Webex App user via the Users page (relation/MultiVendorSubscriber)

  Go to Add a Subscriber

• Add Webex App user via the flow through provisioning procedure.

  Go to Sync Webex App Users with Flow-through Provisioning

Related topics

• Provision Cisco Webex for an existing user (see Provision Webex App)
• Webex Quick Add User

View Webex user

To view a Cisco Webex App user:

1. Go to Webex User Services (dashboard), then:

   • Go to Manage Users (relation/MultiVendorSubscribers), then select a user to view and/or manage their user details, licenses, calling settings, phones, or services. You can also access quick actions available for the user, and enable or disable their login.

     Note

     If the user is associated with a phone (device) you can click the link adjacent to the device to go to relation/WebexDevice to view and manage the device settings.

     Multiple Jabber devices can be added to a Webex User as long as the user does not have an existing device of the same device type.

   • Go to Webex User Details (relation/SparkUser), then select a user to view and/or manage their account details and calling type, calling behavior, assigned licenses, or their roles and addresses.

   • Go to System User Details (relation/User), then select a user to view and/or manage their user details (including their authorized admin hierarchy and sync source), their account information, license audit details, their provisioning and hybrid status, their contact details, and their services.

Add Webex user via Webex User Details page

This procedure adds a new Cisco Webex user via the Webex User Details page in Automate.

1. Log in to the Admin Portal as a Provider, Reseller, Customer, or Site administrator.

2. Go to the Webex User Details list view.

3. Click the Plus icon (+) to add a new record, then choose the relevant site.

4. Configure account details and calling type on the Account Details & Calling Settings tab/panel:

   Note

   Location is read-only, synced from Control Hub.

   • (Mandatory). Select an email address. This value is used to match users when they're moved during an overbuild.

   • Fill out a first name and last name.

   • (Mandatory) At Display Name, fill out a display name for this user, typically, name and surname.

   • At Manager ID, select the manager's email address.

   • At Calling Behavior, choose an option to auto-populate settings:

     Note

     The default calling behavior is Calling in Webex App.

     • Calling in Webex App

     • Calling in Webex App (Unified CM)

     • Cisco Jabber app

     • Third Party app

       Note

       For Calling in Webex App (Unified CM), fields for device creation (Iphone, Android, CSF, Tablet) are displayed and checked by default.

   • Phone Numbers: The fields: Type (e.g. "Work") and Number are available for each entry.

   • Extension: Webex Calling extension is available if a user has a Webex Calling license.

   • Assigned Licenses: selected from licenses available on the Cisco Webex service as synced in from the Webex Control Hub.

     • Depending on a user's license, services such as Collaboration, Conferencing and Contact Center are available.

     • If Webex calling is enabled and a user is assigned a Webex Calling - Professional license, a Calling Settings panel on the form allows for the user management of Calling Settings (such as Barge In, Caller ID, Call Forward, Call Recording, Call Waiting, Intercept).

       Note

       If a user has Calling Settings available, these need to be removed and to be re-provisioned if it is necessary to move the user to another site. For details, see Move users, without services.

     • Configure Contact Center settings - displays only if the user is assigned a Contact Center Premium Agent license. Settings include:

       • User profile ID, Site ID, Team IDs, Skill Profile ID. See Webex Contact Center User Management

       • Agent Profile ID, Multimedia Profile ID. See Webex Contact Center Desktop Experience

         Note

         At Agent Profile ID, all global and only desktop profiles assigned to the same contact center site as the user are available.

6. On the Roles & Addresses tab/panel, select relevant roles:

   No administrator privileges	Default
   Full administrator privileges	Assigns access to all portal features, including: Assign roles Company policy and templates Device management Licenses and upgrades
   Read-only administrator privileges	Assigns read-only access to content available to a full privilege admin
   Support administrator privileges	Assigns access to user information and support logs
   User and Device Administrator	.
   Device Administrator	.

7. If available, on the Wholesale Package tab/panel, manage settings for packages in the Webex for Wholesale service, and their status, for example, provisioned.

   This tab/panel displays only when the Webex for Wholesale service is available. See Create Webex App Service.

   Depending on the package selected, the user's assigned licenses, as available on the Webex for Wholesale service, are then also updated when the user is provisioned.

   Note

   When modifying a Webex user and UCM Calling Licensing is deleted and the work phone number is also set to empty, the number is removed from the user. Work phone number remains assigned to the user if it's not set to empty.

8. Save your changes.

   The Cisco Webex App user is added. You can view added details in the summary list view, which also displays:

   • On-Prem UCM Calling Service (True/False) - Defines whether calling services are on-premise or cloud. The On-Prem UCM Calling license is removed if the Cisco Webex Calling (with UCM) is removed from the user.
   • Calling Behavior (determines license use) - options are:
     • Calling in Webex App - Allows calling via the Webex app using native Webex calling
     • Calling in Webex App (Unified CM) - Allows calling via the Webex app using a registration to UCM
     • Cisco Jabber App - Allows calling using a Cisco Jabber client registered to UCM
     • Third Party App - Allows calling using a third party app registered to UCM
       • Use Organization's Domain (True/False) - When enabled, the Cisco Webex organization domain is used for calling in Cisco Webex (Unified CM)
       • UC Manager Profile - May be used to identify the required UCM cluster when a calling behavior using UCM is selected. If the default UCM domain is selected, this is not required.
       • User Type - "Person", "Bot" or "App User (Guest User)".
       • Status - the current Cisco Webex App user status: for example: active/inactive, in a call/meeting/presenting, and so on. If unknown, then displayed as: "The user status could not be determined".

Delete a Cisco Webex App user

This procedure deletes an existing Cisco Webex App user (a synced in user, or one added via Automate).

1. Log in to the Admin Portal as a Provider, Reseller, Customer, or Site administrator.

2. Set the hierarchy to the Customer or Site level.

3. Go to Webex User Services. Choose an option to open a list view of users. See View Webex user.

4. From the list view, select users to delete, one or more; then, click the Delete icon.

5. Click Yes to confirm.

   Note

   When deleting a user with Cisco Webex App, the internal number inventory (INI) is updated as the number status is changed to Available, and the description, if any, is removed.

Provisioning users with Cisco Webex

This section describes how to provision Cisco Webex for a user, either via the Users list view, or via Webex Quick User.

Related topics

• Add Webex App User
• Webex Teams Quick Add

User relation

Model Details: relation/User