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

Scope a User to Their Customer's Data

Restrict a customer user to see and manage only the entities belonging to their own customer, with no visibility into other customers. No entity groups are required — scope is controlled by where the Generic role is assigned.

Prerequisites: Basic familiarity with Roles and RBAC.

  1. Navigate to Customers & users ⇾ Roles.
  2. Click + Add role.
  3. Name: Customer Full Access — Role type: Generic.
  4. Add one permission entry: Resource All, Operations All.
  5. Click Add.
  1. Navigate to Customers & users ⇾ Customers ⇾ click Manage customer users for the target customer.
  2. Open Groups ⇾ open the target user group ⇾ Roles tab.
  3. Click Add — select Role type Generic, Role Customer Full Access.
  4. Click Add.

The user sees and can manage every entity belonging to their customer — and nothing outside it. Repeat Step 2 for each customer that needs this access pattern.