Unanswered

How to limit access to Audit History Table per Teams or Apps/Solutions?

(0) Share

Report

Posted on by K43876

I am developing a Power Apps Model-Driven app in a dev environment given to my team, which is one of many teams in our organization. It looks like that I am able to extract Audit History through WebAPI in this dev environment from all the tables, not just the ones my app created.

I created a Security Role "Audit History Reader" which has two privileges of prvReadRecordAuditHistory and prvReadAuditSummary under my solution in dev env and assigned it to a service account. What's not clear to me at this point is whether this service account would see really all the tables in the test env when deployed.

If that's true, how can we limit the access of this service account on Audi History only to the tables that my app created?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

MichaelFP 1,999 Moderator on at

Like (0)

Report
Copy link

Link copied!

You need to limit the access to table. Because you have the access to read so you will be able to see the information. Only allow your service account to see the table that it needs.

Was this reply helpful? Yes No
K43876 37 on at

Like (0)

Report
Copy link

Link copied!

When I created a new Security Role 'Audit History Reader', there was no other options beside "Organization" and "Block" with no "Team" option:
Does this mean those privileges apply only to the whole organization level, not having a finer granulation?

Was this reply helpful? Yes No
K43876 37 on at

Like (0)

Report
Copy link

Link copied!

Thanks for replying @Michaelfp ! But already the service account user is disabled for all other tables except my app created ones. WebAPI result still shows history of all other tables including not allowed ones.

Was this reply helpful? Yes No