Enabling Workspace Access for Guest Role – Need Guidance on Required Permissions

Forum|Forum|1 year ago
November 5, 2024
4 replies
1091 views

Version: Windchill 12.1

Use Case: I’m configuring the Guest role in Windchill, but I’m encountering an issue: the Guest role cannot view or create workspaces.

Here’s the situation:

* The Guest role is set up with read-only access to released objects.

* Despite configuring access control to allow Read and Download permissions on object types like WTPart and EPMDocument, the workspace option is still unavailable for users with this role.

* We have also configured lifecycle states to ensure the Guest role has Read access to the Released state.

Question:
What specific permissions or additional configurations are required to enable workspace visibility and creation for the Guest role?

Any insights or guidance on how to set this up effectively would be greatly appreciated!

Thank you!

Collaborative_Data Sharing

Best answer by avillanueva

If its possible via ACLs, I would focus on EPMDocConfigSpec object but this article alludes that its not ACL controlled (https://www.ptc.com/en/support/article/CS45134?source=search). Its a bit dated but might still hold true. Curious why you need to do this? Workspaces can be created anywhere and pull date from any Product or Library so long as the guest has read access to those EMPDocuments. For example, my libraries are read only, users are guest but they can still pull data from them. I suspect its specifically blocked in a UI filter or code that prevents Guest from creating them or seeing them.

What you can do is use a role shift. Make those users who are Guests and need workspaces Team Members. Restrict Team Members from doing much like Guest and create a new role to take the place of a full Team Member. Add addition ACLS to it. That might work but unsure of why you would want Guests to create workspaces in an area that is read only to them. They would not be able to check anything in anyway.

avillanueva

Answer

23-Emerald I

If its possible via ACLs, I would focus on EPMDocConfigSpec object but this article alludes that its not ACL controlled (https://www.ptc.com/en/support/article/CS45134?source=search). Its a bit dated but might still hold true. Curious why you need to do this? Workspaces can be created anywhere and pull date from any Product or Library so long as the guest has read access to those EMPDocuments. For example, my libraries are read only, users are guest but they can still pull data from them. I suspect its specifically blocked in a UI filter or code that prevents Guest from creating them or seeing them.

What you can do is use a role shift. Make those users who are Guests and need workspaces Team Members. Restrict Team Members from doing much like Guest and create a new role to take the place of a full Team Member. Add addition ACLS to it. That might work but unsure of why you would want Guests to create workspaces in an area that is read only to them. They would not be able to check anything in anyway.

joe_morton

18-Opal

Make sure they have the required licenses assigned as well.

H

Hari_Vara

16-Pearl

Hi,

In the ACL / Policy Administration, "Guest" role is not considered as the principal "Team Members", and hence OOTB behaviour is to just Read only. As Villanuev says , if Guest user is not allowed to edit, there could be no use to create workspace.

In case you want that user to work in workspaces, you need to give the user a OOTB role called "Viewer". (As far as I remember).

Please explore it, I have used it in some of my solutions to customers.

Cheers

Hari

T