Resetting FinRev Dashboard Data

FinRev customers may request to reset the data on the FinRev account dashboard after connecting to an incorrect wallet initially or large deposits/withdrawals historically.


Data can not be edited on FinRev dashboards, and the only solution is to delete the user from FinRev, and reimport their deal ID from Ontraport into FinRev. This would require the customer to reconnect their exchange to FinRev via API.


If a customer has requested to reset their dashboard, the following process needs to be followed:


  1. Confirm with the customer that they wish to delete and recreate their FinRev account, meaning they will lose all previous data and will be required to reconnect to their exchange.


  2. Provide the FinRev userID for the account to be deleted along with a request to remove the account to @Chris in Slack.


  3. Reimport the Ontraport Deal ID into the FinRev platform.


  4. Provide instructions and/or a call booking link to the customer to reconnect their FinRev account.


The following explains why this is the only approach that is viable for dashboard resets currently:


Why this is the only approach at least for now:


Data integrity:


There is a lot of data stored against each individual account this data is used in various admin dashboards to verify the functionality of the system etc. so partially removing data from an account would compromise the integrity of the accounts data and therefore the mechanisms we use to ensure the system is functional.

Data safety:


The way data is stored involves a lot of different levels of access and rights, with the idea being no one point of access could edit/delete all the data. To be able to delete all this data would either involve:

1. a very complex setup which needs to be designed and implemented or
2. compromising the safety of all users data by creating a single point of access to edit/delete all data

Why our current solution doesn't violate the 2 points above:


Deleting the user basically just severs its link to the data rather than deleting the data itself.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.