Is it true that if you share a page, you’re sharing your ENITRE doc? Is there any way to only share one page without them being able to everything else you’ve got in there?
Hey Kelly - thanks for posting! Unfortunately, there isn’t currently a way to share just a single page of a doc. This is definitely a commonly requested feature, so I’d be happy to add a “vote” to this on your behalf
Some possible alternatives in the meantime…
- You can use locking to limit what viewer can see/do on each page, but this won’t entirely block them from viewing the page
- If you don’t need pages securely blocked, you have the option to hide pages.
- Finally, some folks use cross-doc to sync certain tables out to new docs, then they grant access to just those new docs.
Sorry for any inconvenience - but thanks for sharing your idea
+1 to improve page sharing and cross doc access. Also moving pages to other docs is a real pain. In this regards, I would hope for a structure like in Notion. One workspace with pages which would equal One doc with pages in Coda.
@Lena_Webster - can you add a vote for this on my behalf as well please.
How exactly do i vote?
can you add a “vote” on this for me aswell?
Please add a +1 vote for me as well.
Another +1 from me, thanks!
Another +1 from me, i need this, thanks!
Transparently, sub-doc sharing is a very common request, and one we’ve discussed at length (we’ve even Hackathon-ed potential solutions to it). The biggest challenge with Coda is that docs can be very interactive, and so defining how a “subdoc share” should operate can be tricky.
Some questions we have to answer:
- What should happen to views of tables that are not included in the share, or formulas that refer to other parts of the document?
- And how should we handle security for users that are creative at seeing everything that comes across to their machine - should we not transmit unshared data?
As we looked at some comparable products to Coda, many of them took shortcuts on these expectations, which we weren’t very comfortable with.
This is why we’re tackling this request in a few stages.
First, we launched cross-doc (with cross-doc actions) as a way to handle this for table data. Then, we started with what might seem like an unrelated launch, but is quite foundational: progressive loading of docs. We launched this as a performance improvement, but it’s also a key building block that allows us to start separating docs into parts, and not send all of them to the client. More to come as we build on this concept.
While we continue to think through this challenge, we’d love to know more about your desired use cases—please sound off in the comments! Key questions we’d love your feedback on:
- What types of docs would you like to share subsets of, and how would you describe the shared subset?
- How interactive would you want it to be (e.g. is read-only ok? would you want it to update when other parts of the doc updated?)?
- And if you’ve already tried cross-doc, which cases did that solve vs. not?
We’ll keep you posted on our progress here, and hope you’re as excited as we are for some big upcoming changes to our editor and overall product performance that help us get further down the road on the request to enable sub-doc sharing.
I take notes with my docs, with each page being a page of notes. I’d love to be able to share read-only pages with my classmates to take a look at my notes.
Hi Nathan, thank you for the update!
Regarding the interactivity, it would be great to have the ability to edit the doc from either folder, and have updates post in real time. The goal is to allow cross functional teams to be able to work collaboratively on docs that would live on both respective folders.