> 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步 - 邀请账户用户**

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


---

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