How to have only the current user's privatized information within a doc

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)

1 Like

@Paul_Danyliuk could your cross doc plus handle this?

1 Like

Um, well, it’s not as simple as just “let’s sprinkle a pack on it”.

The use case implies that each user has a private space to enter their information. This means each user will need a separate doc created just for them. Besides, since we also need to limit what rows get exposed to that user, this is also only achievable if the user gets their own doc where only permitted rows are synced.

Assuming you’re okay with duplicating some template doc for each user (you can automate the process through Coda API / Admin Pack), indeed my Cross-doc Plus pack should make it easier to programmatically share selected rows with selected user docs through a password system basically. Each doc would have a unique password and each row on your backend tables would have the rule allowing access to docs with this or that password.


@Paul_Danyliuk Thanks! I think that gives me a possible way to do what I am thinking. I got to watch your Cross-Doc Plus pack video, and I think that would solve the problem when combined with copied templates. Using copied templates would not be the most ideal solution, but definitely a solution. Do you know when the pack program is being fully launched and cross-doc plus will be available?

1 Like

Sometime in a few weeks, they say

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.