> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/groups-users-and-permissions/users/modifying-user-details.md).
# 修改用户详细信息
用户设置
* **以管理员身份登录：** 使用管理员权限登录。
* **访问用户管理：** 导航至用户设置，在此可以编辑现有用户。
* **选择用户：** 找到并选择要修改详细信息的用户。可以点击用户名或用户旁边的编辑按钮。
* **编辑用户详细信息：** 系统会显示一个表单，其中包含用户当前的详细信息。根据需要进行修改。通常需要编辑的详细信息包括：
* 名字和姓氏
* 电子邮件地址
* 用户角色或权限级别
* **保存更改：** 检查所做的更改，然后点击 Save 保存新的用户详细信息。
* **检查角色变更的影响：** 如果更改了用户角色，请检查此变更对安全访问级别的影响。确保角色变更后，用户仍拥有继续履行职责所需的权限。
* **发送通知（可选）：** 可以向用户发送通知，告知其所做的更改。
完成这些步骤后，用户详细信息即已成功更新，用户将获得根据所做更改更新后的信息和权限。
## 移除用户：
* **选择用户：** 找到并选择要移除其访问权限的用户。可以点击用户名或用户旁边的编辑按钮。
* **移除访问权限：** 点击 "delete" 移除该用户。
* **确认：** 系统会要求你确认移除该用户。
* **可选通知：** 可以向用户发送通知，告知其访问权限已被移除。
* **检查任务和文档：** 移除用户之前，请检查分配给该用户的任务或文档。将这些任务或文档的责任转交给其他用户，确保没有任何内容丢失或未完成。
* **保存更改：** 确认移除该用户并保存更改。
按照这些步骤操作，可以安全地移除用户的访问权限，同时妥善管理所有相关任务和文档。
---
# 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://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/groups-users-and-permissions/users/modifying-user-details.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.
