D365banner

Host your self-service portal for better customer service and provide access to raise incident at customer or contact level across desktop or mobile. Portals are derived from admin center of dynamics 365 if you are already Microsoft Dynamics 365 customer. We can enable portal using below steps to Set up Self-service Portal in CRM Online.

d365-portal-zero

Select the portal for targeted end user type:

d365-portal-one

The custom portal framework is extensible and customizable so this can also be adapted to fit bespoke needs. Each Portal is connected with single organization or instance. Each portal includes entitlement for up 1m page views each month. Crm portals are a cloud service and we recommend customers to enable Azure storage. Portal template contract many configurable site settings various styles can be achieved and modified to get intuitive user experience we can define a theme that will include background style, text color, and layout width. In most instances, an organization will deploy only one portal. This will be managed in Global Portal Settings while settings for individual portals are applied through Portal Site Settings. An authenticated portal user is a Dynamics contact or system user. Web authentication information must be configured for each user.

Configure Portal Contact Web Roles

In order for your User account to configure the Portal you will need to assign the Administrators Web Role for the corresponding Portal Contact record that is created during the installation. Navigate to the Microsoft Dynamics 365 Contacts, you should be able to find the Contact record that corresponds to your user account. The Portal Contact form will have a Web Roles tab, Check it has the Administrator Role, If not you can add the web role as shown below:

d365-portal-two

In Dynamics 365, role based security permissions control what type of records each user can access. For portal users, a web role is needed to gain access permissions and different roles can be configured to enable varying access levels to portal pages. Local authentication is the most common process using a contact record for authentication. However, for custom authentication, developers can use the ASP.Net Identity API to create custom login pages. In these instances, account credentials and password management is handled by a third-party identity provider. This includes Windows ID, Google and Facebook.

Portal Feature and Functions

Once users log in, the portal functions and the data they can access will be determined by their web role which enables portal content to be easily defined and correctly exposed. Administrators will determine which entities are shown and which list views will be replicated within the portal interface. In these scenarios, the Cases entity will frequently be shared with portal users. As shown below, a list view would typically include the case title, case number, create date and current status which is pulled through from Dynamics:

d365-portal-three

Using native knowledge capabilities, a library of articles is accessible to customers and other portal users to find solutions and answers.

If this has been insightful, we invite an opportunity for sharing and listening further thoughts and propagate our cut towards the solution.Â
Feel free to connect, to know further detailsÂ

NSquare XpertsÂ
info@nsquarexperts.com

Leave a Reply