Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Our PSA sitemap is fairly cluttered with a host of entities. Some of these entities are not relevant for certain security roles. Is there a way to make certain entities not visible based on a users security role?
You can restrict access to entities with security roles. For example in the photo below a user only has the OOTB Customer Service Representative and PSA app access roles.
Remember to first test in dev and don't overwrite any of the OOTB security roles. Make a copy of an existing role for testing purposes or build a new role from scratch for testing purposes.
To further evaluate differences between PSA's security roles, please see my blog post here.
And to add to that Resource Hub solution is quite good when it comes to a decluttered interface - both in version 2 and 3. Probably 80% of users will really need the Hub only (depending on size of companmy etc.).
Couple of things:
1. Cleanup the security role, if they don’t need access then remove the privileges for those entities
2. Use sitemap editor to map the sitemap Subarea to entity privilege rule with respect to that entity. If users don’t have privilege they won’t see
Business Applications communities