We have a company app that includes a database of Contacts. That data is essentially a Rolodex used by the staff. None of those Contact names will ever be a “User,” i.e. someone who will log into our app. But historically, as humans with names and email addresses, they have been entered as such.
Is there any advantage to taking those Contact User records and converting them to a simpler data table where that contact info is treated as data instead of as Users? It seems like it could potentially reduce our storage, and reduce the potential (albeit minimal) risk of unused User profiles.
It is easy enough to simply leave it as it is, but any thoughts on the subject are welcome. Thanks in advance.
If I understand your post correctly, you currently have user records within your accounts object, but access to your application for external logins is not permitted. You are considering whether it might be more advantageous to transfer these records to a standard table and whether any benefits might arise from such a change.
In my opinion, there may be minimal benefit to this transition, as you can maintain an unlimited number of account records. Even if you were to migrate them to a standard table object, the overall record count would remain the same.
By retaining the records in the accounts object, you are keeping future options available, allowing for potential access to a portal should your business needs evolve.
2 Likes