Skip to main content

Notifications

Announcements

No record found.

Customer Service forum
Suggested answer

Security Scheme: Mark an entity as private without affecting the ownership of the entity.

Posted on by 5

We are in the process of implementing Dynamics 365 Customer Service.
The security scheme we intend to implement is the following:
All users have permission to read, write, append, append to ALL records of the entity "case".
However, it is intended that some records in particular, can be marked as "Private" without this leading to a change in the ownership of the case.
Do you know of any way to solve this requirement?
Thank you very much for your answers.
Regards.

  • Security Scheme: Mark an entity as private without affecting the ownership of the entity.
    Did you ever figure out how to do this.  Its a requirement when there is an activity (i.e. email) that has confidential information from customer that only should be viewable by one team or queue, but the majority of entities can be viewable by all, how can we mark a case or activity private for a particular team.  I know you can create different business units and queues for this but then its all or nothing.
     
  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Security Scheme: Mark an entity as private without affecting the ownership of the entity.

    Hi ml246,

    Firstly, you mentioned “All users have permission to read, write, append, append to ALL records of the entity case.”

    Which means that the security role that all users assigned has highest privilege(orginaziation) for case entity.

    pastedimage1615445442803v1.png

    Then you mentioned “some records in particular, can be marked as Private”, which means that only some users can view these particular cases.

    Some particular cases must be a part of all cases, Isn't this a logical contradiction to the above request?

    Regards,

    Leah Ju

    Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

  • Suggested answer
    Fubar Profile Picture
    Fubar 2,750 on at
    RE: Security Scheme: Mark an entity as private without affecting the ownership of the entity.

    Not really, the Security model is heavily based on record ownership, and the way to make something 'private' is to assign it to a user or Team.that pushes it out of the view of other users based on their Security Role Privileges and the Business Unit Structure implemented.

    Why is it important that the Owner does not change? (e.g. if it is just to keep a reference of the user, you could add another User field on the entity and use a workflow to copy the record owner to the User field and then set the Owner to a Team when a Private Yes/No was changed etc)

    Other way would be to exclude records using a plugin registered on retrieve and retrievemultiple - but this would also add a performance overhead on every read of the case entity.

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 288,459 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,783 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans