# Locking Resources With Other Roles than Administrator

**URL:** <https://forum.inductiveautomation.com/t/locking-resources-with-other-roles-than-administrator/52497>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [October 29, 2021, 2:00pm UTC](https://forum.inductiveautomation.com/t/locking-resources-with-other-roles-than-administrator/52497 "2021-10-29T14:00:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rrebro](https://avatars.discourse-cdn.com/v4/letter/r/3da27b/32.png) [@rrebro](https://forum.inductiveautomation.com/u/rrebro)\
**Post date:** [October 29, 2021, 2:00pm UTC](https://forum.inductiveautomation.com/t/locking-resources-with-other-roles-than-administrator/52497/1 "2021-10-29T14:00:52Z")

</div>

Ignition has this nice feature to lock resources, we are hoping to use this to lock the customer out of some things we would consider our company’s IP. I know you can give special permissions to allow only certain roles to lock/unlock resources.

We want to be able to give the customer a User with an Administrator role but we don’t want them to be able to unlock our resources. I understand if you don’t have permission to unlock/lock resources you can’t change the permissions but if you have a User with an Administrator role, couldn’t they just create new User with the role that is required to unlock/lock resources.

How can you truly lock resources from an Administrator?

---

<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:** [October 29, 2021, 2:09pm UTC](https://forum.inductiveautomation.com/t/locking-resources-with-other-roles-than-administrator/52497/2 "2021-10-29T14:09:18Z")

</div>

There's not _really_ any way to achieve this.

Discussed elsewhere:

> [@Secured (non-text) python script for deployment](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920/3):
>
> No. Your best bet for obfuscation is to provide functionality via custom module instead. Note my use of “obfuscation” - that’s all it will ever be. You cannot prevent a moderately determined user from getting your IP as long as they have physical or virtual access to the gateway machine.

> [@Best practice to prevent to stolen ignition resources](https://forum.inductiveautomation.com/t/best-practice-to-prevent-to-stolen-ignition-resources/44344):
>
> Hi, As system integrator, there are some cases that I like to protect my resources in ignition after delivering project to client. For example creating a library that use resources like python lib and views,… In other SCADA packages I can put password and encrypted the resource. The resource can be used by system but can’t modify by others unless they know password. The protect option in ignition doesn’t work because when other can access to gateway config they can change the role and passwo…