Answered

Help Understanding Permission Structure

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

I'm working on a portal design allowing different companies to access a power app portal. Each company will have one or more users that will be granted permission to the portal via an Azure B2C invitation. Contact table --> Flow --> B2C --> and so on

Each company will be uploading documents and modifying data related to them.

Would you create a parent business unit, add owning teams, or create a business unit for each company?

BU
- Owning Team A
-- Users
- Owning Team B
-- Users
- Owning Team C
-- Users

or

BU A
- Users
BU B

- Users
BU C

- Users

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Fubar 8,491 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

The Portal does not use Dataverses Business Units, access is granted by assigning Web Role(s) to a Contact record and those Web Roles have Table Permissions. (Internal Users will still get a Contact record if they are also a Portal user). You can achieve the Separation/segregation for the Portal based on the Account that the Contact is associated with and setup lower level permissions using the Scope of "Parent" to the Account permission.

Teams and BU's only apply to an internal user accessing via the Model Driven App or Canvas App etc. If you have people who will be accessing both the Portal and via the Model Driven App etc, then you would setup a BU Stucture and when records are created etc assign the records to the appropriate Team.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thank you! I totally forgot about Contacts rolling up to Accounts. That makes things a lot easier!

Was this reply helpful? Yes No