Is there a way to not permit a group of users to change the Template for a document but allow them just modifying the fields value for this template?
Hi there,
In order to make it so that your users can edit the values in the fields of a template but not change the template applied to a document, you'll want to use template security.
First of all, you'll want to allow the group Read for the template itself. Then for the fields in the template that you want users to be able to change, they should be allowed Edit, Create, and Read.
However, for at least one field in the template you'll need to only allow Read or only allow Read and Create, and not allow Edit. This will make it so that the users cannot edit the value of that field after the first time the template is applied to a particular document. This will also have the same effect on the template as a whole - once the template has been applied to a document the users will not be able to change the template.
Hi Kelsey,
I have had the same issue. However, I need a certain group to be able to modify all the fields, but the template name. Is this possible to be achieved?
I have tried creating a dummy field and make the Read access Denied, but it does not seem to work. The field needs to have Read access and not denied for Edit. Is this correct?
Is there any workaround?
Regards,
Hi Andres,
Can you try this (if you haven't already): Go into the Admin Console and in Metadata Management, open up the template. In the template security, add that certain group, and (for that group) set all of the dummy field's access rights to Deny.
Not all of those access rights need to be set to deny - only edit needs to be disallowed - but following those steps should ensure the goal of making the template unchangeable. If this is still unsuccessful, can you specify what didn't work?
Hi Tanya,
Thanks for your answer.
Unfortunately setting all field access to Deny does not solve the issue. It must have at least the Read access to Allow, which does not make much sense to me as it requires to create a dummy field and make it visible to the users when LF should be able to have this option by default.
If in the form there is at least one field read-only this solves the problem. However, in the scenario when you need to have all field to be modified, the only solution was to create a dummy field and make it read-only. This solved the problem for the moment.
Cheers,
Andres
Note that the workaround of adding a dummy field and having it be read only will cause the field to still show up in the metadata display, but prevents the Client from being able to attempt to change the template.
If you add the dummy field and deny read, create and edit, then the dummy field won't show up in the metadata display, but the Client still lets you try to change to a different template. However, when you try to save the change, the Laserfiche Server will prevent this.
For now, it's just a matter if you want to prevent users from even being able to try to change the template, but they see the dummy read only field, or have it such that it looks like they can change the template, but really can't, and not even see the dummy field at all.