> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/tutorials/hide-the-launcher.md).

# Hide the Launcher

Hide the launcher button so the survey appears without a persistent icon

Hide the launcher for your survey so that it appears according to your visibility rules without showing a persistent icon on your site.

#### How to Hide the Launcher

1. Open your survey and go to **Settings → Design → On-Site**. If the survey uses your account defaults, turn on **Override Design Settings** first, or change it for every survey under **Settings → Design Defaults → On-Site**.
2. Under **Launcher**, pick the **No Launcher** card.

The launcher's own options (radius, scale, layout, text and icon) disappear from the page while **No Launcher** is picked, and come back when you choose **Circle** or **Bumper** again. Nothing is lost in between — the values are kept.

Now your survey will appear according to your trigger rules without a launcher in the corner. When the survey is closed, it will immediately hide from view; whether it comes back depends on what you chose under [Delivery → Frequency](/polls/visibility-settings.md#frequency).

{% hint style="info" %}
A survey with no launcher has to open by itself or be opened from code. The **Ask on Arrival**, **Ask After Engaging**, **Ask in a Modal** and **Open From Code** patterns on [Delivery → Trigger](/polls/visibility-settings.md#trigger) all do this, and each one tells you whether it needs the launcher on or off.
{% endhint %}


---

# 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.zigpoll.com/tutorials/hide-the-launcher.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.