Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[TBD] Transfer Organization Admin Account Ownership to a New Email Address

未关闭
  • 哪里不对？
#606 0 条评论 0 个 reaction 已指派 3 人 在 GitHub 查看

@dragos1195 已经在做这个了。

开始于 2024年8月21日。

评估

这个 Issue 还没有评估数据。

描述

enhancement :rocket:

We have two possible solutions. Each one offers different benefits and challenges. Here’s a summary of each solution:

Solution A

Description
1) Admin Account

In the My Account page, a new section titled "Transfer Ownership" will be added. This section will allow users to transfer ownership of their account to another existing account within the organization.

The section will include:

  • a title labeled "Transfer Ownership."
  • an informational text that reads: "Please note that your account will be disabled, and ownership of the app will be transferred. If you proceed, you will no longer have access to your account."
  • a "Transfer Ownership" button to initiate the process.

When the "Transfer Ownership" button is clicked, the user will be redirected to a dedicated "Transfer Ownership" page. On this page, the user will select an existing user account (an Employee account) from within the organization and confirm the transfer.

Once the transfer is confirmed, the admin account will be automatically disabled.

2) Super-Admin Account (If the ownership transfer feature isn't needed for Super-Admin, this step can be skipped)

In the 'ONG-uri' page, a new option will be added to the kebab menu called "Transfer Ownership." When clicked, the Super-Admin will be redirected to the "Transfer Ownership" page for that specific organization.

From this page, the flow mirrors the process for the admin: the Super-Admin selects an existing user account within the organization and confirms the transfer.

Once the transfer is confirmed, the Super-Admin's account will be automatically disabled.

Advantages
  • provides a straightforward process for transferring ownership with clear steps and confirmation.
  • ensures that ownership is only transferred to another existing user, which helps in maintaining security within the organization.
  • adding a new section and a new option in the kebab menu is relatively simple to implement and integrate into existing workflows.
  • ensures that the previous owner no longer has access.
Disadvantages
  • admins lose their access immediately after the transfer, which might be disruptive if not managed properly.

Solution B

On the 'Add User' page, a new input field (list or checkboxes) will be introduced, allowing users to select the user role as needed.

In this variant, an existing NGO Admin will have the ability to create another NGO Admin. The newly created one will then have the capability to restrict the access of the original NGO Admin.

This approach allows multiple admins within the same NGO and addresses the issue of ownership transfer by providing a mechanism for role management and access control.

Advantages
  • allows for multiple admins within the same NGO, offering more flexibility in managing roles and responsibilities.
  • the original admin retains control over the organization while having the capability to create and manage other admins.
Disadvantages
  • the ability for one admin to restrict another admin’s access might lead to misuse or power struggles within the organization.
  • it requires UI adjustments to the users table and possible involve functional changes on filtering/sorting.
主要语言
TypeScript
星标
6
派生
5
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

code4romania/onghub 的其他 Issue

查看 code4romania/onghub 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。