> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/profile-and-branding/who-is-my-primary-marketplace-contact.md).
# 谁是我的主要 Marketplace 联系人？
在 impact.com 中，加入您账户的首位账户用户将被指定为主要市场联系人。该用户将被列为合作伙伴可就您的项目相关的任何问题联系的人，并且是会接收合作伙伴消息的用户。
#### 查找您的主要市场联系人
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在……中 *账户* 列，在……下方 *常规* 部分下，选择 **账户用户**.
3. 在 *已加入* 列，查看每位账户用户加入该账户的时间。
* 最先加入该账户的用户将成为该账户的主要市场联系人。
#### 更改您的主要市场联系人
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在 *项目* 部分中，选择 **Marketplace 资料**.
3. 滚动到 **联系人** 部分，然后从下拉框中选择您要列出联系信息的联系人。
* 在此选择的任何联系人都可就您的项目相关的任何问题进行联系，并且是会接收合作伙伴消息的用户。
4. 选择 **保存**.
---
# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/profile-and-branding/who-is-my-primary-marketplace-contact.md?ask=&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.
