Confidential Portfolio Plans

[adminpro]

Is anyone aware if there is an out-of-the-box option to set up a confidential Portfolio Plan? For example, a confidential HR initiative. When I mention confidential, consider how the HR scope app operates. I know you can create a portfolio plan and restrict who you share it with, but users in the right roles, such as admin or apw_admin, will still have full access. I also understand that you can customize the security to achieve this. I am mainly interested in discovering if there is an out-of-the-box option or a future plan from the SPM team to introduce such a feature.

[annacontreras]

Hi Kartik23,

I saw you responded in another thread related to this topic and recommended this article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1772519 

This seems much more complex (data filters & ACLs) than previous option with Data Separation...

Could you advise on usability and scalability?

[Kartik23]

Hi, 

I understand that it may seem like a lot of work, but it is much more scalable. I will however take your feedback under advisement. We are working on making the overall application configuration simpler and we will do our best to make it easier to configure.

As far as confidentiality is concerned, we added that for Projects in Yokohama and we plan to add it for more tables in future releases.

[Maarten]

I am interested, we too are getting this request from our PMO to have confidential demands and projects. will mail you

[Rajesh_Singh]

@adminpro Domain separation and team spaces add unnecessary complexity, overhead, and long-term maintenance challenges for a simple confidentiality use case. They are better suited for multi-tenant or organizational boundary separation. Query business rules provide a lightweight, maintainable, and scalable way to restrict access at the data layer without altering platform architecture. It’s a best practice for controlled visibility without compromising supportability. I don’t see any feasibility of this being added in future releases—at least nothing I’m aware of. We’ve achieved this successfully in two projects using carefully crafted query business rules at the data layer, without impacting the core platform design.