# Launch Client without Clent Launcher

**URL:** <https://forum.inductiveautomation.com/t/launch-client-without-clent-launcher/23136>\
**Category:** Ignition Early Access\
**Created:** [March 7, 2019, 6:59pm UTC](https://forum.inductiveautomation.com/t/launch-client-without-clent-launcher/23136 "2019-03-07T18:59:29Z")\
**Posts on this page:** 1\
**Showing post:** 38

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [August 15, 2019, 5:02pm UTC](https://forum.inductiveautomation.com/t/launch-client-without-clent-launcher/23136/38 "2019-08-15T17:02:34Z")

</div>

I think an alternative to what you are trying to accomplish would be this:

1. setup the application configuration however you like on some launcher. maybe this is on a dev machine or separate user account, whatever.
2. set the `lock.configuration` property in the launchers json file (again, in `.ignition/clientlauncher-data`) to `true`
3. replace the json file on the user machine that you want to lock the configuration of with the one that you configured.

You could do this on the launcher you want to configure itself and simply toggle the `lock.configuration` value as needed.

Coupling the `privileges` of a launcher to a specific gateway seems like a recipe for disaster. the lock.configuration property should be adequate to limit users from modifying the configuration of the launcher.

---

_[View the full topic](https://forum.inductiveautomation.com/t/launch-client-without-clent-launcher/23136)._