- Manage databases on a system-wide level instead of tying them to individual accounts. This would ensure that databases remain accessible to other accounts even if the originating account is deleted.
Karol
Summary: the idea here is to have a single database for all integrated accounts.
Problem Description:
- Database Creation:
I log in with Account A and create a database for digital products. This database includes specific codes linked to dynamic fields.
- Usage by Another Account:
I log in with another account (e.g., Account B) and use the same dynamic field, which references the database created by Account A. Everything works as expected at this stage.
- Deletion of Account A:
If Account A is deleted, the database originally created under this account is also deleted. As a result, the codes that dynamic fields depend on are lost.
- Issue:
While the dynamic field remains, it loses the essential data (codes) from the deleted database, rendering it non-functional. This creates inconsistencies in the system, as the dynamic field technically exists but no longer works as intended.
Potential Consequences for Users:
- Users of other accounts (e.g., Account B) may unexpectedly lose access to the database and its associated functionality which creates CHAOS.
- This can cause confusion, complaints, and potential data loss, especially if users are unaware that the database was tied to a now-deleted account.