# New Tag Permissions Model based on Security Levels

**URL:** <https://forum.inductiveautomation.com/t/new-tag-permissions-model-based-on-security-levels/34558>\
**Category:** Ignition Early Access\
**Created:** [May 8, 2020, 1:50am UTC](https://forum.inductiveautomation.com/t/new-tag-permissions-model-based-on-security-levels/34558 "2020-05-08T01:50:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [June 19, 2020, 12:45pm UTC](https://forum.inductiveautomation.com/t/new-tag-permissions-model-based-on-security-levels/34558/3 "2020-06-19T12:45:07Z")

</div>

I’m trying to port my old function for determining whether a tag is readable or writable to Ignition 8 (see [Role-based tag permission vs client visualisation](http://forum.inductiveautomation.com/t/role-based-tag-permission-vs-client-visualisation/29988))

The permissions model seems a lot more complicated though (deeper nested JSON, or-ed and and-ed together).

Would there be an easier way to check if the current user is able to read or write a tag?  
Or is there something coming to bind enabled/editable/visible/… properties to tag readability? Like a special expression perhaps?

It seems like a lot of work to get it right with all special cases, if that functionality could be added in one of the next versions.

---

_[View the full topic](https://forum.inductiveautomation.com/t/new-tag-permissions-model-based-on-security-levels/34558)._