# Disable Chrome/Edge/Firefox Developer Tools for Perspective pages **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [February 16, 2023, 9:53pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975 "2023-02-16T21:53:37Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jay\_doshi](https://avatars.discourse-cdn.com/v4/letter/j/9d8465/32.png) [@jay\_doshi](https://forum.inductiveautomation.com/u/jay_doshi)\ **Post date:** [February 16, 2023, 9:53pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975/1 "2023-02-16T21:53:37Z")
Is there a way to Disable Chrome/Edge/Firefox Developer Tools for Perspective pages. The concern is that if we are using component level security, some information might become available through the developer tools. ---
**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:** [February 16, 2023, 9:56pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975/2 "2023-02-16T21:56:08Z")
No. The browser belongs to the user. If you don't want data exposed, don't send it to the browser in the first place. ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [February 16, 2023, 11:21pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975/3 "2023-02-16T23:21:07Z")
> [@jay\_doshi](#): > > some information Could you elaborate on your concerns? ---
**Author:** ![jay\_doshi](https://avatars.discourse-cdn.com/v4/letter/j/9d8465/32.png) [@jay\_doshi](https://forum.inductiveautomation.com/u/jay_doshi)\ **Post date:** [February 17, 2023, 5:25pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975/4 "2023-02-17T17:25:53Z")
Say for example, there is a URL on a view that should only be visible for user with appropriate credentials. Is there a way that the URL get exposed under the Developer Tools. ---
**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\ **Post date:** [February 17, 2023, 5:56pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975/5 "2023-02-17T17:56:59Z")
Even _if_ they knew the URL, but they don't have the proper permissions, they won't be able to access it. Of course, this is assuming you properly setup security. Check out [Security in Perspective - Ignition User Manual 8.1 - Ignition Documentation (inductiveautomation.com)](https://docs.inductiveautomation.com/display/DOC81/Security+in+Perspective) ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [February 17, 2023, 7:04pm UTC](https://forum.inductiveautomation.com/t/disable-chrome-edge-firefox-developer-tools-for-perspective-pages/69975/6 "2023-02-17T19:04:46Z")
Crafting a URL based on secure information is a bad idea in general. As @andrews has already suggested, the "secure" way to manage something like this is to create a URL which directs to a resource on which you've properly applied Security Settings (right-click the View node in the Project Browser and select "Security Settings"). That being said, there are times when you might need to parameterize a URL with some value - perhaps you want to to something like this where you parameterize the page with the employee ID of another employee: `my.gateway.local:8043/data/perspective/client/MyProj/administration?employeeId=b1cb353d-bb7d-4aa7-a364-ba4612e8f2cb ` That URL would indeed be visible in the DOM, but you should be applying security to how that employeeId is supplied, by most likely hashing the `employeeId` value and unhashing the parameter of the Page which uses it.