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

Question

Question

Weblink - Hiding Specific Fields from my weblink users however still make these available to my Web Client users

asked on April 12, 2019

Hi There,

I was wondering if anyone has customised weblink to Hide Specific fields from the read only users that access information via Weblink? I still need these fields to be available in the Web Client for my full users.

0 0

Replies

replied on April 12, 2019 Show version history

Hi, Sarah

 

Are you trying to hide the fields across all your templates? or just trying to hide the field from a specific template?

You can accomplish this goal by using the laserfiche admin console.

 

If you want the hide the fields across all templates log into your admin console.

Repository > Metadata Management > Fields

Right click on the field you want modify security. Bottom on the field info you have Security button, when you click on it you will see Who has rights to the field. From here you can modify the security to only allow  your name users to see the field.  If use the field other templates it also will be hidden.

 

If you wish to only hide the field in one template you will need to go to .

Repository > Metadata Management > Templates

Pick your template and right click to properties, then click on security. Here you are modifying the security for a field that will just effect one template.

 

1 0
replied on April 15, 2019

Exactly.  Field security - like all other security - is controlled at the user/trustee level, not by client application.

0 0
replied on April 12, 2019

You would not really be able to do this directly through WebLink.

Even if you added JavaScript or something to hide the fields, the data would still be there for anyone savvy enough to know where to look.

The real solution, which we use, would be to create separate user groups with different access rights and have the WebLink users in a group that does not have permission to see those fields.

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

Sign in to reply to this post.