Administration

EasyUC users, access types and location access

Create accounts for the administration interface and define what they may see and change.

EasyUC · Version 4.8.7

In EasyUC: EasyUC Cisco → Administration → Access & Appearance → Administrators & Roles

Images come from the EasyUC lab. Names and example values provide orientation. A different interface language is indicated beside the relevant image.

What it is for

EasyUC users are the accounts with which administrators, template managers and helpdesk staff sign in to the administration interface. They are separate from the CUCM end users, who work in the end-user portal.

Every account has an Access type. Individual permissions / Helpdesk (ROLE_APP_USER) receives only the permissions that you select individually or assign through a permission template, and sees only the allowed clusters and locations. Template administrator (broad access) (ROLE_APP_TEMPLATE) has broad access within the allowed clusters. Administrator (full access) (ROLE_APP_ADMIN) may do everything, including the administration. The owner account (ROLE_OWNER) is created during installation and can be neither edited nor deleted in this list.

An account is either local (password in EasyUC) or bound to a CUCM end user. For bound accounts, EasyUC checks the password against the CUCM at sign-in.

Prerequisites

An account with the access type Administrator (full access) (ROLE_APP_ADMIN) or the owner account (ROLE_OWNER). Only these accounts see the Administration menu.
For the user type Enduser: an active CUCM module and an enabled CUCM connection in which the end user exists.
For restricted accounts: at least one enabled CUCM connection and the locations the account is to access.
If global two-factor sign-in is switched on, every account needs a reachable e-mail address.

Step by step: creating an account with individual permissions

Open the EasyUC Cisco workspace.
In the menu, select Administration → Access & Appearance → Administrators & Roles. The page is called Manage EasyUC Users.
Click Create EasyUC User at the top right.
Under User Type, select either Local User or Enduser.
Only for Enduser: select the Enduser Connection and then the CUCM user under Enduser. EasyUC enters Username and E-mail from the CUCM.
Leave Access type set to Individual permissions / Helpdesk.
Enter Username and E-mail. For a local account additionally First Name, Last Name, Password and ReType Password.
Under Set permissions, select either Individual permissions – for this user or a Linked template. With a template, the following three steps are locked because the template specifies them.
Tick Read only if required.
Under Clusters and locations, select the allowed clusters in the Connections field. For each cluster, mark Default Cluster and either All Locations or individual entries under Locations.

Original view for this guide Go to step 10
The new account uses the “Individual permissions / Helpdesk” access type here. Restrict access in the cluster and location section. Account fields are empty in this example; no user has been created.

EasyUC · Lab/demo environment Interface screenshot in German
EasyUC access and permissions

Empty EasyUC user form with access type, permission mode and cluster assignment. Personal details and password are blank; no account was created.
In the Permissions area, select the task area and tick the allowed actions.
Click Save. The window closes and the account appears in the list.

Step by step: changing or deleting an account

Open Administration → Access & Appearance → Administrators & Roles.
Find the account with the search field in the Name column, or filter by a location in the Connections column.
Click Edit in the row. The window Update EasyUC User opens.
Change the master data, password (local accounts only), template, clusters, locations or individual permissions. The access type is only displayed and cannot be changed afterwards.
Click Save.
To remove the account, click Delete in the row and confirm the prompt Are you sure?.

Fields and options

Fields and options
Field / action	Meaning and use
User Type	Local User creates an account with its own password. Enduser binds the account to a CUCM end user and appears only when the CUCM module is active. Default: Local User.
Enduser Connection / Enduser	Only for the type Enduser: the CUCM connection and the user to which the account is bound.
Access type	Individual permissions / Helpdesk, Template administrator (broad access) or Administrator (full access). Default: Individual permissions / Helpdesk. Selectable only at creation.
Username	Sign-in name. Required.
E-mail	Address of the account. The code for two-factor sign-in is sent to it.
First Name / Last Name	Local accounts only. For bound accounts, the names come from the CUCM.
Password / ReType Password	Local accounts only. Required at creation. Leave empty when editing to keep the password.
Set permissions	Individual permissions – for this user or Linked template: <Name>. Only for the access type Individual permissions / Helpdesk.
Read only	Allowed areas remain visible, changes to managed data are blocked. Default: off.
Connections	Clusters the account may access. Without a cluster, the account cannot open any CUCM data.
Default Cluster	Cluster that is preselected after sign-in. The first cluster added automatically becomes the default.
All Locations / Locations	Either all locations of the cluster or a selection. When a cluster is added, All Locations is set.
Copy permissions from user once	Takes over the current permissions of another account. The accounts are not linked by this, and clusters and locations stay unchanged. Visible only without a linked template.
Save configuration as new template	Creates a permission template from the current selection and links the account to it.

Checking the result and narrowing down errors

For each account the list shows the access type, for linked accounts additionally Linked template: <Name> · Revision <number>, as well as clusters and locations. A green tick marks the default cluster.
The badge local or Enduser [connection] shows the kind of account. deleted from CUCM means that the bound CUCM user no longer exists. disabled means that the connection is switched off.
If the Connections column shows the value None, the account cannot open any CUCM data. Assign at least one cluster.
Message The user could not be saved. Check the marked fields.: a required field is missing or the server rejected a value. The affected fields are marked red.
Message The permission catalog could not be loaded.: close the window and open it again. As long as the catalog is missing, Save stays locked.
If a helpdesk account has no dashboard, this is intended as long as the permission View dashboard is not granted. EasyUC then starts on the first allowed page.
Test a new account by signing in with it yourself before you hand it over.