Add Team Admin role that can only can edit its own team.
#11584
Assignees
Comments
drt-infor
changed the title
bergquist
changed the title
Team Admin role that can only can edit its own team.
|
I would really like to see this implemented. It would remove the need for the Org admin(s) to manage users for all Teams within the Org. |
idavidmcdonald
pushed a commit
to alphagov/reliability-engineering
that referenced
this issue
Sep 4, 2018
- It is rare that teams are using the GDS default dashboard because they are now creating their own dashboards and using those - We also have other sources of metrics meaning teams may also use the container metrics dashboard or metrics for tools like elasticsearch. Based on this I have: - Added a short explanation for how team folders are organised - Added definitions of the purpose of the dashboards in the General folder - Moved the detailed explanation of the default application dashboard into it's own page (but have made no content changes) - Removed some of the simpler content as I don't think we have seen evidence of users struggling to use Grafana so far Note: I have kept the section on team dashboard permissions brief and vague - essentially contact us for help - as I think we need to do more on team permissions. At the moment, teams will not be able to manage the permissions for users of their team without having admin privileges of the whole system as per grafana/grafana#11584. This may be something we want to investigate further to avoid us needing to manage all user permissions in terms of which teams they can access and instead being able to put this burden on the teams themselves.
|
@drt-infor @paulsson I have finished this feature on this pull request: #13144 , and waiting to be merged. |
idavidmcdonald
pushed a commit
to alphagov/reliability-engineering
that referenced
this issue
Sep 11, 2018
- It is rare that teams are using the GDS default dashboard because they are now creating their own dashboards and using those - We also have other sources of metrics meaning teams may also use the container metrics dashboard or metrics for tools like elasticsearch. Based on this I have: - Added a short explanation for how team folders are organised - Added definitions of the purpose of the dashboards in the General folder - Moved the detailed explanation of the default application dashboard into it's own page (but have made no content changes) - Removed some of the simpler content as I don't think we have seen evidence of users struggling to use Grafana so far Note: I have kept the section on team dashboard permissions brief and vague - essentially contact us for help - as I think we need to do more on team permissions. At the moment, teams will not be able to manage the permissions for users of their team without having admin privileges of the whole system as per grafana/grafana#11584. This may be something we want to investigate further to avoid us needing to manage all user permissions in terms of which teams they can access and instead being able to put this burden on the teams themselves.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would like to have the ability to designate a member(s) in a given Team as a "Team Admin" so that they could self-manage the ability to add/remove users to/from their Team.
We are currently running Grafana 5.0.3 in Docker containers on Linux.
The text was updated successfully, but these errors were encountered: