在我的应用中，这是我的管理方式:

Here's how I manage this in my apps:

1. 我的用户具有管理员"，经理"等权限.

1. My users have permissions such as "admin", "manager", etc.

管理员"登录到应用程序后，他们可以通过应用程序界面添加，更新和删除其他用户

When an "admin" is logged in to the app, they can add, update, delete other users via the app's interface

这是通过将更改请求推送到实时数据库中的"updateUser"节点-否到数据库中的实际用户记录来完成的.确保Firebase规则仅允许管理员"用户写入此节点.

This is accomplished by pushing a change request to an "updateUser" node in the realtime database - NOT to the actual user record in the database. Be sure that Firebase rules only allow "admin" users to write to this node.

一旦创建了这个新节点，我将禁用表单并提交按钮，因此无法进行其他更改.然后，我让应用程序监听对以下内容的任何更改:

Once this new node is created, I disable the form and submit buttons so no more changes can be made. Then, I have the app listen for any changes to:

• 这个新创建的"updateUser"节点(类似于:updateUser/xkekek393kdkd)
• 实际的用户个人资料记录

我具有Firebase云功能，可监听对该"updateUser"节点的任何写入

I have a Firebase cloud function listening for any writes to that "updateUser" node

该函数触发时，它将使用admin-sdk对用户配置文件 AND 的Firebase身份验证帐户(电子邮件地址，密码等)进行实际更改.然后，admin-sdk使用以下状态更新"updateUser"节点:

When the function triggers, it uses the admin-sdk to perform the actual changes to the user profile AND their Firebase authentication account (email address, password, etc). Then, the admin-sdk, updates the "updateUser" node with a status like:

{
  status: "success",
  message: "User updated"
}

或

{
  status: "fail",
  message: "Email address already in use"
}