web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Unanswered

Is there a way to emulate team/BU access level functionality on field security?

(0) ShareShare
ReportReport
Posted on by 25

I have a requirement where the client needs field permissions on certain financial fields on an entity which will allow reading/updating of the field for users within the BU of the record, but not to users in other BUs, similar to how security works on the entity level (with permissions being given at access levels of either: User, BU, Parent/Child BU, or Organisation). I know the basic field level security just allows the binary option of "users are never allowed to read/update the field" or "users can read/update the field as long as they have the appropriate entity permissions to the entity", with no discerning between records owned by you/your team, but is there a way to fulfil my requirement without something incredibly cumbersome like a copy of the field for each BU plus an additional field to aggregate them together for business logic?

To clarify the requirement, an example of the need would be for their UK sales people to be able to see a count of Orders owned by the US BU for a given Account (to see whether the Account is being actively engaged by other countries, for example) but not to see how much the Orders cost, but the UK sales people would still need to see and update the Order cost field for Orders owned by users in their UK BU. Is this possible?

I have the same question (0)
  • Fubar Profile Picture
    2,761 on at

    Completely lockdown the field on the Entity in question (Field Level Security, but only give read access to all users), Implement another Team/User entity (the change request entity) and let the respective users edit it, then copy the value in to the field that you locked down (run workflow or plugin as a user that is Sys Admin or has edit on the Field Level Security).

    You could also potentially do something similar with an Approval in Flow (without the extra entity)

  • Harvey Adock Profile Picture
    25 on at

    Thanks for your suggestion, but I think this would only cover update rights, correct? Part of what the client needs is read rights to also be restricted, e.g. BU "X" members can only read the value of the field on records belonging to BU "X", while they can see other data on records from BU "Y", just not the fields which should be restricted by this security.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 163 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 158

#3
Zhilan Profile Picture

Zhilan 49

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans