# User-Specific Authentication for Enabling Historian

**URL:** <https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682>\
**Category:** Ignition\
**Created:** [February 14, 2024, 2:02pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682 "2024-02-14T14:02:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Liliya\_Boyadjieva1](https://avatars.discourse-cdn.com/v4/letter/l/5f8ce5/32.png) [@Liliya\_Boyadjieva1](https://forum.inductiveautomation.com/u/Liliya_Boyadjieva1)\
**Post date:** [February 14, 2024, 2:02pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682/1 "2024-02-14T14:02:07Z")

</div>

I have several groups of people who want to use Ignition at my workplace. Some of them are designing pages/reports that are used in production, and others (technicians) just need to be able to sporadically set up a page to monitor equipment status, i.e. to troubleshoot a bug. I currently have a database for production tag history (DB1) and another for troubleshooting data (DB2).

_My question is_ : Is there any way to validate user roles when enabling history on a **specific** database? Can I somehow give access to our technicians to the Designer and Tag History on DB2, but restrict write access to DB1? I want to separate the databases to avoid having someone inadvertently flood the production database with temporary data and to have better control over pruning.

Or, more broadly, am I approaching the problem in the wrong way? What is a good way to manage different "types" of designers?

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [February 14, 2024, 2:14pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682/2 "2024-02-14T14:14:41Z")

</div>

You should have separate gateways for prod and testing. Solves the access permission issues, and also makes sure the prod projects are inaccessible to those who have no business putting their dirty fingers in there.

---

<div class="post-metadata">

**Author:** ![Liliya\_Boyadjieva1](https://avatars.discourse-cdn.com/v4/letter/l/5f8ce5/32.png) [@Liliya\_Boyadjieva1](https://forum.inductiveautomation.com/u/Liliya_Boyadjieva1)\
**Post date:** [February 14, 2024, 2:18pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682/3 "2024-02-14T14:18:07Z")

</div>

> [@pascal.fragnoud](#):
>
> You should have separate gateways for prod and testing.

We do, we have a test, a certification and a prod gateway, but only the prod one is fully licensed. I guess we'll have to get licensing for the other environments as well. Thanks for the input

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [February 14, 2024, 2:19pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682/4 "2024-02-14T14:19:59Z")

</div>

You don't need licensing for those. You just need to go and re-enable the trial license every 2 hours, which is really not a big deal.

Have the debugging be done on the test gateway, this way you don't have to worry about permissions to sensitive stuff

---

<div class="post-metadata">

**Author:** ![Liliya\_Boyadjieva1](https://avatars.discourse-cdn.com/v4/letter/l/5f8ce5/32.png) [@Liliya\_Boyadjieva1](https://forum.inductiveautomation.com/u/Liliya_Boyadjieva1)\
**Post date:** [February 14, 2024, 2:40pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682/5 "2024-02-14T14:40:36Z")

</div>

That is how we currently do it, however troubleshooting often requires continuous monitoring over a few days..

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 14, 2024, 3:47pm UTC](https://forum.inductiveautomation.com/t/user-specific-authentication-for-enabling-historian/85682/6 "2024-02-14T15:47:13Z")

</div>

> [@Liliya\_Boyadjieva1](#):
>
> What is a good way to manage different "types" of designers?

Be very careful training anyone you allow to use a designer on a production gateway. The security roles for designer access just let in--once in, any designer can do things that break the whole gateway, and/or break security in the whole gateway. Designers just have "guard rails", not complete security barriers.