You are viewing limited content. For full access, please sign in.

Question

Question

Public Portal displays all document relationships

asked on October 23, 2015

I have a client that is using their public portal (weblink) for public access to their Minutes and Agendas. We have built some pretty wicked workflows that go out and find documents in Laserfiche that are somehow related, which creates document relationships. When displaying these public agendas and minutes, if the public looks at the metadata, they can see ALL relationships. Of course, if you click on some of these that they do not have permission to, they will be given an access denied. 

 

Is there a way to hide the relationships to only display the documents that the public user has access to?

 

Thanks in advance!

0 0

Replies

replied on October 26, 2015

I've already checked effective rights for the public user, see screenshot below on a non-public document that is listed with a relationship to a public document . The security has got to be correct but yet it still shows. There is no 'by-pass browse' enabled on any user or group either, including the everyone group. 

Version of Weblink is 9.0.0.259

 

 

public effective rights.PNG
1 0
replied on October 26, 2015

Thanks for including the version. I took at look on that same version of WL, however, and I could still not reproduce.

Could you double-check that you're logged in to Weblink as the user you think you are, by clicking on "My WebLink"?

If that checks out, then can you try the same action in the Client? That will help determine whether there's something unexpected going on on WL, or if there's something we're missing about the security.

0 0
replied on October 23, 2015

I am not seeing the behavior you described: when I log into WebLink as a user that cannot access a document in the list of relationships, that document is hidden from the list. Try looking at the effective rights for the public user on these documents.

0 0
replied on October 26, 2015

I just upgraded them to SP1 (9.0.1.275) and same issue remains. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.