> 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/august-2026/august-29-2026.md).

# August 29, 2026

Hey Storylaners! More control. Less asking for help. This release is about removing friction -\
self-serve setup, and the small things that used to slow your team down.\
Six updates.

### 🔑 API keys and MCP - now fully self-serve

API keys and MCP are now set up directly from **Settings → Integrations** - no need to contact support.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FniktILW8YidRdpcDHg4t%2FMCP%3AAPI%20self-served.gif?alt=media&amp;token=8bab9a57-e512-4486-8911-16873245cc6d" alt=""><figcaption></figcaption></figure>

**API keys** Generate separate keys for each integration so you can safely rotate access when needed.&#x20;

**MCP** Copy the Storylane MCP server URL and paste it into any supported AI client.&#x20;

Supported clients: Claude, ChatGPT, and Microsoft Copilot. More to come.

***

### 🔔 Webhooks now set up through Alerts

Webhook configuration has moved. Instead of a separate integration, webhooks are now set up directly inside an Alert.

* Go to **Settings → Alerts**
* Click **"Create first Alert"**
* Toggle on **Webhooks**

<img src="https://docs.storylane.io/~gitbook/image?url=https%3A%2F%2F2431356420-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FN8hWd9k2Pbb6YSWO4pUQ%252Fuploads%252F2o9HGICgJmd8HF1zwcZW%252FScreenshot%25202026-08-19%2520at%25208.14.19%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Db1f261c3-5496-425d-a391-0223cea9865e&#x26;width=768&#x26;dpr=3&#x26;quality=100&#x26;sign=7aade9a9b82919ee920eeb26e8cc9d2a&#x26;sv=3" alt="" height="263" width="628">

* Paste your **Webhook URL** — this is the URL where you want to receive webhook events
* Add **Custom headers** if needed. Custom headers let you attach extra key-value pairs to every webhook request — useful for passing authentication tokens, routing identifiers, or any metadata your receiving endpoint expects. Click **"+ Add header"** to add one
* Use **Test webhook** to confirm everything is working, then hit **Save**

{% hint style="info" %}
Custom headers let you pass authentication tokens, routing identifiers, or any metadata your endpoint expects.
{% endhint %}

***

### 🎙️ AI voiceover in Media to Demo

When converting images to a demo, you can now enable AI voiceover directly in the creation modal.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FKjTN7xWM3VPClOXu03Aj%2FScreenshot%202026-09-09%20at%2015.26.34.png?alt=media&amp;token=0488d631-3668-4220-b299-adf8f0e64806" alt=""><figcaption></figcaption></figure>

Toggle on **AI voiceover**, select a voice, and voiceover will be generated and applied to every step of the created demo automatically.

Supports PNG, JPG, and WEBP - up to 20 images per demo.

***

### 👥 Export team members

You can now export your full member list directly from **Settings → Team**.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FLZV49oGibLvxlg2wF8Qh%2Fexport%20members.gif?alt=media&amp;token=72c12028-5bd1-4183-905b-38694b54958c" alt=""><figcaption></figcaption></figure>

Click the **⋯ menu** in the top right of the Members page and select **Export members**. Exports include name, email, role, and team.

***

### 🍪 Cookie consent for share pages

For teams that need additional GDPR-compliant demo sharing, you can now enable a cookie consent banner on share pages as well (previously only embedded demos).

Go to **Settings → Workspace** and toggle on **Show cookie consent banner on share pages**. When enabled, visitors see an Accept/Decline prompt before any tracking begins.

<div align="left"><figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FmNkRumu1ZBVyd3wttied%2FScreenshot%202026-09-09%20at%2015.28.30.png?alt=media&amp;token=72e50f44-8655-465f-8a5c-7451ac8a14f0" alt="" width="563"><figcaption></figcaption></figure></div>

Tracking only starts after the visitor accepts — viewers who decline are not tracked.

***

### 🖼️ Image position and zoom for intro/outro screens

You can now control which part of your cover image is shown on intro and outro screens - and adjust the size of the logo displayed on top of it.

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

Crop and reposition the cover image to show exactly the right area, and scale the logo to fit your layout.

Find these controls in the intro/outro screen editor.

***

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.storylane.io/changelog/august-2026/august-29-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.