Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
22.5k Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

Roles

Role-Based Access Control (RBAC) in ThingsBoard provides a structured security model that governs what actions authenticated users can perform on entities and resources within the platform. RBAC ensures scalable, secure user access by defining roles with specific permissions and assigning them according to organizational needs.


In ThingsBoard Community Edition, the RBAC model is based on a fixed set of predefined authority levels used to manage access. Permissions are determined by built-in roles assigned directly to users.


Built-in roles
  • System administrator has full access to system-wide resources and settings and can create and manage tenants. This role does not own IoT entities.
  • Tenant administrator has full control over a specific tenant environment. This role owns and manages its IoT entities, including devices, assets, dashboards, customers, and other tenant entities.
  • Customer user has read-only access to the resources and data explicitly assigned by the Tenant Administrator.