> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/convai-playground/character-customization/publish.md).

# 发布

了解如何将你的 Convai 体验向公众、指定用户发布和共享，或嵌入到你自己的网站中。

## 简介

该 **发布** 此页面允许您将已完整创建并自定义的 Convai 体验分享给全世界，或分享给选定的一组人。从这里，您可以配置体验的标题、描述、缩略图和可见性设置，以及生成分享链接。

<figure><img src="https://2402152281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEtUJA212Zc1S9ACc8T4l%2Fuploads%2FUSCY5YBYT3dhfZbByU0A%2Fimage.png?alt=media&amp;token=c447acf8-d634-4835-a1c0-9a2f9a692307" alt=""><figcaption></figcaption></figure>

***

## 发布选项和可见性设置

该 **Details** 选项卡包含发布您的体验所需的所有基本设置：

* **体验链接** – 您体验的直接链接，便于分享。
* **体验名称** – 已发布体验的显示名称。
* **体验描述** – 描述您体验的简短摘要。
* **缩略图** – 默认情况下，这会使用所选环境的图片，但您可以上传自定义缩略图。
* **可见性设置** – 控制哪些人可以查看并与您的体验互动：
  * **公开** – 任何人都可以在 `x.convai.com`.
  * **不公开列出** – 只有拥有直接链接的用户才能访问该体验。
  * **私密** – 该体验仅限受邀用户访问。
    * 当设置为 **私密**， **私密分享** 按钮将变为可用。您可以：
      * 输入您想邀请的人的电子邮件地址。
      * 或者，将体验链接分享给受邀用户以授予访问权限。

***

## 嵌入体验

“嵌入体验”选项卡允许您将 Convai 体验直接嵌入到您自己的网站中。此功能可轻松将交互式体验集成到自定义平台或应用程序中。

{% hint style="danger" %}
Convai 像素流式嵌入目前仅对专业版及以上方案开放。
{% endhint %}

***

## 结论

发布页面提供您所需的所有工具，用于控制您的体验如何被分享：无论您希望它向公众开放、仅向特定个人开放，还是直接嵌入到您的网站中。通过选择合适的可见性设置，您可以确保您的体验以正确的方式触达合适的受众。


---

# 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.convai.com/api-docs/zh/convai-playground/character-customization/publish.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.
