Power Platform Community Forum Thread Details

I think I have my security settings where they need to be, but am a little confused & wondered if someone could explain how it works a little.

I am using a non-default environment. For a given custom table/entity, I have a custom security role defined "company managers," where under the "custom entities" tab, I have given a green circle to the create/read/write/delete/append/append to/assign/share columns. For the other tabs, I have minimal permissions defined. This seems to enable appropriate data connections and the powerapp works.

I have also enabled column security for the "hiddenfield" field in this table/entity

I then created a custom Field Security Profile called "general managers" where I denied read/update/create field permissions, and applied this Field Security Profile to user 3.

When user 3 logs in, they can view the powerapp & most of the data in it's tables/entities. Also data in "hiddenfield" remains hidden... which all sounds good.

My question is why is it working? Did I chance across the right settings in the custom Security Role I created? Or does the Field Security Profile keep "hiddenfield" out of reach of user 3... Or by enabling column security, did this create the right environment where, in combination with the custom Security Role, it keeps "hiddenfield" hidden for anyone by those with higher access permissions?

Sorry for any lack of clarity. Any insight would be hugely appreciated, thx!

Categories:

Building Power Apps

Hi @Medoomi :

I found some tips, they explained the relationship between Security Roles and Field Security Profiles:

Security Roles implement record-level security – i.e. can I see a record, can I edit a record. Field Security Profiles implement field-level security on a field by field basis. Record Level Security always has a higher priority over Field Level Security!
Users with the System Administrator Security Role override the Field Level Security configuration and automatically have Read+Write+Create permissions on the Fields involved
As soon as enable Field Level Security on a Field, this immediately takes away access to the Field for all Non-System Admin Users and so should be done carefully!

Best Regards,

Bof