Power Platform Community Forum Thread Details

Customer Data Portal: How to configure permissions

Good Day everyone,

I am looking to build a self service website for new and existing customers. Details of this are as follows:

Right now, each customer (business) has an entry in the account table in dynamics. There are several contacts associated with each account (business).
I understand that upon the creation of a user account in Power Pages, an entry is added to the Contact table. Ideally, we would disable the ability for a user to sign up for the site on their own. Instead, we would add their entry to the Contact table, and send them an invite code to sign up to access the website.
When a user first accesses the website, they should be provided with the option to create their own record. This record, which will contain miscellaneous information, will be stored in separate table(s).
After creation of a record, we wish for users to be able to access the website at any time, and modify their record as they wish.

The following are what I need guidance on:

I need to associate the record to a specific account, not a specific user. I also need each user that is related to that account, to be able to access the corresponding account record on the separate table(s).
I understand this can be done via relationships in dynamics. What I am confused about, is the best way to setup these relationships. Additionally, should the record for each account be stored in one table, or multiple? I plan to use multi step forms to collect the information.
There will be one account table per customer. Several contacts per account. And, possibly, several records per account. These are the relationships I wish to establish.

Any guidance on this would be greatly appreciated!

Categories:

Security

Their is not one answer to this, but you will control access via Table Permissions assigned to a Web Role(s) that are assigned to (or inherited by) your Portal Users (Contact).

Table Permission with scope = Contact: If you need an individual Portal User to access a record then you put a Contact Lookup on that table, and when the record s created populate the Current Portal User into the Lookup (on the Portal you can do this via form Metadata or the Form definition has Associate Current Portal User settings),

Table Permission with scope = Account: If you need other Contacts for the Portal User's Account (using the out of the box parent lookup on the Contact) to access record then use an Account lookup, and populate it on create e.g. via form Metadata.

Table Permissions with scope = Parent: allow you to extend this e.g. if you had an Account lookup on Table A (and a Table Permission with Scope = Account), and Table A has child records in Table B, you can use a Parent scope to give access to the Table B records that are linked to the Table A record without having to have a Contact/Account lookup on Table B (because the Portal User has access to the record in Table A via the Account Scope permission they inherit access to the child records due to the Parent Scope permission).

Quick Links

Subscribe to this forum!