feat: Adjust root permissions

[liza-veis]

What feature?

Adjust needed permissions and make sure all of them work as expected. The resources should be disabled on the backend as well.

Rules:

• [x] Projects page (sidebar and page itself): View All Projects, Manage All Projects.
• [x] Analytics page (sidebar and page itself): View All Projects, Manage All Projects.
• [x] Contributors page (sidebar and page itself): Manage All Projects.
• [x] Root access management page (sidebar and page itself): Manage Access.
• [x] Project access management page (button and page itself): Manage Access.
• [x] User groups and project groups (create, edit, delete): Manage Access.
• [x] Create a new project (button): Manage All Projects.
• [x] Delete a project (option): Manage All Project.
• [x] Edit project (option): Manage All Project.
• [x] Setup analytics button and api key generation: Manage All Projects.

Screenshots

No response

[VeronikaHordus]

For QA: Check whether the link on the Logo on header redirects users to correct pages with certain permission type.

[GvoFor]

Questions

• If rule states "...: View All Projects, Manage All Projects.", then this means that user shoud have AT LEAST one of the listed permissions, right? (or all of them?)
• If there is nothing left to display in the menu (for example user has only View All Projects permission and not Manage All Projects, then both edit and delete options should disapear), then I should not render the menu component (button with ellipsis) itself at all, right?
• In rules list, Manage Access permission was mentioned, but currently in project we have Manage User Access. Are these the same permissions? or should I create new Manage Access permission? or should I rename Manage User Access to Manage Access?
• Our project details page contains contributors list and it can be accessed with just View All Projects permission, but Contributors page can be accessed only with Manage All Projects permission. So should I render contributors list in this case?

[liza-veis]

If rule states "...: View All Projects, Manage All Projects.", then this means that user shoud have AT LEAST one of the listed permissions, right? (or all of them?)

yes, one of them.

If there is nothing left to display in the menu (for example user has only View All Projects permission and not Manage All Projects, then both edit and delete options should disapear), then I should not render the menu component (button with ellipsis) itself at all, right?

yes, would be nice to hide the options menu.

In rules list, Manage Access permission was mentioned, but currently in project we have Manage User Access. Are these the same permissions? or should I create new Manage Access permission? or should I rename Manage User Access to Manage Access?

yep, It's the sam permission, no need to rename or create a new one.

Our project details page contains contributors list and it can be accessed with just View All Projects permission, but Contributors page can be accessed only with Manage All Projects permission. So should I render contributors list in this case?

Contributors page will be for all contributors configuration, so only users with Manage All Projects (who is able to edit contributors) can access it. It will be hard to show all contributors, but disable actions for some of them if user has/doesn't have project-specific permissions. But it's ok for the project details page, + contributors on this page are mostly for view and tracking purposes, so users with View All Projects permission should see them.

[VeronikaHordus]

@GvoFor Everything seem to work as required, only I have one point to make clear. The Project Access Managment page is unaccessible for user with Manage Access rights untill he has also the View All Projects permission. (If I wold paste the URL of the Project Access Managment page I am redirected to the 404 page). Is that right?

[GvoFor]

Hi. Thanks for noticeing. Looks like a bug for me. I think I should fix it However I'm not sure