Skip to main content
P
PV_110290844-Participant
4-Participant
May 4, 2026
Question

SCM ThingTemplate access control

  • May 4, 2026
  • 2 replies
  • 42 views

I have 2 user groups which need to access the SCM page for things belonging to different ThingTemplates. User Group A should access only things from ThingTemplates ABC_1, ABC_2 and ABC_3; whereas User Group B should access only things from ThingTemplates XYZ_1 and XYZ_2. And all ThingTemplate inherit a BaseTemplate.
 

How do I manage access levels based on ThingTemplate?

2 replies

N
nmutter16-Pearl
16-Pearl
May 5, 2026

Would the normal ThingWorx permission model not already apply to that scenario: If user only has visibility permission for specific thing templates (Instance visibility) they should also not see them in SCM deployment target list. I did not have this scenario yet so I am not exactly sure how this will behave.

Or should both groups see all asset but only in SCM not being able to deploy to them?

 

C
CharlesJiCommunity Manager
Support
May 28, 2026

Hi ​@PV_11029084, 

 

User Group A should access only things from…

I'm not sure what the “things” mentioned here refer to, but in SCM, you can use access control on packages to define which user groups have specific permissions (e.g., View & Deploy or Delete) for each package.

https://support.ptc.com/help/thingworx/utilities/r9/en/index.html#page/ThingWorx_Utilities/AssetsforDeployment.html

 

If you are referring to the deployment target (asset list), I would recommend using the Saved Search Criteria filter to achieve your goal:
https://support.ptc.com/help/thingworx/utilities/r9/en/index.html#page/ThingWorx_Utilities/EnhanceAssetSearch.html

Terms & ConditionsAccessibility statement