> 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/developer-reference/hide-userlane-on-specific-pages.md).

# Hide Userlane on specific pages

Control Userlane visibility per page using display rules, audiences, the hide command, or passive mode.

## About hiding Userlane content

Userlane content can be restricted so that it does not appear on particular pages, or for particular people. Common reasons are a login page, a page holding sensitive data, or a group of users who should not receive guidance.

There are three ways to do it:

* Option A, configured in the Portal: display rules and audiences.
* Option B, implemented in application code: the hide command.
* Option C, arranged with Userlane: passive mode.

## Option A: display rules and audiences

### Keep content off a page

A display rule controls where content is placed, so it also controls where content does not appear. This works where the page has a URL fragment that is not part of the domain and appears only on that page, for example `/login`.

See [Content operations](/assistance/content-operations.md).

### Keep content away from a group of people

An audience is a reusable group defined by attribute rules, and content can be targeted to it. Restricting content to one audience keeps it away from everyone outside that audience.

See [Audiences](/administration/audiences.md).

## Option B: the hide command

Userlane can also be hidden programmatically on specific pages, for example the login page:

```javascript
// hide Userlane
Userlane('hide');
```

To show Userlane again after hiding it, use the initialize command:

```javascript
// initialize command
Userlane('init', property_ID);
```

{% hint style="info" %}
**Good to know**

* To open the Assistant from a specific button, use the `openAssistant` command. See [Implement a command to open the Assistant](/developer-reference/implement-a-command-to-open-the-assistant.md).
* Where links are used to share Guides, the hide command does not apply on the login page. The Guide starts on the login page if the login URL is listed on the Application URLs page in the application settings. To prevent that as well, a developer has to remove the Userlane snippet from the login page.
  {% endhint %}

## Option C: passive mode

Where the application has its own button that should trigger Userlane, do not use the hide command. Contact Userlane instead, and the right setup will be arranged directly.

## Relevant articles

{% content-ref url="/pages/TKBRGmMaapWk0xuF3XwG" %}
[Audiences](/administration/audiences.md)
{% endcontent-ref %}

{% content-ref url="/pages/BkK6BtMQAoCXdpgXSBa5" %}
[Targeting](/assistance/content-operations/targeting.md)
{% endcontent-ref %}

{% content-ref url="/pages/cg5g8Xki3RfJej7DhphW" %}
[Content operations](/assistance/content-operations.md)
{% endcontent-ref %}

{% content-ref url="/pages/9LSBBfW7D6q4LDf7Zi6F" %}
[Implement a command to open the Assistant](/developer-reference/implement-a-command-to-open-the-assistant.md)
{% endcontent-ref %}


---

# 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/developer-reference/hide-userlane-on-specific-pages.md?ask=<question>&goal=<user_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.