> 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/account-settings/invite-and-manage-users/manage-2fa-for-brand-accounts.md).
# 管理品牌账户的 2FA
[账户管理员](/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/understanding-user-management-as-a-brand.md) 可以要求所有 impact.com 品牌账户成员在从新设备登录时使用双因素认证（2FA）。对 2FA 有疑问？请查看我们关于 [双因素认证常见问题解答](/other/zh/reference-documentation/two-factor-authentication-faqs.md).
当您受邀加入账户且注册方式需要使用用户名和密码时，您将自动注册 2FA，且默认身份验证方式将设置为电子邮件。
启用 2FA 后，用户体验如下：
* 账户成员首次登录时，将通过短信、电子邮件或身份验证应用在其移动设备上收到验证码。
* 账户成员成功通过身份验证后，其设备将自动保存为受信任设备——这意味着他们在后续登录时无需再使用 2FA。只有当设备发生变更或检测到异常活动时，才会再次要求账户成员使用 2FA。
* 账户成员可以在 impact.com 用户资料页面管理已保存的设备。
#### 启用登录 2FA
这将为登录您品牌账户的所有账户成员启用强制双因素认证。
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在左侧栏中，位于 *常规*，选择 **账户用户身份验证**.
3. 在……上 *账户用户身份验证* 页面  **\[开启] 用户登录**.
4. 选择 **保存**.
* 在 **账户用户** 页面上查看已启用 2FA 的用户，其状态会在 *双因素认证* 列。
#### 为 PFT 启用 2FA
这将为尝试进行 [合作伙伴资金转账](/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/partner-funds-transfer/transfer-funds-to-a-partner.md) 且高于转账最低金额的账户用户启用强制 2FA 检查——一旦通过身份验证，PFT 将会完成。
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在左侧栏中，位于 *常规*，选择 **账户用户身份验证**.
3. 在……上 *账户用户身份验证* 屏幕上，选择  **\[开启] 合作伙伴资金转账**.
4. 在……下 *转账最低金额*, **输入一个值** 作为触发 2FA 所需的最低金额。
5. 选择 **保存**.
#### 管理已保存的 2FA 设备
1. 从顶部导航栏中，选择  **\[用户资料] → 编辑资料**.
2. 前往 *安全* 部分。
3. 在……下 *设备和活动*，其中列出了该账户已保存的设备，以及该设备上次登录的日期和时间。
4. 选择 **移除此设备** 如果您不再在该设备上访问 impact.com。
---
# 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/account-settings/invite-and-manage-users/manage-2fa-for-brand-accounts.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.
