Can we Hide or Not accessible the Pro/program relations in assembly for external user of that assembly?

[VinitKadamITT]

Can we hide or not accessible the Pro/program relations in assembly for external user of that assembly?

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[TomU]

Nope. If you have something you don't want getting outside your organization you either need to remove the information from the file (either manually or with custom software/3rd part utility) or send neutral data (STEP file, etc.).

[TomU]

You may want to consider keeping your business rules outside the models. This can be done with 3rd party software (SmartAssembly, NitroCELL, etc.) or custom J-Link/VB/Toolkit applications.

[VinitKadamITT]

Hello Tom,

Not accessible the Pro/program relations in assembly for external user of that assembly,

Here, external user of that assembly, means I have to say not editable for all other users than me.

Means, Users in my organization as well should not able to edit or change the relations written by me in perticular assembly & assembly skeleton. But that assembly in read only mode should be accessible by users in my organization in same, .asm format.

The perticular assembly is accessible for all proe/creo users in my organization through Windchill.

[TomU · Accepted solution]

Relations and Pro/PROGRAM statements can't be locked.

If a user has permission to change a part, then they have permission to change ANYTHING and EVERYTHING in that part.

The only options are:

1.) Don't allow users to change the part at all. (Use network file permissions, PDM system, etc.)

2.) Use Model Check to verify that the Relations and Parameters are still the way you want them.

(I don't think you can use Model Check to verify Pro/PROGRAM statements though...)

3.) Use a 3rd party application to manipulate the models instead.

Again, it doesn't matter if the user is internal or external. If they can open the model in Creo, they can view/change anything. The most you can do is try to prevent them from saving their changes back into the system.