Skip to content

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

@andrei-manda

Description

@andrei-manda

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.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions