> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/changelog/october-2026/october-12-2026.md).

# October 12, 2026

Hey Storylaners! A few updates on this release giving you more control over how your demos look and who they alert you about.

***

### 🔔 Smarter alert triggers

Alerts now support more precise conditions - so you get notified about the right visitors, not every visitor.

Find it in **Settings → Alerts → Create Alert → Trigger conditions**

**New trigger conditions**

Five new conditions available when creating or editing an alert:

* **Company revenue** - filter by annual revenue range ($0–$1M up to $10B+)
* **Company size** - filter by employee count (1–10 up to 10K+)
* **Domain** - include or exclude specific domains. Add comma-separated domains via the modal
* **Lead known** - filter by attribution type: Direct, Attributed, or Nurtured
* **Active deal trigger** - get alerted when a demo is viewed by a contact associated with an active deal in your CRM. Filter by pipeline and deal stage — so you only hear about the deals that matter right now.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2F16KU7nRag0sgYcvDfC6h%2Falerts%20enriched.gif?alt=media&amp;token=08583239-1d5f-4a23-80cf-a9ebcf4bea68" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Active deal trigger requires HubSpot or Salesforce to be connected.
{% endhint %}

***

### 🎛️ Nav bar: three visibility modes

The nav bar now supports three modes - giving you more control over how it appears during a demo.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FX5z7Fmsb4BIFFj0dztam%2FSetup%20navigation%20spotlight.png?alt=media&amp;token=74026264-7cc8-46bf-94e5-3b9719ab3361" alt=""><figcaption></figcaption></figure>

| Mode     | Nav bar        | Play bar                                                |
| -------- | -------------- | ------------------------------------------------------- |
| **Off**  | Never shown    | Hidden while playing, appears on pause, hides on resume |
| **On**   | Always visible | Always visible for timed media                          |
| **Auto** | Hover-reveal   | Hover-reveal for timed media                            |

Set it in **Demo Settings → Appearance → Setup navigation**.

**Also in this update:**

* Space bar now pauses and resumes all media types - voiceover, avatar, and video.
* Off and Auto modes share the same play bar hover-reveal behavior, but Off uses neutral colors while Auto uses your brand colors
* Existing demos with nav bar On have been migrated to Auto automatically

{% hint style="info" %}
When the nav bar is set to On, it always stays visible - including on intro and outro screens.
{% endhint %}

***

### 🎨 Richer themes

Themes now cover more of your demo experience.

{% @storylane/embed subdomain="app" linkValue="cu3vofo3aazd" url="<https://app.storylane.io/demo/cu3vofo3aazd>" %}

In addition to existing styling options, themes now apply to:

* Convert CTA
* Intro and outro screens
* Chapter menu
* Nav bar

Set your brand once. It carries through every part of the demo automatically.

***

Thanks for trusting us.\
If you have any questions, feel free to reach out at <support@storylane.io>.


---

# 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.storylane.io/changelog/october-2026/october-12-2026.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.