> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/changelog/sneak-peek-feature-previews.md).

# Sneak peek: Feature Previews

24 September 2024

{% hint style="success" %}
**Update: this feature is now live!** [Read more about Feature Previews on our documentation](https://docs.flip.to/integrations/websites/feature-previews), or [sign into your platform and try it for yourself](https://manage.flip.to/home).
{% endhint %}

## <mark style="color:purple;">Sharing the platform to your fellow team will soon be even easier</mark>

Driving impact is a team effort, so we know sharing the platform to peers is a must.

**That's why we're launching the ability to preview the platform, right on your site**—an incredibly easy way to work with your team to dial in and get launched even quicker. Stay tuned!

{% embed url="<https://customer-sr3qzvw7aivuwyt8.cloudflarestream.com/c5b4239dcc86a96ddd1cd4cd0e5c6045/watch>" %}


---

# 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.flip.to/changelog/sneak-peek-feature-previews.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.