Couchdb / Pouchdb circuit design

Question

I have an application that manages prospects. These prospects are assigned to some employees. They have a tablet that they use to contact our customers. The mobile application has offline support and synchronization with the desktop application. I have some users who manage these employees, and they need to have access to all potential visitors from their co-authors.

Our current design is a cordova app with angular and pouchdb that syncs with couchdb. The desktop application is an application for laravel. We create a new couchdb database for each employee who synchronizes with their account in the mobile application. Administrators and supervisors need to access, list and edit all the perspectives of all couchdb databases. Thus, we synchronize the nodejs process, all perspectives on the couchdb database in the mysql perspective table, so we can easily list all the perspectives.

My question is, does this design make sense or should we go a different way.

There is a similar question and design here

Answer 1

To increase security and reduce design problems with multiple databases for synchronization, I use AES encrypted data in documents. For me, this is the best solution. Everyone can read, but the data is protected.