Extension Visibility
Under Extension and Trunk > Client Permission > Extension Visibility, you define which extensions are visible to specific users or extension groups in the UC Client. This allows you to control whether a user can see other extensions, for example, in the phonebook, on BLF keys, or in the presence display.
Access Extension Visibility
- Log in to the Cloud PBX administration portal.
- Navigate to Extension and Trunk > Client Permission.
- Select the Extension Visibility tab.
Overview
The rule overview displays all configured extension visibility rules:
| Column | Description |
|---|---|
| Extension/Extension Group * | The extension or extension group this rule applies to. |
| Permission Type * | The type of permission: Allow view or disallow view. |
| Objects * | The extensions or extension groups are defined as visible or invisible (e.g., Default_All_Extensions or individual extensions). |
| Move | Arrow icons to change the rule priority (move up/down). |
| Operations |
Add a Rule
Click + Add rule to create a new visibility rule. Select the extension or extension group, the permission type, and the objects (visible/invisible extensions).
Rule Priority
When multiple rules apply to the same extension, the order determines the outcome. Rules higher in the list have higher priority. Use the arrow icons in the Move column to adjust the order.
Edit or Delete a Rule
Click the edit icon () to modify an existing rule. To remove one or more rules, select them using the checkboxes and click Delete, or use the delete icon (
) in the respective row.
Important Notes
- Order matters: When rules conflict, the rule with the higher position (further up) takes precedence. Place restrictive rules above permissive rules.
- Scope: Visibility rules affect all areas of the UC Client where extensions are displayed — e.g., the contact list, BLF keys, and presence display.
- Extension groups as objects: In the Objects field, you can select both individual extensions and extension groups (e.g., Default_All_Extensions).
Comments
0 comments
Article is closed for comments.