# Tag provider restriction

**URL:** <https://forum.inductiveautomation.com/t/tag-provider-restriction/76353>\
**Category:** Ignition\
**Created:** [July 13, 2023, 8:52pm UTC](https://forum.inductiveautomation.com/t/tag-provider-restriction/76353 "2023-07-13T20:52:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahman.tarek](https://avatars.discourse-cdn.com/v4/letter/r/b77776/32.png) [@rahman.tarek](https://forum.inductiveautomation.com/u/rahman.tarek)\
**Post date:** [July 13, 2023, 8:52pm UTC](https://forum.inductiveautomation.com/t/tag-provider-restriction/76353/1 "2023-07-13T20:52:29Z")

</div>

Hello,

I have a use case where i have a project with an assigned tag provider. While in the designer we cant let users have access to any other tag providers except the assigned one. How do i build security so the other tag providers cannot be access from the tag browser?

---

<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:** [July 13, 2023, 8:57pm UTC](https://forum.inductiveautomation.com/t/tag-provider-restriction/76353/2 "2023-07-13T20:57:46Z")

</div>

You cannot.

Tags are global resources, not project resources. You can put up some guardrails with tag security.

But you should know, if you don't already, that anyone with access to a designer can do anything anywhere in the gateway, period.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [July 13, 2023, 9:09pm UTC](https://forum.inductiveautomation.com/t/tag-provider-restriction/76353/3 "2023-07-13T21:09:23Z")

</div>

You could consider letting them do design work in a development gateway with the two-hour trial licence which they could reset as required. When the project is ready for production it could be ported to the production gateway by a production administrator.