# Table in database to store user credentials instead of gateway

**URL:** <https://forum.inductiveautomation.com/t/table-in-database-to-store-user-credentials-instead-of-gateway/100842>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [January 14, 2025, 4:32am UTC](https://forum.inductiveautomation.com/t/table-in-database-to-store-user-credentials-instead-of-gateway/100842 "2025-01-14T04:32:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Fran\_Dujmovic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/fran_dujmovic/32/70280_2.png) [@Fran\_Dujmovic](https://forum.inductiveautomation.com/u/Fran_Dujmovic)\
**Post date:** [January 14, 2025, 7:35am UTC](https://forum.inductiveautomation.com/t/table-in-database-to-store-user-credentials-instead-of-gateway/100842/2 "2025-01-14T07:35:34Z")

</div>

Take a look at this thread;

> [@Database location in Ignition](https://forum.inductiveautomation.com/t/database-location-in-ignition/59630/6):
>
> Yes. Commonly statements of the form Insert Into someTable (...) Select ... From otherTable.

Generally speaking you'd want a database connection for your users and a user source configured. You'd then import the users and their roles from your own DB into your Ignition DB via the query browser.

---

_[View the full topic](https://forum.inductiveautomation.com/t/table-in-database-to-store-user-credentials-instead-of-gateway/100842)._
