Launched: Sync page access control (view-only)

There is somewhere a presentation sheet where you can see that this update is planned for july - so within the next 1.5 months I guess.

2 Likes

Where can I find that presentation?

I can’t find it again unfortunately. I was looking for it as now 1.5 months passed. Does anyone have any update on it? It’s now 14 months ago since they launched the last sharing update. Also, not a single update in july. :frowning:

You can find it in here: Personally I think Coda is in some deep :poop: with it’s architecture so they are confronting big issues that take a lot of time to go around.

4 Likes

All previous roadmap items from before the merger with Grammarly seem to in limbo. They might see the light of day but are certainly getting re-prioritized. This is my impression after chatting with support yesterday.

1 Like

Hi there,
I was wondering if there are any updates regarding the ability to edit synced pages. It’s been over a year since this was first discussed, and for many of us, it’s become a critical missing piece.

Could you please share a realistic ETA for this much-requested feature?

To be frank, in its current form, the Page Sync functionality offers very limited value. Without the ability for users—who don’t have access to the source doc—to contribute or edit, the feature feels more like a read-only Cross Doc, which was already possible before.

This limitation defeats the purpose of what could be a powerful tool for data compartmentalization and access control. If we’re forced to grant access to the original Synced Doc just to enable interaction, we lose the very separation we’re trying to create.

I say this with the utmost respect, but it’s frustrating to see ongoing emphasis on visual/UI updates while such a strategic, community-requested improvement remains unaddressed for so long. It’s becoming harder to justify continued investment in a platform that seems to prioritize surface over substance.

Thanks for listening—and really hoping to hear some concrete news soon.

13 Likes

:waving_hand:t5: folks,

Many thanks for sticking with us—we know how frustrating the wait has been.

We’re actively investing in this area and your feedback continues to shape our approach, so please keep it coming.

We’ll share updates as soon as we have something concrete, cheers.

4 Likes

@Ayuba_Audu hi!

What specifically can the community do to help? It seems everyone is aligned and no doubt you are a hard at work. The thing that seems hard to reconcile is the amount of time that has passed since step 3 was released. Given you also made it clear that this is a priority all the way up to Shishir, what else can we do to help?

Offering some example questions below to connect the dots between all the discussions above;

Is it possible to share an updated timeline? Do you need any community input for decisions? Is there a way to break down the roadmap for interim releases? Is there any testing that is needed from the community? Following @lane ‘s excellent commitment to communication post merger, would a live community discussion help?

Others in the community please add your own thoughts / questions to help…

5 Likes

Dear @Ayuba_Audu,

I was very happy to read the latest from Coda about Superhuman and all the developments incorporating the newest AI technologies. I truly believe this is the way.

mando-way-this-is-the-way

However, after reading the e-mail a painful realization came into my mind. Can it be that the page-level permission roadmap is not progressing for years now, because all the attention and effort goes to the merger and to uncover the potential of the AI?

How do you see it? Do we still have some hope that this road map will be finalized and we can get the page-level permission ready before Christmas?

Thank you very much for your answer in advance!

4 Likes

I ASSUME that it has got caught up in the idea of breaking Coda into a database layer, and a presentation layer…

1 Like

is this going to happen in 2025?

2 Likes