So I’m currently trying to create a prototype of a website for a startup idea that can help organize the pros and cons of different arguments. The prototype will be published and the goal is to have a lot of people able to interact with the site and explore it at one time. This means that all views will need to be filtered by user. I already know how to do this. However, I would also like the ability for users to have private information (e.g. private account settings, private emails, private profiles, privately made pros and cons, etc.). Because of the nature of the @mention functionality, anyone can access any row on the site at any time. Thus I need to have it that the only rows on the site are the ones that the user is allowed to access. This information needs to be unique to multiple users using the site at once. Is there a way to do this?
I’m thinking there may be some way to use cross doc, but I am having trouble figuring out how. At the moment you can only filter for the current user from front-end doc. This means that all the rows for all users have to be available in the front end, which means that anyone can access the rows not owned by them. Thus I’m trying to figure out if there is a way to filter the back-end table by the current user for the front-end. Any thoughts?
I’m open to any solution at the moment including the use of special packs, or even ideas for making my own pack (I’ve recently become a part of the beta program and hope to be exploring the ins and outs of how to create packs soon)