> 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>

***

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

此 **详细信息** 选项卡包含发布体验所需的所有重要设置：

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

***

## 嵌入体验

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

{% hint style="danger" %}
目前，只有 Professional 及更高级别的套餐才能使用 Convai Pixel Streaming 嵌入功能。
{% 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.
