Field Level Security not working

(0) Share

Report

Posted on by Mattw112b

1,088

I've seen some other posts on this and read them, still not working.

I have a custom column in the Accounts table called "Is Flu required"... It is a Yes/no toggle.

In the properties for that Column I have enabled field level security. Auditing is also enabled.

In "Column Security Profiles" I have created a new profile, "Set Flu Data in Account". I added it with that specific column I care about.

I have assigned users.

I have set, Read = Allowed, Update = Allowed, and Create = Not Allowed.

I have saved everything. I have given it 24 hours.

Users I assigned report that when they go to that form with that Column, they just see "****" and cant read or update???

From everytihing I can find I think I've done everythign required??

Anything I'm missin?

Thanks,

Terry

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (8)

Answers (0)

MichaelFP 1,847 Super User 2025 Season 2 on at

Like (0)

Report

@Mattw112IG when you create the Field Level Security, you need to have a fallback for the other users. Instead of will always show *****. Because FLS instead of Roles, process from more restrictive to less restrictive permissions.

I would recommend to you to use teams instead of to set for specific users. You can include in the fallback FLS the business unit team, so all the new users will have the fallback.

If my answer help you, please give me a kudo. If my answer solve your question, please mark as solution. This is help the community

Was this reply helpful? Yes No
Mattw112b 1,088 on at

Like (0)

Report

Thanks.

So I created a new field level security rule with the same field but with everything set to false for rights... and set to everyone.

Now users who always had access to that account form, can access again.

But the group that I set read=true and update=true, still can't access...

Do they need permissions to thee Account Table too? if so what permissions? I dont want to do edit for everything in accounts, because there's tons of fields I'd have to go back and say no to. I only want this group to be able to read or change about 5 fields.

Thanks,
Terry

Was this reply helpful? Yes No
MichaelFP 1,847 Super User 2025 Season 2 on at

Like (0)

Report

You only need to apply the FLS on the fields that has security column turned on.

Was this reply helpful? Yes No
Mattw112b 1,088 on at

Like (0)

Report

I just shared screens and made sure it wasn't working for them. It isn't. I also tried doing anotheer FLS for everything = true...

Let me document this out in more detail, I must be missing something.

Three FLS Profiles. 1 group I care about. Only want to edit one toggle on Accounts. That group currently only has read rights to Accounts.

"Set Flu Data in Account All"
Members (Teams): Everyone "Default team for the parent business unit. ".. which does include the people I am trying to grant access to.
Members (Users): None
Field Permissions (new_isflurequired - Type: two options): Read (Yes), Update (Yes), Create (Yes)

"Set Flu Data in Account Not Create"
Members (Teams): Health Screeners (Owner Group I created with the users I want to be able to edit/update)
Members (Users): None
Field Permissions (new_isflurequired - Type: two options): Read (Yes), Update (Yes), Create (No)

I had a test user refresh their browser a coupel times but still only has read rights to that field (It is grayed out, not asteriks)

....
I then created a new FLS Profile

"Set Flu Data in Account None"
Members (Teams): Health Screeners (Owner team I created with the users in it)
Members (Users): None
Field Permissions (new_isflurequired - Type: two options): Read (No), Update (No), Create (No)

But that didn't help either.

Am I missing something?

Seems liek I should be able to set a form to read, then open it up with a FLS profile. Which is what I was doing originally but then just got asteriks.

Thanks,
Terry

Was this reply helpful? Yes No
Mattw112b 1,088 on at

Like (0)

Report

Just found this:
Field security entities (Microsoft Dataverse) - Power Apps | Microsoft Learn

Says "Boolean attributes can be secured for create and update operations but not for read."

So maybe that's the issue here? But... if they can't read, then how can they update?

Terry

Was this reply helpful? Yes No
MichaelFP 1,847 Super User 2025 Season 2 on at

Like (0)

Report

for the boolean, if i'm not wrong. When you set update you will automatically have the read

Was this reply helpful? Yes No
Fubar 8,338 Super User 2025 Season 2 on at

Like (0)

Report

Not sure if this is your problem or not.

Your user must have a Security Role with privileges to the record. Assigning a FLS does not give additional privileges over and above the Security Role - what it does is 'mask' specific fields (acts like another layer above the Security Role), so whilst your user may have Read access to the record the FLS determines if they do or do not to the specific field in the FLS Profile. If your user has Read access to the record and the FLS Profile has Read and Update, they will only have Read on the field (as their Security Role hasn't given them edit).

Was this reply helpful? Yes No
Mattw112b 1,088 on at

Like (0)

Report

Thanks, I'm not sure I 100% follow what you are saying.
They have read rights to the table.
I think what you are saying that means they will only ever have read rights.
So how do I give them update rights to just that one field?
Do I need to make every field edit and then restrict to read int he profile??

Was this reply helpful? Yes No