Hello everyone,
 

As we all know, access rights in the 3DEXPERIENCE Platform are fundamentally controlled through Credentials, defined as the combination of Collaborative Space + Organization + Responsibility. This is the core mechanism for determining who can see and do what.
 

In our current aerospace environment, we face a situation where:

There are too many Collaborative Spaces
Only one or two Organizations are used under each CS
Extended roles are heavily relied on in the Baseline environment
Large volumes of data are stored across each Collaborative Space.

Because of this, our PnO landscape has become difficult to scale, govern, and secure. To move toward a true best‑practice PnO model, I would like to gather your insights and recommendations.
 

In particular, I’m interested in your thoughts on:

1- How we can reduce the number of Collaborative Spaces, keeping only those that provide meaningful access segmentation ?

2- How we can restructure our Organization Model(e.g., Business Unit, Department,Subsidiaries ) so that it works effectively with the horizontal PnO approach (CS + Org + Responsibility) ?
3- How we can redesign our Organization structure to better reflect ownership, responsibilities, and departmental boundaries, and
4- How we can simplify and rationalize User Groups, avoiding the over‑complexity that exists today.

Ultimately, how can we reorganize our current setup into a cleaner, more scalable PnO architecture that supports secure collaboration, reduces administrative effort, and provides a strong foundation for long‑term growth?

Thanks in advance and I look forward to hearing your suggestions.

Kind Regards,

Nuh Keremoglu