@Fimbi_SJ,
Many thanks for your note—we couldn’t agree more on the importance of the scenarios you shared!
As I shared in my original post, this is a stop along the way and we’re committed to making things editable. Instead of waiting until we support every scenario, we continue to release updates periodically that unblock a range of use cases.
Once we enable editing, this will unlock the scenario you’re describing where you can sync a specific page and allow a smaller set of people make changes to only that page—and prevent them from seeing or accessing anything else from the source doc.
We’ll continue to share updates as we have them, so you can look forward to many more improvements to come, thank you!
@AJM,
Many thanks for continuing to engaging with us!
The general principle is if a link or modal etc. points to something that’s synced, we navigate or open in the same tab i.e., it should behave like any other Coda page in the same doc. If the link points to something that’s not synced, we’ll open in a new tab.
In the question I was responding to, the OpenRow()formula was pointing to a hidden page which isn’t synced over. Following our principle, we’ll open in a new tab, since the content isn’t synced over and you don’t have access to the page.
All that to say, we’re generally aligned with your feedback about not transporting someone elsewhere—as long as the content synced into the container doc.
If there’s a sample doc you’re looking at, I’m happy to take a look, so please feel free to email me aaudu@coda.io with a loom, docs or anything that would be helpful, thank you!
1 Like
Still confused what the reasoning behind the building of sync pages is but I am pretty sure that the community was mostly anticipating the sync pages so that
a) we can hide the hidden pages
b) sync only part of the document but they function exactly as they are in the original doc.
So if you don’t fix this openrow() issue, maybe you shouldn’t bother much about the Edit of sync pages.
Seems like table view and how they function are the main problem so that could be a problem to tackle first.
1 Like
As part of a consulting project I have written the specs of a new software solution, and want now to engage with potential tech partners able to contribute to his development, so to discuss the specs, tweak them, get a budget and select the partner.
The specs are in a Coda doc page (I’m working with my customer using Coda to coordinate), in a single table, validated from my customer.
So the ideal will be:
- create a new doc
- create a new page with a copy of previous specs
- tweak them (will add some more info, and remove some unnecessary elements)
- create multiple copies of the final version in new pages
- share a single page with a single perspective partner
- allow every perspective partner to see and edit only his page
- discuss with them having their own specific page to change and update
This way I will have a single doc with multiple pages, and every page will be a point of contact with a different perspective partner.
I understand in current settings this is not possible if not creating multiple docs, one for every perspective partner. Wanted to ask if with step 4 this will be possible.
2 Likes
It’s pretty safe to say that 100% of us are interested in this.
If that becomes a reality with step 4 we can all have an Ibiza party to celebrate to it 
2 Likes
Phase 4 will fully implement sync pages, meaning that it is possible to sync a page and subpages to a separate document, and then sharing that document with other individuals. They will then be able to edit that page, which will update to the source doc. They will not need to have access to the source doc .
1 Like