# Create User Button

**URL:** <https://meta.discourse.org/t/create-user-button/136067>\
**Category:** Feature\
**Created:** [December 16, 2019, 8:16am UTC](https://meta.discourse.org/t/create-user-button/136067 "2019-12-16T08:16:53Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Tris20](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tris20/32/264639_2.png) [@Tris20](https://meta.discourse.org/u/Tris20)\
**Post date:** [November 9, 2022, 9:29pm UTC](https://meta.discourse.org/t/create-user-button/136067/19 "2022-11-09T21:29:37Z")

</div>

I don’t remember the exact details, but I think there was a way to either disable ldap and login locally, or have both types of log in possible. Something like enabling these:

 ![image](https://global.discourse-cdn.com/meta/original/4X/f/b/5/fb503d7d1fa7c09df50f2612608c0e5047f05fc4.png)  
and disabling one or two of the ldap login settings. I’m not recommending you mess with this on production just in case, but if you have a staging server see if changing those makes it possible to resolve the first login.

Otherwise is there anyone with an LDAP account who has left the platform? For our server I ended up anonymising someone who had left. It basically decouples the account from email and login, but keeps the account there so I can give it a variety of permissions and impersonate it(after giving it an appropriate name). Likewise I gave it some API keys and use it to perform automated tasks.

---

_[View the full topic](https://meta.discourse.org/t/create-user-button/136067)._
