# Designer Security

**URL:** <https://forum.inductiveautomation.com/t/designer-security/9531>\
**Category:** Ignition\
**Created:** [January 12, 2015, 7:25pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531 "2015-01-12T19:25:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\
**Post date:** [January 12, 2015, 7:25pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531/1 "2015-01-12T19:25:03Z")

</div>

I posted this under: Re: Designer/Tag Security - Second Instance?  
but since it is such an old thread and I got no response I thought I better start a new thread.

Did anything ever happen with Nathan's suggestion that Ignition have a developer/designer permission structure? I have vendors that need access to their project on my Gateway and I am adverse to giving them access to the other projects.

[quote="nathan"]Does it make sense to implement a tag level design security structure as opposed to a larger developer/designer permission structure? I'm referring to design control permissions for: projects, windows, transaction groups and other such objects in addition to tags. To me it doesn't make sense to just do tags, unless that is somehow more significant than the others and/or much more natural to implement.

> [@Colby.Clegg](#):
>
> The first thing that comes to mind is that perhaps we could add an option to limit tag editing to certain roles, so that you could create a login that was allowed in the designer, but not allowed to modify the configuration of tags. Would this be sufficient?[/quote]

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 12, 2015, 11:36pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531/2 "2015-01-12T23:36:11Z")

</div>

Nothing has happened yet and it’s not on the timeline for 7.8. It may be worth adding to our feature requests section if it’s not there already.

Ignition isn’t currently designed to be a hosted solution, which is evident in a number of areas. I imagine one day we’ll get to work on improving this use case, and in doing so will end up re-evaluating how security and permissions work.

---

<div class="post-metadata">

**Author:** ![Kleppe85](https://avatars.discourse-cdn.com/v4/letter/k/c4cdca/32.png) [@Kleppe85](https://forum.inductiveautomation.com/u/Kleppe85)\
**Post date:** [April 25, 2017, 7:24am UTC](https://forum.inductiveautomation.com/t/designer-security/9531/3 "2017-04-25T07:24:03Z")

</div>

Is there any news regaring this?

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [April 25, 2017, 2:38pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531/4 "2017-04-25T14:38:14Z")

</div>

More security has been added to Ignition. Check out these links:  
[https://docs.inductiveautomation.com/display/DOC79/Tag+Security](https://docs.inductiveautomation.com/display/DOC79/Tag+Security)  
[https://docs.inductiveautomation.com/display/DOC79/Tag+Provider+Security](https://docs.inductiveautomation.com/display/DOC79/Tag+Provider+Security)

---

<div class="post-metadata">

**Author:** ![Kleppe85](https://avatars.discourse-cdn.com/v4/letter/k/c4cdca/32.png) [@Kleppe85](https://forum.inductiveautomation.com/u/Kleppe85)\
**Post date:** [April 25, 2017, 7:16pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531/5 "2017-04-25T19:16:00Z")

</div>

But none of these settings makes the designer display i.e. only tags for a given project? These are settings for setting restrictions to who may edit tags etc?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 25, 2017, 7:18pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531/6 "2017-04-25T19:18:19Z")

</div>

> [@Kleppe85](#):
>
> But none of these settings makes the designer display i.e. only tags for a given project?

Tags don't belong to any one project, so no.

I think at best you could partition tags by provider and then restrict editing in each provider, but nothing will let you hide those tags altogether.

---

<div class="post-metadata">

**Author:** ![Kleppe85](https://avatars.discourse-cdn.com/v4/letter/k/c4cdca/32.png) [@Kleppe85](https://forum.inductiveautomation.com/u/Kleppe85)\
**Post date:** [April 25, 2017, 8:03pm UTC](https://forum.inductiveautomation.com/t/designer-security/9531/7 "2017-04-25T20:03:33Z")

</div>

Any future updates that might include such functionallity? Would be nice to have the possibility to lock a project to a given tag provider, and then limit the designer browsing accordingly.
