You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 22, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: _includes/docs/pe/user-guide/groups.md
+61-1Lines changed: 61 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,12 +97,72 @@ For example, let's create an action to quickly go to the dashboard with full inf
97
97
98
98
{% include images-gallery.html imageCollection="action-configuration" showListImageTitles="true" %}
99
99
100
-
### Batch operations
100
+
### Group permissions
101
+
Use the Permissions tab to define who can access the entities inside this group and what actions they can perform.
102
+
A permission links a Group role to a User group and applies only to the entities inside this group.
103
+
Permissions supplement tenant-wide RBAC and do not override global restrictions. See [Group roles in RBAC](/docs/{{docsPrefix}}user-guide/rbac/#group-role){:target="_blank"}.
104
+
105
+
**How to add group permissions:**
106
+
- Open **Entity group details** → **Permissions** tab.
107
+
- Click "**+**" (Plus icon) to add a group permission.
108
+
- Select **Role** (Group role) from dropdown list.
109
+
- Select **User group owner**[Tenant](/docs/{{docsPrefix}}user-guide/ui/tenants){:target="_blank"} or a specific [Customer](/docs/{{docsPrefix}}user-guide/ui/customers){:target="_blank"}, and **User group**
110
+
- Click "**Add**" to save. The group permission appears in the table.
111
+
112
+
You can **Edit** or **Delete** existing group permissions at any time from **Permissions** tab:
113
+
-**Edit**: click "**Edit**" (pencil icon) of the target permission → update fields → "**Save**".
114
+
-**Delete**: click "**Delete**" (trash icon) of the target permission → "**Confirm**".
115
+
116
+
Changes take effect immediately for all members who can access the group.
117
+
118
+
To review assigned permissions from the [user side](/docs/{{docsPrefix}}user-guide/ui/users/#assigning-permissions-to-user-group): Open **Users group** details → **Roles** tab.
119
+
120
+
## Batch operations
101
121
102
122
Over each entity of the group, you can perform operations such as: change the owner of the entity, move it to another group, add or remove an entity from the group.
103
123
104
124
{% include images-gallery.html imageCollection="batch-operations" showListImageTitles="true" %}
105
125
126
+
## Share entity group
127
+
128
+
Sharing a group provides access to all entities inside the group at once and creates a permission entry that links this entity group to the selected user group.
129
+
130
+
**How to share an entity group:**
131
+
- In **Groups** tab, click "**Share**" icon in the row of the target group.
132
+
- Choose [**Customer**](/docs/{{docsPrefix}}user-guide/ui/customers/){:target="_blank"} from dropdown list.
133
+
- (Optional) Enable **All users** checkbox to provide access to every user of that customer.
134
+
- Choose the Permissions access: Read, Write, or Other (Roles).
135
+
- Click "**Share**" to apply. The access is propagated to all entities within the group.
136
+
137
+
To update or revoke access, open the group [permissions](#group-permissions) tab and edit/delete the corresponding permission.
138
+
139
+
## Make group public or private
140
+
141
+
Public groups provide read-only access to anyone (no sign-in). Use it for non-sensitive data only. When you set a group as Public,
142
+
the platform adds permissions to that entity group for the Public customer’s "Public users" group.
143
+
144
+
**Make public:**
145
+
146
+
- In the **Groups** tab, click "**Make public**" icon of the target group.
147
+
148
+
- Confirm in the dialog.
149
+
150
+
The Public checkbox becomes enabled for this group.
151
+
152
+
{% capture public %}
153
+
**Note:** Public dashboards that use device data, require the dashboard and the related device group must be public.
154
+
{% endcapture %}
155
+
{% include templates/info-banner.md content=public %}
156
+
157
+
**Make private (revoke public access):**
158
+
159
+
- In the Groups tab, click "**Make private**" icon of the target group.
160
+
161
+
- Confirm in the dialog. Public access is removed.
162
+
163
+
If you need controlled access for specific customers or users, use [Share entity group](#share-entity-group)
164
+
or configure entries on the [Permissions](#group-permissions) tab.
165
+
106
166
## Delete entity group
107
167
108
168
You can delete an entity group along with all its entities using one of the following ways:
Copy file name to clipboardExpand all lines: _includes/docs/user-guide/widgets.md
+27-4Lines changed: 27 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,7 +152,7 @@ A data key identifies the telemetry, attribute, or entity field a widget should
152
152
153
153
<b><fontsize="3">Sources of keys</font></b>
154
154
-**Attributes** — the combined set of Client, Server, and Shared [attributes](/docs/{{docsPrefix}}user-guide/attributes/){:target="_blank"} of the selected entity. If a needed attribute doesn't exist yet, you can still add the key; the widget will show data once the device reports it.
155
-
-**Time series** — telemetry keys reported by devices or written by the Rule Engine / [REST API](/docs/{{docsPrefix}}reference/rest-api/){:target="_blank"}.
155
+
-**Time series** — telemetry keys reported by devices or written by the [Rule Engine](/docs/{{docsPrefix}}user-guide/rule-engine-2-0/overview/){:target="_blank"} / [REST API](/docs/{{docsPrefix}}reference/rest-api/){:target="_blank"}.
156
156
-**Entity fields** — metadata fields that depend on entity type and may evolve over time (e.g. created time, entity type, name, type, label).
157
157
158
158
The data keys list for data source depends on the [widget type](/docs/{{docsPrefix}}user-guide/widgets/#widget-types){:target="_blank"}:
@@ -222,9 +222,9 @@ Let's look at the basic data key settings an example of the "Entities table"
222
222
223
223
{% include images-gallery.html imageCollection="data-key-configuration-color" %}
224
224
225
-
-**Use data post‑processing function** — enable a custom function to transform raw values before display.
225
+
-[**Use data post-processing function**](#data-post-processing-function) — enable a custom function to transform raw values before display.
226
226
227
-
**Aggregation of key**
227
+
##### Aggregation of key
228
228
229
229
By default, the Latest values widgets do not have the time window. If you enable aggregation for any data
230
230
key in the **Latest values** widgets, the time window control will appear. You can set up aggregation for each telemetry
@@ -305,7 +305,30 @@ This option allows you to specify how the result should be displayed:
305
305
306
306
-**Delta (percent)** - Displays the result as a percentage relative to the previous interval <br>formula: **(IntervalValue - prevIntervalValue)/prevIntervalValue*100**
307
307
308
-
**Use data post-processing function.** The data post-processing function allows changing the output data depending on your wishes. To use data post-processing function, you must check the "Use data post-processing function" checkbox and enter the function in the field below. Then click the "Save" button in the lower-right corner.
308
+
##### Data post-processing function
309
+
The data post-processing function enables real-time transformation of incoming telemetry values before they are displayed
310
+
in widgets. This feature allows you to apply custom JavaScript logic to each data point — for example, convert units,
311
+
filter out anomalies, or calculate derived metrics without touching upstream sources.
312
+
313
+
**How to use:**
314
+
- In the widget → go to section with **Data keys** → click the **Pencil** icon of the target data key.
315
+
- Enable toggle **Use data post-processing function**.
316
+
- Enter your code in the function body. The platform automatically injects the function header:
0 commit comments