> 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/march-2026/march-21th-2026.md).

# March 21th, 2026

Hey Storylaners! It's time to make demos more measurable and presentable. This release focuses on three things:

* Who’s actually driving results
* How demos perform in live settings<br>

Introducing.... 👇

### User activity&#x20;

Not all sales reps are equal. Now you can finally see who’s driving pipeline - and who isn’t.

**Now you get:**

* Leaderboard of top performers (views, leads, accounts, time, links)
* Dynamic sorting by what matters most to you
* Deep-dive into each rep’s performance

💡 *Use it for:*

* Sales performance reviews
* Identifying top performers&#x20;
* Coaching underperforming reps

Try interactive demo below 👇

{% @storylane/embed subdomain="app" linkValue="8swgfgon0bco" url="<https://app.storylane.io/share/8swgfgon0bco>" %}

***

### Presenter mode (run better live demos)

Live demos shouldn’t feel like you’re reading tooltips. Now they don’t.

**What changed:**

* Presenter mode is now available directly in **Share**
* Clean viewer experience > guide text is hidden
* Presenter sees **private sales notes in a separate tab**
* Add custom notes per step to guide your story
* Optional on-screen pointer (with color control)
* Keyboard navigation for smoother flow

💡 *Perfect for:*

* Live demos and Conferences

Try interactive demo below 👇

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

***

### **Guides on video steps**

Until now, videos were passive. Not anymore.

You can now add tooltips and hotspots directly on video steps.

It helps you:

* Highlight key moments in motion
* Explain complex flows step-by-step
* Add CTAs inside videos

***

### One more thing 👀

We’re actively working on a **new, more polished editor experience**.

Today, it’s automatically available to free users, and Starter users can switch anytime with a single click - but things are evolving behind the scenes, and we can’t wait to bring it to everyone soon 🙂

***

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


---

# 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/march-2026/march-21th-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.