> 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-user-access-groups.md).
# 管理用户访问组
在……上 *用户访问组* 在此屏幕上，您可以编辑该项的设置 [访问组](/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/create-a-user-access-group.md) 您已经创建的。在此，您可以查看已归档的访问组，或将某个特定访问组设为新用户的默认组。
{% hint style="warning" %}
**警告：** 在邀请新的账户用户之前，请确保分配给他们的访问组拥有必要的权限。权限通过 *用户角色*，然后应用到该访问组。有关完整流程概览，请参阅 [作为品牌了解用户管理](/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/understanding-user-management-as-a-brand.md).
{% endhint %}
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在左侧，在 *常规* 部分下，选择 **用户访问组**.
3. 使用  **\[搜索栏]** 以搜索特定的用户访问组，或使用 **状态** 筛选器来搜索 **全部** 用户访问组， **有效** 用户访问组，或 **已归档** 用户访问组。
4. 选择  **\[列]** 如果您想添加其他列。请参阅 *列参考* 以获取更多信息。
列参考
| 列 | 说明 |
| ------ | ---------------- |
| 组名称 | 用户访问组的名称。 |
| 已分配用户 | 分配到该访问组的用户数量。 |
| 创建者 | 创建该访问组的用户。 |
| 创建日期 | 创建用户访问组的日期。 |
| 最后更新者 | 上次对用户访问组进行调整的用户。 |
| 最后更新日期 | 用户访问组上次更新时间。 |
| 状态 | 用户访问组的当前状态。 |
5. 将光标悬停在您要管理的用户访问组上，并选择  **\[更多]** 以执行以下操作之一：
* **编辑**：对用户访问组进行调整，然后选择 **保存** 以确认更改。
* **归档**：要归档用户访问组，请选择 **归档** 以确认该操作。
* **设为默认**：在邀请新用户时，将此组设为您的默认用户访问组。
---
# 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-user-access-groups.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.