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
Description
I have multiple Edge CE instances deployed in different locations and one central platform that control all of them. I want to give tenant_admin permissions in a specific edge instance to a user, but i don't want to have access as tenant_admin in the central platform.
As i see, i can only create a customer and assign to specific edge instance, but that users appears as client also in edge.
Is this feature available?
Thanks in advance.
Disclaimer
We appreciate your contribution whether it is a bug report, feature request, or pull request with improvement (hopefully). Please comply with the Community ethics policy, and do not expect us to answer your requests immediately. Also, do not treat GitHub issues as a support channel.
The text was updated successfully, but these errors were encountered:
this is not possible at the moment and I'm not sure that we are going to add this feature in the future.
I would consider to install ThingsBoard CE on your remote locations as well and push only to central ThingsBoard CE required data using external rule nodes or some additional services that are implemented by you.
Description
I have multiple Edge CE instances deployed in different locations and one central platform that control all of them. I want to give tenant_admin permissions in a specific edge instance to a user, but i don't want to have access as tenant_admin in the central platform.
As i see, i can only create a customer and assign to specific edge instance, but that users appears as client also in edge.
Is this feature available?
Thanks in advance.
Disclaimer
We appreciate your contribution whether it is a bug report, feature request, or pull request with improvement (hopefully). Please comply with the Community ethics policy, and do not expect us to answer your requests immediately. Also, do not treat GitHub issues as a support channel.
The text was updated successfully, but these errors were encountered: