Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.0][8.0] project_baseuser Missing 'Projects Administrator' group #59

Closed
JordiBForgeFlow opened this issue Jan 23, 2015 · 5 comments
Closed
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@JordiBForgeFlow
Copy link
Sponsor Member

@dreispt I'm interested to use this module. However I have the following concerns:

  • If the group "Project Manager" can only view the projects they manage, why can they still access to the project configurations settings for all projects?
  • Who will then have access to view all projects? I can see that in an organization, directors will need to have access to list all projects.
  • In an organization that has a Project Management Office administrative department, a PMO Project Administrator role would typically have full access to all projects and also Project Configuration, because they provide service to all Project Managers in the organisation.

Would it make sense to add the following changes?

  1. Add a new group "Project Administrator", that has full access to all projects + access to the Project Configuration menus.
  2. Remove the authorisations to the group "Project Manager" to access to the Project Configuration menus.

Regards,
Jordi.

@dreispt
Copy link
Sponsor Member

dreispt commented Jan 23, 2015

For my use case, it was OK to use the super admin to manage all projects.
I now realize that the "Project Manager" group is closer to a Project Administrator, but is suiting both roles.

An improved granularity is a nice addition. I agree with you proposed changes.
👍

@angelapper
Copy link

I tried this on v.8, it dose not work, the rule user_id = user.id did not prevent

@pedrobaeza
Copy link
Member

Any news on this?

@rafaelbn
Copy link
Member

dalonsod pushed a commit to solvosci/project that referenced this issue May 28, 2019
@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

5 participants