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

Notifications

Announcements

No record found.

Community site session details

Community site session details

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

Column level access to allow users to update only certain columns on a custom entity

(0) ShareShare
ReportReport
Posted on by 110

I've got a need to permit a group of users access only to certain columns on a custom entity.

Is there a way to do this using column security? 

Would users who have read/write access to the entity via a security role retain that access, or would I have to explicitly assign them a custom profile to preserve their access to the columns with column-level access?

Thanks,

Jessica Weissman

I have the same question (0)
  • Verified answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Hello Jessica,

    If you would make fields "Secured" you will have to provide the mentioned group of users the profile to have the access to "Secured" fields.

  • Jessica Weissman Profile Picture
    110 on at

    Hi, Andrew, and thanks.  What I am looking for is a way to allow certain users write access only to a small subset of the columns on a custom entity.  They can view any other column.

    Everybody else with access to the entity should have read/write access to all the columns.

    It sounds like what I have to do is make all columns EXCEPT the small subset Secured.  Then create two Security profiles, one for most users that has create/read/write access to the many Secured columns and one that has read access to the many Secured columns.  

    For both profiles, they would have access to the unsecured columns by virtue of the relevant Security role.

    Not robust, but it will make the client happy.  

    Or maybe I can talk the client into skipping the whole thing and just telling the small group of users not to touch the other columns.  They're busy and shouldn't have the time to mess with anything that isn't their primary responsibility anyway.  Plus we have an audit trail.

  • Verified answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Alternatively, you can depending on the user role enable/disable fields using JavaScript. It's not bulletproof because there is LevelUp or other tools that might be used to disable fields easily but it's not as heavy as field-level security.

  • PP-29040829-0 Profile Picture
    54 on at
    Hi a3ik,
     
    If I mark primaryVendorID as 'Secured,' does it mean I can set up a special group to update this field, or not?
     

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 170 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 61

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 52 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans