HI All,
I have a custom model driven app assigned to a security role with minimum permissions. The users can see the app, but they cannot see anything inside the app (1 view + 1 form working with 2 entities) as below:
I have assigned the permissions to the security role as below:
So, I've included basic permission, read permissions for the entities in the app, read permission to forms and views, read permission to the Security Role and Field Security Profile (giving them read-only access) and access to the mobile app.
Could anyone suggest what permissions I'm missing for the users to be able to see the components of the app?
TIA!
Someone outside this forum gave me the answer (thank you Vitor!), the customisation page should have the following settings:
Hi Angelo,
Ok, allow me to make some questions to help you narrow down the source of the behaviour
Did you add the Views and the forms in your custom application?
Did you include the Areas and the Subareas of your entity in the application SiteMap?
Did you manage the application roles?, or Did you promote the application with the same user access level?
Did you enable the form with the user security role?
thanks Fabio Bianco
I am actually working with Customer Service rather than field service. Unfortunately the customer service role is far too extensive, and the Customer Service app role is not enough (I already added the read Model-Driven app permission to my custom role)
I have followed this article https://alphabold.com/user-login-permissions-in-microsoft-dynamics-crm-365/ to set up the role, and then added a few permissions to reflect the intended use.
The app has already been made available to the correct security role. The users can see the app, they just can't see the form, view and data once they get into it. The only entities they need to see (read-only) are contacts and phone calls (made available through the activity entity)
I am keen to set up a role that is as restrictive as possible, and only allows access to the intended views and forms as I will then use as a template for other roles and apps
Hi,
Aditionally, the 'Set up field service users and security roles' (for Field Service) [https://docs.microsoft.com/en-us/dynamics365/field-service/view-user-accounts-security-roles ] documentation should give you a good starting point to build your own custom app
Hello AngeloA,
Thank you for your question
Each entity migth have its own required rigths in order for the user to see the Components of the application succesfully.
I would advise in this situation to make a copy of the OOB 'Customer Serivce app', or 'Sales Representative' security role, and start to revoke the rigths direclty from your custom security role till you manageachive your goal
Please check the 'Manage access to apps by using security roles' :docs.microsoft.com/.../manage-access-apps-security-roles
These OOB security roles are used to give the 'minimum' of rigths Sales or Customer Service representatives in the application. You can adjust and revoke the access of your users from your custom Security Rule till you limit the access of the application as desired
Hope this helps build your application following your business requirements
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156