Power Platform Community Forum Thread Details

This question has Dataverse, Power Automate, and Power App components. Due to the community size, I'll start here in the Power Apps forum.

I have a Power App in which users can create groups and add/remove members from those groups. Additionally, users can create tasks and can share the task with individuals or groups. This is done by selecting the individual users or groups from a combo box and then saving that to the Task Member table.

Currently, Power Apps then filters only tasks that have been assigned/shared with you.

To do this, I have the following Dataverse setup:

Group Table (Details about group)

Group Member Table (UserId + GroupId)

Task Table (Details about tasks)

Task Member Table (UserId + TaskId)

This (appears to) work fine, but I am controlling access to the tables and rows via the Power App only. If possible, I’d like to enhance that, and control access at the database level, too.

I’ve come across this article about how to dynamically set owners with Power Automate, but I’m wondering if this is the preferred way, or if there is a different strategy? Using the above article, it seems as I would listen to a new record being created, and then add all the users as owners and then assign those to the record. Then I would assign a security role granting user-level access to the record.

I’m also wondering if this is the most efficient strategy or if there are other patterns that might be implemented? For example, are there other flow strategies I could use? Could I leverage Dataverse teams, and instead of having my own group table, could users create and manage Dataverse teams with Power Apps/Power Automate and then use Automate to assign those teams to tasks? Or is there a particular security role configuration that would require table access occur via a Power App only, thereby allowing me to be more confident in securing access to the tables using Power App filters only?

Categories:

Building Power Apps