Is there a quick way to create a user group that has access to run everything but not have editing rights (composer rights) or do I have to create a group and then add it to everything that is run on the mashup?
In follow up to that. It is best to specifically permit the runtime and not mass permit the runtime, many of the runtime services can impact the design and should be kept secured.
The best way to approach this would be to always 'wrap' the standard services in your custom service. i.e. you are creating services that the users utilize that utilize the Thingworx standard services. Next you permit those custom services, and you apply the System User to all the standard services.
Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum!