Is there anyway to restrict some users from seeing some specific records?

(0) Share

Report

Posted on by Dan_B

Good afternoon all,

we have a situation in our company where one of our users has a conflict of interest, and we need to ensure that they are not able to access a specific address on our system - we store properties on there.

Due to the way Dynamics is setup I can't think of an obvious way to do this, and the other concern is that this is likely to crop up again in the fitire.

Has anyone dealt with anything similar or even started looking to the potential solutions?

Thanks

Dan

I have the same question (0)

All responses (3)

Answers (0)

edmunch on at

Like (2)

Report

You can do this using Security Roles in Dynamics 365. Yes, that is the tricky part. Example, you can restrict access to certain entities by User, Business Unit, Child Business Units, and Organization. You also have the ability to enable Field Level Security. Maybe start with a new Security Role and see what you can restrict so they cannot see those records. It is possible.

https://docs.microsoft.com/en-us/power-platform/admin/create-edit-security-role

Was this reply helpful? Yes No
Dan_B 21 on at

Like (0)

Report

Thanks @Efrain Hernandez - I will have a good read of that article.

The complication for us, is that in a company of 1000 people who use Dynamics, this one person can't see one of 30,000 properties.

Next week a different person might join who needs to not be able to see 1 or 2 other properties.

Presumably in that case we would need to tailor a security role to each of those individuals, and create a new one for each case that crops up.

I'm surprised it doesn't seem to have cropped up before.

Was this reply helpful? Yes No
icimasa 390 on at

Like (1)

Report

Hi Dan B,

In this case where there is only one person who can't se a specific record I would assume you still have to follow Microsofts process of using security roles or field security if that would me more appropriate. But the easiest way using OOTB solutions would be to use the record base security. I could not think of an easier way but i see your point.

docs.microsoft.com/.../use-record-based-security-control-access-records

regards

Martin

Was this reply helpful? Yes No