Skip to main content
vmedvedev1-Visitor
1-Visitor
October 25, 2017
Solved

Restricting visibility between users and things in the organization

  • October 25, 2017
  • 3 replies
  • 2560 views

I have assets and users with visibility set to the same organization. As I understand all user from the organization can see all assets. I have requirement that every user could see only some subset of assets from the organization that is configurable run-time. How I will achieve this? Should I create for every asset  user group, say,  <AssetName>_DisableAccess_Group, put users why are not allowed to see asset into this group and configure run time permission for asset disabling all  read/write, execute, subscribe operations for this group? Or there is another way to achieve this?

Thank in advance,

Vladimir Medvedev

Best answer by PaiChung

Just create appropriate Organizational subunits.

Either each user is their own unit or if you can group the devices, then create a unit per group and then assign the Users or User Groups to the appropriate Units

then assign those units to the appropriate entities in Thingworx.

3 replies

PaiChung22-Sapphire IAnswer
22-Sapphire I
October 26, 2017

Just create appropriate Organizational subunits.

Either each user is their own unit or if you can group the devices, then create a unit per group and then assign the Users or User Groups to the appropriate Units

then assign those units to the appropriate entities in Thingworx.

vmedvedev1-VisitorAuthor
1-Visitor
October 26, 2017

Thank you for the quick response. As I can have thousands assets and few users so it is better to assign users to separate sub units. Just another quick question. Organization could have child organization with own set of assets and users. To give users from parent organization ability to see the assets from child organization I need to add to child asset visibility property user sub units  from the parent organization. Will it work or I need to do something else.

Thanks again,

Vladimir Medvedev

PaiChung22-Sapphire I
22-Sapphire I
October 26, 2017

In Thingworx visibility inherits up the structure.

So Users who need to see assets in all child nodes, should be assigned to the parent node.

Terms & ConditionsAccessibility statement