Integration with Other Applications > Digital Product Traceability > Configuring the Windchill Digital Product Traceability (DPT) Extension in ThingWorx > Permissions for ThingWorx Platform Entities
  
Permissions for ThingWorx Platform Entities
ThingWorx user profiles who configure the integration require the following permissions:
Thing or Thing Template
Runtime
Design
Visibility
OslcDataServicesThingTemplate
Service Execute: Yes to instances
NA
Yes to instances
OslcMappingConfigThingTemplate
NA
Read: Yes to instances
Yes to instances and itself
OslcFlowsTemplate
Service Execute: Yes to instances
NA
Yes to instances
OslcValidationFlowThing
Service Execute: Yes to itself
NA
Yes to itself
OslcValidationServicesThingTemplate
Service Execute: Yes to instances
NA
Yes to instances
Collection:Things
NA
Create: Yes
Read: Yes
Update: Yes
NA
ThingWorx user profiles using the Traces functionality require the following permissions:
Thing Template
Runtime
Visibility
OslcDataServicesThingTemplate
Service Execute: Yes to instances
Yes to instances
OslcMappingConfigThingTemplate
NA
Yes to itself
OslcFlowsTemplate
Service Execute: Yes to instances
Yes to instances
OslcValidationFlowThing
Service Execute: Yes to itself
Yes to itself
OslcValidationServicesThingTemplate
Service Execute: Yes to instances
Yes to instances
To know more about permissions, see the section Configuring Visibility and Permissions for ThingWorx Entities. For more information about the user profiles and organizations in ThingWorx, see the section Securing the Applications Built on the ThingWorx Platform Using Visibility and Permissions in the ThingWorx Platform Help Center.
* 
Refer to the documentation for your supported version of ThingWorx application.
Setting Up User-specific Permissions for Windchill RV&S and Windchill Modeler OSLC Servers
You can set up user specific permissions in the following ways. These instructions are applicable for IBM Rational Doors NG too.
• Create user groups for the following user profiles:
◦ Configurator
◦ End user
Create a unique user group for an end user profile specific to the configured external OSLC servers. For example:
▪ Create a user group RVS for an end user profile using Windchill RV&S OSLC server, and a user group Modeler for user profiles using Windchill Modeler OSLC server.
▪ Create a user group that includes user profiles common to RVS and Modeler user groups.
• Create units in Organizations specific to the user groups that you have created.
After creating a new configuration Thing, enable the Visibility permission of the Thing for a specific user group based on their user profile.
• Enable Visibility permission for the RVS user group to see a Windchill RV&S specific Thing.
• Enable Visibility permission for the Modeler user group to see a Windchill Modeler specific Thing.
After creating a new validation flow Thing, enable the Visibility and Service Execute permissions for appropriate user groups.
• Enable Visibility and Service Execute permissions for the Modeler user group to see and execute the Windchill Modeler specific validation flow Thing.
Since Windchill RV&S uses the default OSLC validation flow, no such permission is required for Windchill RV&S.