So I have an HR Template that I only want HR and the Admin to see. But the template contains fields that Everyone should have access to. My fields must not be setup correctly. Any help would be great.
So I have an HR Template that I only want HR and the Admin to see. But the template contains fields that Everyone should have access to. My fields must not be setup correctly. Any help would be great.
Actually, there's nothing 'special' about Admin - it's simply a user that, in a default repository, has all administrative privileges. However, it would still be covered by an explicit deny by the everyone group. In your case it looks like you have everyone just unset instead of denied, which shouldn't impact Admin. Are you certain field security is the issue here? Do you know which specific field is causing the issue?
Field rights (such as the ability to view or edit the contents of the field) are specifically tied to the field themselevs. The administration console lets you edit them directly from the template, but they aren't actually properties of the template. If you simply want to ensure that only HR and Admin sees the template, and don't care about the fields inside of the template, you can simply ensure that they are the only trustees that have the 'read' template access right allowed (the one in the middle section), and then leave the field access rights alone. That way only the admin or a member of that group will be able to see or select this template, but all users could see values assigned to these fields, regardless of template state.
Note that you might want to also restrict other users being able to view the values of one or more of these fields (for example I see SSN there), and that you'd do in the bottom section.
Justin, the problem I'm having is, Forms is getting suspended on the save to laserfiche step. I have the user in Forms setup as the admin. Why am I having security issues? Is it because of the Everyone group. Shouldn't the admin override the everyone?
Actually, there's nothing 'special' about Admin - it's simply a user that, in a default repository, has all administrative privileges. However, it would still be covered by an explicit deny by the everyone group. In your case it looks like you have everyone just unset instead of denied, which shouldn't impact Admin. Are you certain field security is the issue here? Do you know which specific field is causing the issue?
No, I am not sure. I removed all the fields in the save to repository task and it worked great. I assumed it was the field rights. I will see if IT can get me access to the Event Viewer so I can see what might actually be the full reason.
I figured it out...Simple error on my part. After attempting to try out the same process using workflow it pin pointed the mistake I made. Had nothing to do with the Field security or Template. The path was missing a simple piece.