Projects Rights & Organization

Hi,
I don't confusing Profiles and access mode. I said   I have created a profil named "reader"  (with Reader access mode everywhere only)
So "Reader" is now a profil for me. It's like a supervisor profile but without some modify rights. 
I made it clear from the start that I had created a "Reader" profile in the first post  
 
Currently, with Albert user we can create project with "sub-project" empty ! This is my issue I guess. Because if it is empty, the project is create on the root  tree structure, or he is not supposed to have creation rights.

Albert default profile : My Reader Profile (because he don't be able to create project anywhere but only where he has a Project Leader profile on some project (like 1.1.1 and his sub-project)) 
Albert has "Project Leader" profile on 1.1.1 (and his all sub-project inherited)

So Albert should have right to create project only under 1.1.1. Not de rest. 

Thank for help,

Best regards,
Florian



 

Good Morning ! 

To put-it in a nutshell, I have 4 profiles in this order: 
- [None rights profile] --> Order 205 --> Absolutely none rights everywhere
- [Reader profile]  --> Order 210 --> Reader rights everywhere (not reader+)
- [Project Creator profile] --> Order 220 --> Reader rights everywhere but with creator rights on project. 
- Project Leader --> Order 310 --> defaults ProjeQtor rights (no modify on this profil)

If I have understood correctly, the lower the order number, the more weight it has compared to the higher ones. 
So, in my tree structure, I have this for Albert : 

1 - Global DSI  --> here [None rights profile]
   |- 1.1 - Application & office service --> here [Reader profile]
           |- 1.1.1 - Application pole --> here [Project Creator profile]

And when Albert create a new project --> he has Project Leader profile by default (it's his default profile on his account). 

With this configuration, I identify many bugs: 
 1 - When Albert create a project : the default sub-project selected is where you are in the proejct tree (by example : 1.1), regardless of the rights on that part of the project tree. If we save, the project is created under this sub-project, even if we have no rights to create it here !
When you look at the list of sub-projects, you should only find sub-projects that you have the rights to create, right? However, we systematically find there the sub-project of our selector.

2 - When Albert creates a project: if he selects an empty choice in the sub-project, the project is created on the root project! Maybe because he has a default project manager profile on his account, but this is annoying. Isn't there a way to allow or disallow project creation on the root by account?

3 - Although Albert has no rights to 1 - Global, so he has no inheritance rights to 1.2, but he can still see the tree of all project names in the project selector. (But of course he does not see the projects in the project list).

Thank you,

Best regards,
Florian 

Hi Alain ! 

I have configured the profiles in this way to give more weight to the reader's profile than the project leader profile. 
The aim is to have the reader's rights on a part of the project tree (not the whole project tree : the rest is with non right profile), and to give him the possibility to read and create his own project with all the rights (Project Manager profile by default) without having the right to modify the existents projects managed by others in the same sub-project (except if he has been added with the Project Manager profile of course)

By the way, thank you very much for your training !

Best regards,
Florian