The portal can be setup to be either anonymous or to require authentication. If authentication is required, note that it is contact-based and so administrators will need to be assigned a web role with permissions to update the portal. While authentication can be either Local Authentication or External Authentication, we strongly recommend the Azure B2C option.

For more information on portal authentication, refer to the Microsoft website and search for “Configure Dynamics 365 portal authentication”, or click here.

For more information on restricting page content to specific citizens, refer to the Microsoft website and search for “Control webpage access for portals”, or click here.

Web Roles

Web roles determine permissions to complete any special actions or access any protected content on the portal. For example, if a page can only be seen if the contact is known, the contact must be assigned to a role allowing access to that page. If the content on a page needs to be updated or a new page created, the contact must be assigned to a role that is given content publishing permissions. There are 3 roles included with an out of the box portal: Administrator, Authenticated Users, and Anonymous Users.

Administrators – The Administrator Role is created for users that should be free from the constraints of either the Authenticated Users Role or the Anonymous Users Role.

Authenticated Users - The “Authenticated Users Role” is the default web role for all authenticated users. This role is commonly used to provide a predetermined access for users that are not associated to any other roles. Keep in mind that users can have multiple web roles, but there can only be one Authenticated Users web role for authenticated users.

Unauthenticated Users - The “Anonymous Users Role” is intended to be used with Entity Permissions. It will not respect any other rules or permissions. By enabling the “Anonymous Users Role” it will become the default web role for all unauthenticated users. There can only be one Anonymous Users web role for unauthenticated users.

To create a new web role:

  1. Navigate to Portals -> Security -> Web Roles. The Web Roles grid displays.
  2. Click New. The New Web Role form displays.
  3. Specify values for the fields provided. Refer to the table.
  4. Click Save.

Name

Description

Name

The descriptive name of the Web Role

Website

The website to which the role is associated.

Description

An explanation of the Web Role's purpose. Optional.

Authenticated Users Role

Set to Yes - this will be the default web role for authenticated users. The settings for the 3 typical roles are:

Authenticated User – Yes

Anonymous User – No

Administrators - No

Only one Web Role with the Authenticated Users Role attribute set to true should exist for a given website. This will be the default web role for authenticated users that have not been assigned a web role.

Anonymous Users Role

Set to Yes - this will be the default web role for unauthenticated users. The settings for the 3 typical roles are:

Authenticated User – No

Anonymous User – Yes

Administrators - No

Only one Web Role with the Anonymous Users Role attribute set to true should exist for a given website. This will be the default web role for unauthenticated users. Also note that the Anonymous Users Role will only respect Entity Permissions.