Generic Structure limited by Owner access permission

David Landry_02d4gk

Hi,

We are building a generic Structure so that every project in our organization can access the data pertaining to their project according to their permissions within that Structure.

For example, the Structure search for all issue of type Risk and show only the issue for which the user has access to the project.

Structure seems to be applying the permissions of the owner of the Structure on top of the permission for the user of the Structure. Thus limiting what the user can see to what the owner has access.

For example, if the owner has access to project 1, 2 and 3 and user has access to project 4, 5 and 6. The user won’t see anything in the Structure.

How can this behavior of Structure can be avoided ?

We have a hard time understanding why Structure apply a permission validation based on the owner of the Structure when there’s already a validation within Structure based on the permissions of the users.

Oday Rafeh_2jhprw

Hi @David Landry , 

As you've mentioned, Structure currently applies the permissions of the owner of the Structure on top of the permission for the user of the Structure. This behaviour can be confusing and limiting in some cases, but unfortunately, there's no direct way to avoid this behaviour in the Structure app itself.

1. There's a workaround that you can try to ensure users see the issues they have access to:
2. Create a new dedicated user account specifically for owning the generic Structure. This user account should have the necessary permissions to access all projects within your organization.
3. Log in as the dedicated user and create the Structure. Since this user has access to all projects, it won't limit the visibility of issues in the Structure.
4. Share the Structure with all users in your organization. When users access the Structure, they will only see the issues they have access to, based on their individual permissions within the respective projects.

This way, you can ensure that the Structure owner has access to all projects, and other users can see the issues they have access to without being limited by the owner's permissions.

Remember that giving the dedicated user account access to all projects might have some security implications, so evaluate this workaround carefully based on your organization's requirements and policies.