Skip to main content

Notifications

Customer Insights - Journeys forum

Restricting rights for user who can upload to contact entity

(0) ShareShare
ReportReport
Posted on by 180

HI

WE wish to give our event managers to ability to upload data into the contact entity but we dont want them to have rights to delete, which I believe you need to have given the user read, write & DELETE.

Is this correct and if so have do you get around this?

Brad

  • Suggested answer
    Abhinav Sunku Profile Picture
    Abhinav Sunku 350 on at
    RE: Restricting rights for user who can upload to contact entity

    Hello Brad,

    As per my understanding, we can change the roles under Settings-> Security

    Select the roles and open it and under core records you can change as per the requirement.

    access.PNG

    Hope it helps,

    Best regards,

    Abhinav sunku.

  • cloflyMao Profile Picture
    cloflyMao 25,202 on at
    RE: Restricting rights for user who can upload to contact entity

    Hi Brad,

    Yes, a setting for your Event Manager could be below, if you want to restrict user's right to delete, just set it to None.(No access is allowed)

    security.png

    In addition, here are my suggestions:

    1. Security role privileges are cumulative

    which means if you assign another security role to your user(it already has Event Manager security role), 

    you should ensure that it hasn't delete privilege on contact entity.

    2. There is an existing security role called Event Planner, you could take it as reference while setting up Event Manager.

    pastedimage1563776659287v2.png

    Regards,

    Clofly

  • Suggested answer
    Pawar Pravin  Profile Picture
    Pawar Pravin 5,227 on at
    RE: Restricting rights for user who can upload to contact entity

    Hi Bradh,

    As per my understanding you need to assign access as belows:

    pastedimage1563775045364v1.png

    In your case if you dont want to give delete access to event manager then make sure that delete access in security role should be null and in other side create, read, write should be filled with user, BU, parent child or organizational level as per your requirement.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,969 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 230,842 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans