Hi everybody,
Thank you !
Thanks to your precision, I finally realised that creating a profile with no rights was not the right solution.
So now I have the right rights everywhere: my user only sees what he is supposed to see everywhere: project view, planning, project selector... and he can create projects only in some sub-projects
But the bug of creating a project on a project where you only have read rights still exists.
You can try it: put rights on a read-only project, select it in the project selector, then create a new project: it will be automatically selected as a sub-project (although it will not appear in the list of sub-projects if you look at the drop-down menu) and if you save: the project is created under this project in spite of only reader access !
And sorry for creating a topic in the submit issues section, but in my opinion they were 2 different issues.
So now it's just the bug at creation.
To me we should close this topic and leave the other one open, and focus it on this bug.
What do you think about it?
With kind regards,
Florian
Support us on Capterra
