> 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 - 创建自定义角色**

* *自定义角色* 可让你根据账户管理需求自定义权限。创建自定义角色后，便可将其分配给 *用户访问组*。应首先完成此步骤。我们提供了 *预定义用户角色* 以供便捷使用，同时也允许你创建 *自定义角色* ，以获得更大的灵活性。
* 有关管理现有 *自定义角色*的详情，请参阅 [相关文章](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/manage-custom-roles.md).

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

* 创建 *自定义角色* 后，你可以将其分配给 *用户访问组*. *用户访问组* 有助于整理具有特定角色的项目。请注意，每个产品只能应用一个角色。创建 *用户访问组* 旨在帮助你根据各组分配的角色管理权限。
* 有关管理现有 *用户访问组*的详情，请参阅 [相关文章](https://help.impact.com/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/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.
