thingsboard/thingsboard

ThingsboardCE 3.3.4.1 : Is it possible to create users with different access levels ?

Open

#15,882 opened on Jul 1, 2026

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Java (6,302 forks)batch import
help wantedquestion

Repository metrics

Stars
 (21,744 stars)
PR merge metrics
 (Avg merge 11d 7h) (95 merged PRs in 30d)

Description

Good morning,

I am using thingsboardCE 3.3.4.1. I have created a dashboard displaying two entity tables. The 1st entity table : Displays assets linked to the connected user. The 2nd entity table : Displays devices linked to the selected assets.

In the 2nd entity table, on each row (displaying one device), there is a button at the end of line. If user clicks the button, a popup appears showing all the shared attributes of the selected device.

At the moment, for all the users I have created, each users can see all the parameters of the selected device in the popup menu.

I would like to know if I could create users with different access levels ? I would like to used the access level in order to choose which shared attribute the user can see in the popup menu. Is it possible ? => The popup menu has been designed using IA : It is made in HTML/CSS I think.

Thank you for your help, this is really important. Best regards,

Contributor guide

Research direction
Investigate Thingsboard's role based access control (RBAC) system to determine if custom user roles can be created to restrict visibility of shared attributes in dashboard widgets. Consult documentation on permissions and entities.
Tech stack
javajavascripthtmlcss
Domain
backendfrontendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70