How do I Secure my adxstudio portal?
Record-based security in Adxstudio Portals that applies to individual records is provided by using Entity Permissions. While permissions to change and access URLs in a portal sitemap is granted via Content Authorization, site managers will also want to secure their custom web applications built with Entity Forms and Entity Lists.
How do I add an entity permission to a web role?
In order to add an Entity Permission to a Web Role, navigate first to the Web Role you wish to add the permissions to. Web roles for a website can be found in the CRM in either Portals > Web Roles or Portals > {your portal} > Web Roles. Click to Add an Existing Entity Permission.
How to restrict the information being exposed on the portal?
Yup Agreed, but you can control it by restricting the information being exposed on portal. For example, if you want to query on email address field only, use only email address field in the odata view instead of keeping rest of the information.
Adxstudio Portals- Forgot Password - Email to contact is not sent
I did tried all the options suggested above but still didn't receive the email - workflow also not trigger to send a email.
Adxstudio Portals- Forgot Password - Email to contact is not sent
Hello, I am receiving the same issue. Can you please tell me if you have found a resolution for this? Thanks.
Adxstudio Portals- Forgot Password - Email to contact is not sent
Using Odata Feed is anonymous. It means anybody can see your data by adding .crmportals/_odata
Adxstudio Portals- Forgot Password - Email to contact is not sent
Exposing confidential email address is data breaching it means anybody can see confidential email address... Better solution is to expose the standalone Webservice with secured connection using API token... I will never implement adxstudio odata feed especially for contacts...
Resetting Adxstudio Portal Passwords on Azure
Despite the fact that Microsoft will now only be selling Adxstudio Portals v7.0 on an exception basis (see here ), there are still hundreds of portal implementations that still being deployed and supported.
Published by Nick Doelman
Microsoft Business Applications MVP, Dynamics 365 Specialist. Technology enthusiast. Powerlifter. View all posts by Nick Doelman
Adding Entity Permissions to A Web Role
Global Scope
If a Permission record with Read permission is granted to a role that has global scope, any Contact in that role will have access to ALL records of the defined Entity in the CRM. i.e. they can see all leads, all accounts, etc. This permission will be automatically respected by any Entity Lists; essentially showing all records according exactly to the CRM view(s) that has been defined for t…
See more on community.adxstudio.com
Contact Scope
With Contact Scope, a logged-in user in the Role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user's contact record via a relationship that is defined in the CRM. On an Entity List, this means a filter will be added to whatever CRM view(s) are surfaced by that list, which retrieves only records linked to t…
See more on community.adxstudio.com
Account Scope
Self Scope
Parental Scope
In this most complex case, permissions for an entity are granted that is a relationship away from an entity for which a permission record has already been defined. This permission is actually a child record of the parent Entity Permission. The Parent Permission Record defines a permission and scope for an entity (Probably Global or Contact Scope, a...
See more on community.adxstudio.com