Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
The ET aligns their Deliverables based on the nature of the deliverable/task. For example, the ET specifies deliverables as Client for any deliverable that is related to client work. Please note that the ET does not use the client portal for their workspace nor do they plan to use this. Furthermore, the ET had their files stored within the existing SharePoint folder structure to align with engagement execution and deliverables.
Now after the security permissions update, they are not allowed to attach files from SharePoint into their Client Deliverables. Two workarounds have been identified but both would be time consuming and may cause users to resist Concourse adoption going forward.
Concourse Workspace link:
https://concourse.pwc.com/engagement_90dfa2a5ad596696/
Scott Foster
| Workspace Territory | United States |
@Scott - My Engagement Team is experiencing the same issue, and I agree that the work arounds are arduous and time consuming. I am already seeing signs of adoption resistance as many of my team are starting to push back on using the "Attach Files" feature of concourse altogether.
@Courtney - Can you loop me in with the team that focuses on Concourse's SharePoint integration as well?
From my perspective it doesn't feel like the ways in which Engagement Teams work/deliver engagements has been, or is being, taken into account when designing this functionality/adopting the requirements from Risk. My interpretation of what Risk is mandating is that there be greater clarity and partitioning of what files are and are not being shared with clients. Engagement Teams want the same thing.
I think part of the the issue is being driven by the overly simplistic assumption that something is EITHER a Client Deliverable (should be seen/accessible by Clients) OR an Internal Deliverable (should only be seen/accessible by PwC). That's just not how Engagement Teams work - there are very often tasks/draft documents that are associated with or support a Client Deliverable and need to be attached to a Deliverable/Task so they can be linked to Save It, but that the client should not have access/visibility to.
What's been implemented following the updates last week interferes with and directly impedes the ability for Engagement Teams to successfully deliver engagements using Concourse.
Hi Scott! Thank you so much for submitting this idea. We've assigned this to our team that focuses on Concourse's SharePoint integration and they'll be in touch.
We understand the SharePoint permission feature has caused disruption in many workspaces this past week and we're extremely sorry for that. If you need any guidance or would like to view any demo videos on how to deal with the new security measures, you can find them on the Concourse Guide.
Thank you again for using this portal and submitting your idea! We appreciate it!