# Adding new users

**URL:** <https://forums.percona.com/t/adding-new-users/5749>\
**Category:** PMM 1.x\
**Created:** [July 19, 2017, 10:36am UTC](https://forums.percona.com/t/adding-new-users/5749 "2017-07-19T10:36:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dazzla76](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@dazzla76](https://forums.percona.com/u/dazzla76)\
**Post date:** [July 19, 2017, 10:36am UTC](https://forums.percona.com/t/adding-new-users/5749/1 "2017-07-19T10:36:41Z")

</div>

I’ve scoured the documentation for this and can’t find what i’m looking for. Hopefully i’ve not missed something obvious.

How do you add additional users to pmm? on first login it asks you for username, password and optionally public key. This all works as expected and i can use chrome to login and ssh access works as well.

I need to be able to share this with members of the DBA team and i would like to be able to give each of them their own logins so not everyone needs to know the admin credentials. Is this possible?

i’ve got round it somewhat by adding entries to the .htaccess file manually but this isn’t particularly manageable when the team has around 25 members who change of a fairly frequent basis. We’d also like to be able to open up access to application teams so they can perform some level of self service on performance diagnostics.

Grafana has the concept of users and organisations but the nginx configuration seems to block all access until a user has logged in to it.

Thanks in advance

---

<div class="post-metadata">

**Author:** ![dazzla76](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@dazzla76](https://forums.percona.com/u/dazzla76)\
**Post date:** [July 19, 2017, 10:37am UTC](https://forums.percona.com/t/adding-new-users/5749/2 "2017-07-19T10:37:57Z")

</div>

oh, forgot to mention, pmm is deployed on a virtual machine, not docker

---

<div class="post-metadata">

**Author:** ![Mykola](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mykola/32/30_2.png) [@Mykola](https://forums.percona.com/u/Mykola)\
**Post date:** [July 19, 2017, 11:04am UTC](https://forums.percona.com/t/adding-new-users/5749/3 "2017-07-19T11:04:35Z")

</div>

It is very important thing for us.  
We have plenty of internal discussions about this issue.  
thank you for your feedback, I have added your post to the internal ticket.

> [@](#):
>
> Grafana has the concept of users and organisations but the nginx configuration seems to block all access until a user has logged in to it.

if you want to use both htaccess and internal grafana authorizations simultaneously it is possible to disable this grafana behaviour.  
but it will be unsupported custom modification which can broke update process.  
do you need instructions?

---

<div class="post-metadata">

**Author:** ![dazzla76](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@dazzla76](https://forums.percona.com/u/dazzla76)\
**Post date:** [July 20, 2017, 1:48am UTC](https://forums.percona.com/t/adding-new-users/5749/4 "2017-07-20T01:48:08Z")

</div>

Thank you,

Its not an emergency for us at the moment as we are only evaluating using the tooling. As long as you have it on your roadmap and a solution implemented we should be ok.

---

<div class="post-metadata">

**Author:** ![jpage](https://avatars.discourse-cdn.com/v4/letter/j/96bed5/32.png) [@jpage](https://forums.percona.com/u/jpage)\
**Post date:** [March 21, 2018, 9:58am UTC](https://forums.percona.com/t/adding-new-users/5749/5 "2018-03-21T09:58:47Z")

</div>

> [@dazzla76;49076](#):
>
> i’ve got round it somewhat by adding entries to the .htaccess file manually but this isn’t particularly manageable when the team has around 25 members who change of a fairly frequent basis. We’d also like to be able to open up access to application teams so they can perform some level of self service on performance diagnostics.
> 
> Grafana has the concept of users and organisations but the nginx configuration seems to block all access until a user has logged in to it.
> 
> Thanks in advance

This is exactly my concern!

Grafana users and organisations are unusable because of nginx access control.

Somehow related to this is [the ticket I’ve opened](https://jira.percona.com/browse/PMM-2241) explaining that the HTTP auth user must be the same in the clients that the one used in the server.

Both problems are derived from a poor authentication mechanism desing. (Understand me, PMM is a great piece of software but in my opinion this is a weakness that prevents me sharing PMM with the DEV team).