---
title: "Web Vision | Permissions Example | N3uron KB V1.22"
slug: "web-vision-example-permission-configuration"
description: "Follow a Web Vision example to control access to application sections by user role, using properties and expressions to manage element visibility."
updated: 2026-10-07T15:01:05Z
published: 2026-10-07T15:01:05Z
canonical: "docs.n3uron.com/web-vision-example-permission-configuration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.n3uron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Permission configuration

## **Restricting Access to Specific WebVision Application Sections by Role**

To make certain parts of a WebVision application accessible only to specific roles, follow these steps:

### **Backend Restrictions**

Configure the [**Access**](https://docs.n3uron.com/v122/docs/web-vision-configuration-1#access-configuration) section in WebVision by adding one or more filters to specific parts of the **Data Model**. These filters will restrict access to designated areas of the application at the backend level.![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/AccessByRole.png)

### **Frontend Restrictions**

Limit access in the WebVision user interface by using the [**ui("user.roles")**](https://docs.n3uron.com/v122/docs/web-vision-input-helpers-1#link-ui) expression. This function returns the logged-in user's role, enabling dynamic control over which sections of the interface are displayed based on the user's assigned role. To customize the user visualization based on their role, start by creating a **Region** in the **StartUp** window or any other relevant screen. Within the Region, configure the **'Shown Child'** property to include an expression that evaluates the system variable **ui("user.roles")**. This expression allows you to compare the logged-in user’s role with the client-specific role and dynamically select the appropriate visualization. This approach ensures that each user sees the interface tailored to their assigned role.

- ```javascript
// Define a mapping object for roles and their corresponding visualizations
const roleVisualizationMap = {
    "RoleA": "ScreenRoleA",
    "RoleB": "ScreenRoleB",
    "RoleC": "ScreenRoleC",
};
// Get the user's roles
const userRoles = ui("user.roles");
// Return the visualization for the first matching role, or a default visualization
return roleVisualizationMap[userRoles] || "DefaultVisualization";
```

- ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/JavascriptExpression.png)

Another option is to directly assign the **Region** **Shown Child property** to the return value of [**ui("user.roles")**](https://docs.n3uron.com/v122/docs/web-vision-input-helpers-1#link-ui), and then name the containers instantiated within the Region to match the roles defined in the system.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/AccessByRole03.png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/AccessByRole02(1).png)

[Web Vision Full Product Details](https://n3uron.com/iiot-platform-modules/web-vision/)