Full permissions in sandbox project, no permissions in all other projects

[bbeuckSIG]

Dear Thingworx Community,

a new colleague has joined our company and we are currently introducing him to Thingworx. My idea is to create a sandbox project solely for him where he can do and test whatever he wants, with full permissions. But he should NOT be able to save any test entities to other projects, neither should he be able to modify existing entities from other projects.
Is this possible? If yes, how?

Thank you
Benny

[rosharma]

In Thingworx composer, under modelling section we have Projects. through that we can create separate projects particularly for that user, can add entities which we want that user to work on. through entities tab drag those entities that need to be worked upon and finally providing permissions to it.

[bbeuckSIG]

Thanks for your feedback, @rosharma .

Clear so far. But how do I grant new users the permission to create new entities (Things, ThingTemplates, Mashups etc.) within their project but prohibit them to move their entities to another project (or remove project assignment)?

Thanks

Benny

[rosharma · Accepted solution]

basically projects are used for managing the entities which will help users to export and import as that would happen in bunch.

Projects are used to organize entities within ThingWorx. Entities that are collected in projects can be exported and imported together. An entity can belong to only one project.

You can refer help center link for more details on projects

http://support.ptc.com/help/thingworx_hc/thingworx_8_hc/en/#page/ThingWorx%2FHelp%2FComposer%2FThingWorxProjects.html

now coming back to your scenario, here project won't come into picture. though you can use for good structuring the entities. In your case here,

first you need to provide all collection permissions on entities ( things, thing shapes, thing templates , mashups etc) to both the users so that both users are able to create and manipulates with those sets of entities . now to restrict one of the user from for ex one mashup . open the mashup , go to permissions-- in runtime and design time permissions add the user and use deny ( cross buttton) options to set those. in this way the user who is restricted won't be able to do anything with mashup. but keep in mind all users would be able to view entities because there is no such option to deny the visibility. but runtime and design time would work. restricted user once clicks on mashup to view/edit -it will show unauthorized error pop up.

i hope this clears and helps.

[bbeuckSIG]

Thank you for clarifying, @rosharma . It looks like projects are not whay I am looking for. Your suggestion also seems not to be viable for us, too much overhead. I will try to figure out an organizational solution rather than technical.

Thank you

Benny

[slangley]

Hi @bbeuckSIG.

If the previous response helped you to find a solution, please mark it as the Accepted Solution for the benefit of others with the same question.

Regards.

--Sharon