Info

Sometimes you may need to block certain users from accessing specific menu options on the phone or web interface.

For example, you might want to set a default ringtone and prevent users from changing it in the phone’s settings.

To do this, you’ll use the User Access Level settings, which let you hide or lock menu items in both the phone UI and the web UI.

To get started, you’ll need to create a configuration file for the phone to reference and turn on a few security options.

Understanding the Access Levels

Yealink phones control who can see or change different settings using a file called WebItemsLevel.cfg.
Each line in that file sets permissions for one specific setting, using this format:

ItemName = XY

For Access Level item names you will need to reference the Yealink document called "Description of Configuration Parameters for User Access Level" spreadsheet.

By turning on these features, you’re basically defining what each user level (user, var, admin) can see or change on the phone, based on the permissions set in the WebItemsLevel.cfg file.

X defines who can access the setting:

• 2 = admin

• 1 = var (like an installer or advanced user)

• 0 = user

• 3 = none (no access at all)

Y defines what kind of access they have:

• 0 = writable for X and higher levels

• 1 = read-only for X, writable for higher levels

• 2 = read-only for X and higher levels (only the very top level can edit)

• 3 = read-only for everyone at X and above

So basically, X sets the minimum role that can see or edit the item, and Y fine-tunes whether it’s editable or locked for that role or higher.

The following table provides the possible values for XY:

(W: writable; R: read-only; N: hidden

Creating the Web Items Level Config File

Phone UI Configs

In our example, we will be turning off the wallpaper menu item on the phone. 

Open a text editor like Notepad or Notepad ++

At the top of the document type [ GUI ]

Below this you will enter in the configuration parameters that you want to change on the phone's UI

You will need to reference the Yealink document called "Description of Configuration Parameters for User Access Level"

In our example, we'll enter display_wallpaper and the value of the access level, in our case 2

This will set the Menu > Basic Settings > Display > Wallpaper option to hidden for the user and var, but writable for the admin (if they log in). 

Continue adding configurations until you are finished

Web UI Configs

Just as the examples above for the Phone UI Configs, you will enter configuration parameters and access permission values into the same text document. 

You must first start with a section header (these are referenced in the same sheet as above) for the configuration parameter you're working with. 

For example, if I was working with disabling adding a wallpaper from the Web UI, I would use [ Settings-Preference ] at the top of the configuration parameters, e.g.:

Configure the Endpoints

The next thing you'll have to do is host the WebItemsLevel.cfg file and point the endpoints at it. 

Host the file so it is accessible to the phone, in my case I'll use one of our provisioning servers. 

Then you'll need to give some configurations to the phone(s) as well:

security.var_enable="1"
security.default_access_level="0"
web_item_level.url="https://URL-WHERE-THE-FILE-IS-HOSTED.com/WebItemsLevel.cfg"

security.var_enable

security.default_access_level

web_item_level.url

Sync the phone so it will get the new configs and download the WebItemsLevel.cfg file, it will reboot.

Lastly, test to see if the menu items are accessible or not.

Caveats

Admin users will notice that they cannot log into the phone like normal using the admin password. They will need to change the UserMode on the phone first: