# Cross-doc to client docs - filtered views for view only non-users? **URL:** \ **Category:** Ask the Community\ **Created:** [December 10, 2022, 3:46am UTC](https://connect.superhuman.com/t/cross-doc-to-client-docs-filtered-views-for-view-only-non-users/35995 "2022-12-10T03:46:58Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Paul\_Danyliuk](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/paul_danyliuk/32/27228_2.png) [@Paul\_Danyliuk](https://connect.superhuman.com/u/Paul_Danyliuk)\ **Post date:** [December 11, 2022, 1:39pm UTC](https://connect.superhuman.com/t/cross-doc-to-client-docs-filtered-views-for-view-only-non-users/35995/3 "2022-12-11T13:39:17Z")
> [@Alan\_Patrick\_Kenny](#): > > I appreciate the Sync Tables Pro functionality but am not in love with the required table name nomenclature and so much complexity in the execution. Sorry to hear that but you cannot do it otherwise. The name nomenclature is largely for your own good (and there’s not much to it — like, make one view and call it OUT? or make a `__read` column for rules?) and there shouldn’t be any complexity really to do what you need — just give each student a token and set it up in each of the individual docs. It may just seem like it because I never found time to make simple documentation for it. With webhooks there would be much more complexity, to be honest. Happy to assist you with setting it up if you’re interested — DM me or write at [paul@codatricks.com](mailto:paul@codatricks.com) If you absolutely don’t want my pack, here’s the least painful way to do it with Cross-doc > [@\[Video\] Swap a cross-doc table in a doc (e.g. duplicate a doc and share with a different client)](https://connect.superhuman.com/t/video-swap-a-cross-doc-table-in-a-doc-e-g-duplicate-a-doc-and-share-with-a-different-client/15628): > > Here’s a new spontaneous tutorial that I just recorded slight_smile As a Coda expert for hire, I need to track my work for different clients. Obviously I do it in Coda, and I want to do it in a single doc so that I can see all the summary in one place. Today I was rebuilding it and thought it would be nice to make a template that I could copy and share privately with each of my ongoing clients, populated separately with only the data each of them can see. Previously I [showed](https://connect.superhuman.com/t/video-sync-data-changes-from-one-doc-to-multiple-docs-e-g-admin-individual-users-docs/10096) how to build thi… — but yes, you’ll still need 150 individual views for each student’s export. You can generate those with DuplicatePage now. The downside is that now that you’ll have 150 views, that’s gonna be 150x the recalculation time on filters on any row addition/removal/change. Then there’s always external solutions like app scripts, Integromat, [Zapier](https://connect.superhuman.com/t/video-sync-data-changes-from-one-doc-to-multiple-docs-e-g-admin-individual-users-docs/10096) to read rows from the main doc and push them into individual docs. But at that point it would be more viable to just do webhooks. --- _[View the full topic](https://connect.superhuman.com/t/cross-doc-to-client-docs-filtered-views-for-view-only-non-users/35995)._