> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/sharing/embed-codes/embedding-interactive-demos/updating-your-embed-code-when-changes-are-made.md).

# Updating your Embed Code when changes are made

The only time you need to update your embed code are the following:

* Change status of mobile responsive version of the tour (Change to on or off)
* Changes to mobile button enablement (change to on or off)
* Changes to status of nav bar (change to on or off)
  * Styling changes do not require an updated embed code
* Change or add certain account level custom scripts
* White labeling your demos with your domain (going from \[yourcompany].tourial.com to demos.\[yourcompanydomain].com)

Everything else like copy changes, branding changes, screenshot/video background changes or additions or subtractions, etc are intended to all be updating in real time.


---

# 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.navless.ai/sharing/embed-codes/embedding-interactive-demos/updating-your-embed-code-when-changes-are-made.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.