> 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/understanding-user-management-as-a-brand.md).

# 了解作为品牌的用户管理

本文介绍了作为品牌方有效创建和管理账户用户的流程。它涵盖了如何 *创建自定义角色*, *创建用户访问组*，以及 *邀请账户用户*。遵循推荐的设置流程很重要，以确保您避免需要回退步骤。

**步骤 1 - 创建自定义角色**

* *自定义角色* 使您能够根据账户管理需求定制权限。您将创建它们，以确保以后可以分配给 *用户访问组*。此步骤应首先完成。虽然我们提供 *预定义用户角色* 以方便使用，但我们也允许您创建 *自定义角色* 以获得更大的灵活性。
* 有关管理现有 *自定义角色*的详细信息，请参阅 [相关文章](/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/manage-custom-roles.md).

**步骤 2 - 创建用户访问组**

* 一旦 *自定义角色* 已创建，您就可以将其分配给 *用户访问组*. *用户访问组* 帮助您使用特定角色组织项目。请注意，每个产品只能应用一个角色。创建 *用户访问组* 旨在帮助您根据每个组分配的角色来管理权限。
* 有关管理现有 *用户访问组*的详细信息，请参阅 [相关文章](/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/manage-user-access-groups.md).

**步骤 3 - 邀请账户用户**

* 最后一步是邀请一个 *账户用户* 在创建 *自定义角色* 之后（如果您尚未选择 *预定义用户角色*）以及 *用户访问组*。创建后，在邀请新用户时，两者都可供添加。
* 有关管理现有 *账户用户*的详细信息，请参阅 [相关文章](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/invite-account-users).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/understanding-user-management-as-a-brand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.