Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
we have a pretty simple business unit structure: overhead as the root, and below that two different units.
Now, overhead people like designers mostly work on projects for both units and of course submit their time entries and expenses for those projects.
However, the project approvers of those projects are from their respective business unit, and they cannot see or edit time entries that are in a BU above theirs.
If I wanted them to see the time entries from overhead, I would have to set their permission level for expenses and time entries to global, which allows them to see way more than they are supposed to.
Is there a way for this to work that does not involve giving global permission level to every project approver that has overhead people in their projects?
Unfortunately OOB PSA is not built for resources/users in multiple BUs.
Here is a comment copied from another thread on the same subject:
Michael Nunes – August 27 at 08:26 AM from iPhone
Business units create a hard divide in crm and you would have to work harder to allow cross over permission between business units. How you would approach this in normal sales crm would then be needed for psa also. In the world of PSA it is the different organisation units that divide the different resources but if you already have business units then this will be painful. Hope you find a way
As a workaround you could try this:
1. PM cannot see the Approval record - use a workflow to change the owner of the approval to be the same as the owner of the project.
2. PMs can't even all Team Member on the project - use a workflow to update Project Team Member's owner to be the same as the owner of the project.
I hope this helps or at least explains that such relatively simple requirements is not met by OOB PSA. You could try this workaround but with multiple BUs you may easily find yourself in development territory... Use one BU if possible.
Business Applications communities