[Index]
Tip
Use the Action search to navigate Automate
Overview
This section describes the user settings for admins and end users.
You can select the following tabs/panels to view and manage admins and users:
An additional More Actions toolbar overflow menu also provides additional user management actions on the System User Details form. See Additional user settings.
Note
Click the toolbar Switch to Tab/Panel layout option to toggle between a panel or tab layout.
User Details tab/panel
This section describes the user details settings.
User Name: Mandatory. The sign-in username.
First name, Last Name, Title, Email Address
Local Password: The local, VOSS system password (the password specified when the user is manually added or provisioned in VOSS)
Role: Mandatory. This user's role (which will determine their menu layouts and dashboards). Available roles include those with the current hierarchy in the Permitted Hierarchy Types list. See Role-based dashboards and menus.
For a provider, reseller, customer, or site administrator or operator, the available roles are limited to those applicable to the hierarchy level. For an intermediate node administrator or operator, the available roles are limited to those associated with the nearest non-intermediate node above the intermediate node in the hierarchy. For more details on roles, see Role-based dashboards and menus.
Entitlement Profile: A profile that specifies devices and services that may be assigned to a user. This setting may not be available for Admin users.
Language: User's preferred language.
If you don't choose a language, the language is inherited from the nearest hierarchy node (at or above the user's hierarchy) that has a default language configured. If no default language is configured anywhere in the hierarchy at or above this admin user, their preferred language is set as English.
If you're choosing a language on the Admins page, the language remains unchanged even if the admin user is moved to a different hierarchy. However, if language is inherited, the admin's language changes if they're moved to a different hierarchy, to the default language at that new hierarchy.
accessed via VOSS Phone Services. See Configure phone services for details. This setting may not be available for Admin users.
Authentication Method: The type of authentication that will be used. See User Authentication Methods. Options are:
For user authentication method (Auth Method) changes when updating, see Authentication Method Setting Rules.
LDAP Server: Displays only when authentication method is LDAP. The LDAP server the user must authenticate against.
LDAP Username: Displays only when authentication method is LDAP. The login attribute of the associated LDAP device model instance.
SSO Identity Provider: Displays only when authentication method is SSO. The entity ID of the SSO Identity Provider.
SSO Username: Displays only when authentication method is SSO. The name identifier used for an SSO authenticated user. Defaults to VOSS username.
Sync Source: Read-only. User's sync source. Sync source is "Local" when the user is created on VOSS. The application from which the user (and user data) was synced, that is, LOCAL (VOSS), UCM, MS-LDAP. Sync source determines the the master of the data. Data in the user mode will be derived from the fields of the master application (for example, CUCM, CUC, MS-LDAP). Default is LOCAL.
Sync Type: The user's sync type. Identifies the user type that was synced from the device as indicated by sync source information, for example CUCM-Local, CUCM-LDAP, LOCAL. Default is LOCAL.
User Type: Read-only. The user's login type. Default is Admin. Determined by the role interface (administration or selfservice). User types may be one of:
See Authorized Admin Hierarchies and Roles under Introduction to role-based access
Authorized Admin Hierarchy: Selected for users with multiple user roles to enable admin capabilities for end users or for admins who have permissions to a restricted set of hierarchies. See Authorized Admin Hierarchies and Roles
Related topics
Account Information tab/panel
This section describes user account information settings.
Provisioning Status tab/panel
This tab/panel is relevant only to end users. Provides a read-only view of a user's provisioning status, including multi-vendor provisioning (if applicable).
Select the Provisioned checkbox to view additional UCM's if applicable.
If the user is added to an LDAP server (see the LDAP section below), then the provisioning status will also show the server at the LDAP field.
Contact Information tab/panel
This tab/panel is relevant only to end users.
Defines contact information for the user, such as employee number, employee type, country, state, state, street, department, manager, Fax number, directory URL, Jabber ID, telephone number, mobile, and IP phone.
Hybrid Status tab/panel
This tab/panel is relevant only to end users and is available if the Global Setting Enable Cisco / Microsoft Hybrid is enabled on the Enabled Services tab/panel in the Global Settings. See Global Settings.
For details on the Hybrid Status tab and managing hybrid users, see: Cisco-Microsoft Hybrid Users.
Assigned Lines tab/panel
This tab/panel is relevant only for hybrid multi vendor scenarios. The fields are blank by default.
The fields on this tab are used to capture line details for users set up with an integrated service between two vendors (for example, Cisco and Microsoft).
Services tab/panel
This tab/panel is relevant only to end users, and provides direct links to the user's services, typically only their available and enabled services, which may include Cisco UCM user, CUC user voicemail, Webex App user, Pexip, UCCX Agent, MS 365, MS Teams, or MS Exchange. Clicking on the link for the service opens the settings for that service. For example, clicking the link for MS Exchange user opens the user's User Mailboxes settings page.
Note
You can choose to show or hide disabled services via the Enabled Services tab in the Global Settings.
Custom tab/panel
This tab/panel is relevant only to end users. User defined customized strings and booleans.
LDAP tab/panel
If a user is added as a Microsoft Active Directory LDAP user; then:
If a secure Microsoft Active Directory LDAP server (port 636) is configured higher in the user hierarchy and the server has Enable Write Operations checked, user details can be managed on the server if it is selected from the LDAP Server drop down list.
Only secure LDAP servers are listed. If no suitable servers have been set up, then the tab will not display any fields.
If no such Microsoft Active Directory LDAP server is configured and enabled, the tab will show a message to indicate this.
For setup server details, see:
LDAP Server in the Core Feature Guide
If the Microsoft Active Directory LDAP server is configured and the user already exists on this server, the tab will show a message to indicate this.
The Description field will display in the Microsoft Active Directory Users and Computers interface.
The User Account Control dropdown supports the following UserAccountControl values (associated with codes):
Important
When the LDAP user is added, the User Details tab/panel will show the Sync Source and Sync Type of the user as LDAP.
For details on updating and deleting the user on the LDAP server (Delete from LDAP, Push to LDAP), see Additional user settings.
Note
Additional user settings (More Actions)
The System User Details user management page (relation/User) contains a More Actions overflow menu that provides additional tools for managing users.
The table describes additional user management functionality available in the More Actions overflow menu:
| Align Hierarchy to Sync Source | For example, if the user's sync source is UCM, the data/User is at Customer level, and the UCM user is at Site level, then the data/User instance will be moved from the Customer level to the Cisco UCM's hierarchy, that is, to the Site level. |
| Align Hierarchy to User | All other related instances of the user (e.g. UCM, device/cucm/User, device/cuc/user, etc.) will be moved to the hierarchy of the data/User instance. |
| Delete From Ldap | Relevant only for Microsoft Active Directory LDAP server. The delete transaction succeeds only for users on Microsoft Active Directory LDAP servers on port 636, where the Enable Write Operations setting is checked. Thus, if Write operations are enabled on the associated LDAP server and the LDAP server is a secured Active Directory LDAP server, the LDAP user (device/ldap/user) is removed, and the Automate user (data/User) is updated, that is, the sync type (source) is set to LOCAL to reflect LDAP removal. If there is an associated Cisco UCM user, the UCM user and the Automate user are updated. In this case:
|
| Push To Ldap | Creates an LDAP user (if the LDAP user does not exist). Requires availability of an LDAP server that allows write back and is configured as a secure Microsoft Active Directory server. This server must be on port 636, with Enable Write Operations checked. Used when adding user details on the LDAP form tab for the first time and first adding the LDAP user. Clicking the Save button when you're done also updates the LDAP user details on the LDAP server. However, if any user details have been updated for the LDAP server, this Push To Ldap menu option will also save these. On the Users list view:
This menu option can't be used for Automate LDAP-synced users (in which case a system message on the LDAP tab displays the following error message: Push to LDAP is not allowed). |
Related topics
The User model for user details that correspond with Cisco Unified Communications Manager and Cisco Unity Connection server.
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| User Details | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| User Name * | User's Username. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| First Name | The User first name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Last Name | The User last name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Display Name | Display name of the user |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Title | Title. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Email Address | The User email address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Primary Line |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Local Password | The User password. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Role * | The role to which the user belongs. See: Role. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Entitlement Profile |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Language | The preferred language for this user. Default: en-us |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Set by Default Language | Indicate if the user's language is set by language default in the hierarchy. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Exclude from Directory | Exclude from Directory flag to control the Phone Services directory lookup. If set to true the User's phone number will not appear in the directory lookup. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Auth Method | The type of authentication that our user would be using. Typically this would be choices between a Standard VOSS 4 UC user, an LDAP user or an SSO user. Default: Local |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| LDAP Server | A reference to the LDAP server which this user must authenticate against. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| LDAP Username | The login attribute of the associated LDAP device model instance |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| SSO Identity Provider | The entity id of the SSO Identity Provider. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| SSO Username | The name identifier that is used for an SSO authenticated user. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Sync Source | Sync source of the user. Identifies where the user was synced from. This value will determine the master of the data. The data in the User model will be derived from the fields of the master application (E.G. CUCM, CUC, MS-LDAP). Default: LOCAL |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Sync Type | Sync type of the user. Identifies the user type that was synced from device as indicated by Sync Source information, e.g. CUCM-Local, CUCM-LDAP, LOCAL. Default: LOCAL |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| User Type | Indicate the user's login type. Default: Admin |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Hybrid Status |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Authorized Admin Hierarchy | A reference an Authorized Admin Hierarchy instance that defines this user's administrative capabilities. This enables administrative capabilities for end users. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Account Information | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Account Information | Additional account information for the given user. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Change Password on Next Login | Indicates if the user must be forced to change their password the next time that login. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Credential Policy | Specifies the policy with the rules used to govern this user's credentials. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Disabled | Indicates if the account has been disabled to prevent the user from logging in until an administrator enables the account again. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Reason for Disabled | A description of why the account is disabled. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Time Locked Due to Failed Login Attempts | The time when the user account was locked as result of the number of failed login attempts exceeding the permitted thresholds. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Time of Last Successful Login | The time the user last logged in successfully. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Locked | Indicates if the account has been locked to prevent the user from logging in. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Number of Failed Login Attempts Since Last Successful Login | The total number of failed login attempts since last successful login. Default: 0 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Time of Last Password Change | The time when the password was last changed. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Time of Last Password Change By User | The time when the password was last changed by the user. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| License Audit Details | License Audit Information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| License Audit Status | The License Audit status of the user. Default: Unknown |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Last Checked | The last time the License Audit Details were updated. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Contact Information | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Employee Number | Employee number of the user |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Employee Type | Employee type |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Country | Country name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| State | Contains full names of state or province. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| City | Contains the name of a person's locality. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Building Name | Building name or number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Street | Contains site information from a postal address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Postal Code | Contains code used by a Postal Service to identify postal service zones. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Department | Department names and numbers. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Manager | Manager. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Directory URI | Alphanumeric Directory URI (e.g. SIP URI) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Jabber ID | Jabber ID |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Physical Delivery Office Name | Physical Delivery Office Name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Unverified Mail Box | Unverified Mail Box. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Home Phone | Contains strings that represent the user's home phone number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Telephone Number | Telephone Number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Facsimile Telephone Number | Contains strings that represent the user's facsimile telephone Number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Mobile | Contains strings that represent the user's IP mobile number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| IP Phone | Contains strings that represent the user's IP phone number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Other Mailbox |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Organizational Unit | The name of the person's organization unit. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Member Of | The user can be a member of a variety of groups. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Object Class |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Assigned Lines | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extensions | Extensions to select primary details from. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Line |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Line E164 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Class of Service |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Custom | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 1 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 2 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 3 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 4 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 5 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 6 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 7 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 8 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 9 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom String 10 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 1 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 2 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 3 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 4 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 5 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 6 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 7 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 8 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 9 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom List of Strings 10 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 1 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 2 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 3 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 4 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 5 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 6 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 7 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 8 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 9 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Custom Boolean 10 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||