# Hide Gateway Scripting Libraries from Other Users in Perspective Project? **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [August 25, 2025, 12:28pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146 "2025-08-25T12:28:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [August 25, 2025, 12:28pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146/1 "2025-08-25T12:28:42Z")
Hi everyone, In my Perspective project, I’ve created several libraries in the Gateway Scripting section. Is there a way to hide these libraries from other Gateway users so they are not visible or accessible? Any guidance would be greatly appreciated. Thanks in advance! ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [August 25, 2025, 12:31pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146/2 "2025-08-25T12:31:37Z")
If you are trying to protect proprietary information, the only reliable way to do that is with a module. And even those can be reverse-engineered to a point. ---
**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:** [August 25, 2025, 12:36pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146/3 "2025-08-25T12:36:36Z")
A more detailed discussion: > [@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… ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [August 25, 2025, 2:47pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146/4 "2025-08-25T14:47:20Z")
Hi, Can you help to understand this. I will be thankful to you. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [August 25, 2025, 3:16pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146/5 "2025-08-25T15:16:10Z")
If someone has access to the designer, they can read any Ignition project or configuration data. Full stop. There's no way to prevent that, and there won't be for the foreseeable future. The only thing _close_ to intellectual property protection is to use the module SDK to compile your business logic into a module. You will, however, find that Java code is trivially decompilable unless you go to great efforts to _obfuscate_ your code at build time. Protecting source code is **fundamentally** incompatible with delivering code to end users to execute on their own hardware. No matter the language, with sufficient effort it can be decompiled or reverse engineered. Disclaimer: This is just my personal opinion, not an official stance of Inductive Automation LLC, I am not a lawyer, etc. Instead of burning money on ultimately pointless attempts to "protect" source code: 1. Establish a relationship with customers where the valuable part is your _support_ of the code, not giving them a black box they cannot inspect. 2. Be willing to fire customers for shenanigans like attempting to reverse engineer your IP, and accept that _anyone willing to do that was not a good customer in the first place_. ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [August 25, 2025, 4:25pm UTC](https://forum.inductiveautomation.com/t/hide-gateway-scripting-libraries-from-other-users-in-perspective-project/110146/6 "2025-08-25T16:25:46Z")
@paul-griffith sums it up the best.