> 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/wu-dai-ma-ti-yan/chat-experiences/prerequisites.md).

# 使用聊天体验前需要了解的内容

了解构建聊天体验前 Convai 账户需要具备什么、可以向房间添加哪些角色，以及控件缺失时该怎么做。

创建和运行聊天体验需要一个 Convai 账户、至少一个角色，以及“聊天体验”控件位于 **我的体验**.

### 账户要求

| 要求        | 详细                                                             |
| --------- | -------------------------------------------------------------- |
| Convai 账号 | 登录于 <code class="expression">space.vars.dashboard\_url</code>. |
| 仪表板访问权限   | **我的体验** 位于左侧边栏中。聊天体验会在该页面创建和重新打开，没有其他入口。                      |
| 至少一个角色    | 你的某个角色，或某人通过 ID 与你分享的角色之一。在向房间发送消息之前，房间至少需要一个角色。               |

### 你可以添加到房间中的角色

房间是在你开始聊天体验时打开的文本对话。你可以在其中添加角色，在 **向房间添加角色** 对话框中。它有两个选项卡，每个选项卡列出不同的一组角色：

| 选项卡         | 列出的内容                                                      |
| ----------- | ---------------------------------------------------------- |
| **来自我的工作区** | 你正在使用的工作区中的角色，按最近编辑优先排序。网格显示最近的八个，并且 **显示全部** 将其展开为完整列表。   |
| **按角色 ID**  | 按 ID 查找的角色。每行输入一个 ID，可一次查找多个。若要查找某人从你的工作区外分享给你的角色，请使用此选项卡。 |

角色会带着自身的人设加入，并在此基础上接收体验简报。该简报来自房间类型以及你在创建体验时选择的用途。

### “创建聊天体验”按钮缺失时

如果 **我的体验** 不显示 **创建聊天体验** 也不显示 **聊天体验** 部分，请联系 <support@convai.com>.

### 下一步

满足要求后，打开创建聊天体验的中心。

{% content-ref url="/pages/c55d8326fdc43837c6474f97a49ebbb4abad844b" %}
[打开我的体验](/api-docs/zh/wu-dai-ma-ti-yan/chat-experiences/open-my-experiences.md)
{% endcontent-ref %}


---

# 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/wu-dai-ma-ti-yan/chat-experiences/prerequisites.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.