> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/deployment/rollout/how-userlane-is-deployed.md). # How Userlane is deployed The recommended deployment path, why full coverage matters, and on-request exceptions. Userlane runs as a browser extension deployed centrally by IT through device management. The extension delivers all product capabilities to end users inside web applications. ## The browser extension The extension is a single component installed once per browser. It carries everything Userlane provides to end users: guides, the Assistant[^1], HEART[^2] tracking, App Discovery[^3], Contextual Actions, and change communication. Supported browsers: * [Chrome](https://chrome.google.com/webstore/detail/userlane/oaienfpdbimabhlgjlbdpocbogaijnam) * [Edge](https://microsoftedge.microsoft.com/addons/detail/userlane/joephgegnilhnnnocnkigpmmamgghage) * Firefox (distributed through the organization's device management) ## How it is deployed The extension is pushed silently through the organization's device management platform, such as Microsoft Intune. It connects to single sign-on (SSO) so end users are authenticated automatically. End users take no action. After the extension is installed, add the target application domains in the portal so tracking and the extension activate on the right pages. See [Set up the application URL](/getting-started/first-steps-in-the-portal/set-up-the-application-url.md). For the full rollout procedure, including browser-specific configuration and policy settings, see [Roll out the extension](/deployment/rollout/roll-out-the-extention.md). ## Alternative: the JavaScript snippet Some environments cannot use a centrally managed browser extension, for example mobile web applications or platforms where device management is not available. For these cases, a developer can add a JavaScript snippet to the application's front-end source code instead. The snippet delivers Userlane capabilities within the single application it is installed in. App Discovery depends on the browser extension. The snippet is in the portal under **Settings** > **Setup**. A developer adds it before the closing `` tag. For the full code reference, including user identification and the authenticated variant, see the [Quick reference of commands](/developer-reference/quick-reference-of-commands.md). The browser extension is the right choice for most deployments. If you are unsure which method fits your environment, [contact your customer value team](/support/contact-and-escalation.md) before starting implementation. ## Relevant articles {% content-ref url="/pages/ZbAA5aBZMukn2qqLRZji" %} [Roll out the extension](/deployment/rollout/roll-out-the-extention.md) {% endcontent-ref %} {% content-ref url="/pages/SRW9iMERFNl0SSjAfJnd" %} [Environment prerequisites](/deployment/rollout/environment-prerequisites.md) {% endcontent-ref %} {% content-ref url="/pages/IkbYytjTIP1b0c4ZNCbM" %} [End-user single sign-on](/deployment/rollout/end-user-single-sign-on.md) {% endcontent-ref %} {% content-ref url="/pages/fsN54CJn1Adx0IhuudPQ" %} [Set up the application URL](/getting-started/first-steps-in-the-portal/set-up-the-application-url.md) {% endcontent-ref %} ## FAQ
Which browsers does Userlane support? Chrome, Edge, and Firefox. See [Roll out the extension](/deployment/rollout/roll-out-the-extention.md) for minimum versions.
Can Userlane be deployed without a browser extension? Yes. A developer can add a JavaScript snippet to a specific application's source code where a browser extension is not possible. The snippet is scoped to that single application. Speak to your Customer Value Manager to confirm whether this is the right approach.
Do end users need to do anything? No. IT pushes the extension through device management, and SSO authenticates end users automatically.
Does Userlane work on desktop applications? No. Userlane operates in the browser only. Desktop applications, native mobile applications, command-line tools, and server-side processes are outside scope.
[^1]: The Assistant is the floating in-app panel that end users interact with. It provides access to guides, announcements, surveys, search, and connected knowledge sources. [^2]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100. [^3]: App Discovery scans which applications are in use and how heavily. It depends on the browser extension being installed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.userlane.com/deployment/rollout/how-userlane-is-deployed.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.