Question

field security 9013

Security Workflow

Updated April 6, 2020

asked on April 3, 2020

A repository user 'agent' is a member of the 'administrators' repository group. Administrators has every Privilege including "Manage Templates and Fields".

On the field 'Permit Status' workflow, connecting as agent, gets this error. The data assigned to field 'Permit Status' is not valid 9013 [Access denied. [9013]] [0265-WF10]

That should only happen if the data does not meet constraints on the field. There are no constraints, the token value can be pasted into the field and saved in the client as a different user.

I assigned edit field permission explicitly to agent and voila the workflow errors went away. This goes against everything I understand about Laserfiche security.

Help me understand what went wrong here. Why wasn't "Manage Templates and Fields" sufficient? Why did I have to add agent explicitly on one field? Every other field is fine.

0 0

Answer

SELECTED ANSWER

replied on April 3, 2020

Privileges are administrative in nature. So Manage Template and Fields grants you the ability to see and modify the definition of every field and template. Applying a field to a document would be controlled by that individual field's security (and the security of the document).

So the behavior is correct. With the privilege, you can tell the field exists. But without the rights to read it and edit it, you can't actually set it.

3 0

Replies

replied on April 6, 2020

Thanks for the clarification.

0 0

You are not allowed to follow up in this post.

Question

Question

field security 9013

Answer

Replies

Sign in to reply to this post.