Hello,

To begin, I want to extend my heartfelt apologies for the delayed reply, 

which is due to an unexpectedly high volume of inquiries. 

We truly value your patience during this period.

-

I am sorry, but i did not fully understand all the details/points of your Use-Case.

It seems it might be a simple use-case or perhaps having one "main Table" which holds all the data that only the Admin can see, and then for the Front-End users, you can add an SQL Query Table which will pull from the main Table, but you can limit what each User can see - such as if you need each User to only see the Rows they added, not see other people's rows, etc;

but i am not sure what you mean exactly when you say it should be 'interactive databases'.

Can you please elaborate in more details on that aspect of the Use-Case, if you can provide me with an example, what should a User see when they visit their Table, what functionalities should happen, should they simply just edit their own rows ( while just seeing the rows they added), or is there some more advanced functionality needed?

You can start by checking out our Editable Tables here.

Then, if you need to make Foreign Key Relations between multiple Database Tables, you can check this Feature.

And here you can see our Feature to limit the Rows, so that each User can only see and edit their own rows ( which they added).

Let me know how that seems to start with, and then if you can elaborate more about the Use-case, if you can add any screenshots as examples or a Video?

If you show any sensitive Data, just make sure to mark the reply as PRIVATE for security reasons;

or if a Video gets too large, you can upload it to weTransfer and send a download link.

Thank you.