cancel
Showing results for 
Search instead for 
Did you mean: 

Recommended task role approach for disabling a field that is editable by default

ldubois1
Explorer
0 Kudos

Scenario:

Default view allows editing a field. We want most users to NOT have access to edit the field. Creating a Persona would turn off the ability to edit, but would require assigning most users the role to have that as default, and thus we had to add that task role to a lot of business roles. So to have the standard view and be able to edit the field, it is the absence of the task role that gives the standard role and allows edit. That presents problems where governance level users also have to have other roles that cause them to see the persona (and removes ability to edit the field). What is the recommended approach for this type of scenario?

Accepted Solutions (0)

Answers (1)

Answers (1)

tamas_hoznek
Product and Topic Expert
Product and Topic Expert
0 Kudos

Keep in mind that Personas is not a data security solution, so disallowing edit access to a field may not be the proper use of the tool. Also, a knowledgeable user can add the parameter to the URL to disable Personas, thereby use the Original Screen where editing the field is allowed. I would rather try to find a way to prevent editing the field with some backend authorization (if possible) to close that gap.

With that said, how about creating another flavor that does allow access to edit the field (assuming this is not the only one thing the flavor does)? This flavor can be assigned as the default to a role governance level users have. With proper role rank settings you can make sure that this flavor is selected instead of the one that prevents editing.