Whether you’re rooting for the Seahawks, Patriots, or you’re just looking forward to 7-layer dip and some Bad Bunny bangers, we have a Friday Features update that should hopefully please all.
First, we have another roundtable coming your way to show you all the ways that Coda MCP can help to optimize your ability to write smarter and faster. Space is limited, so please RSVP here to get a sneak peek at what we’re working on.
Second, we have a few updates to the tabbed views feature we recently rolled out:
Convert to tabbed views: One of the most requested features is an easier way to convert your existing views into tabs. Previously, you’d have to recreate everything from scratch. Now, you can simply drag and drop a view onto another view of the same table to convert it to tabs, making it much simpler to organize your existing content.
Show row counts on tabs: You can now display row counts directly on your tabs, giving you insight into each tab without having to switch between them. This is especially useful for task tracking—set up tabs like “my tasks” or “completed tasks” and enable row counts to see your progress at a glance. To turn this on, just right-click on any tab and select it from the menu.
Independent tab selection across browser windows: We’ve made a small but helpful change to how tabs work across multiple browser windows. Previously, your selected tab would sync across all windows, which meant you couldn’t view two different tabs side by side. Now each window maintains its own tab selection, so you can easily compare different views*.*
As always, we value your feedbackand hope you find these updates as exciting as we do.
I apologize for crashing the party, but I would really like to bring another most requested feature into your attention and tagging you at that topic did not work, so I thought I try in a more fresh one.
Page-level permissions road map was presented more than two years ago but unfortunately the last step has never been implemented.
Do you have any means to know what is the ETA of completing the page-level permission road map?
I think I speak for many when I say it would be very important to know if it is coming up or it has been buried and will never happen?
In order to give you all the context here is the link to the topic:
I appreciate your attention to this and I apologize again for bringing another topic here.
On my immediate roadmap is capturing any outstanding requests from the Coda community that haven’t been resolved or responded to yet. Since I’m still getting up to speed, I’d love your help surfacing insights I might have missed. More to come in a separate post soon!
Also, we just launched this doc to help keep track of feature requests so they live within a single source of truth. Any chance you’re open to dropping into the doc so we can more easily track and surfact to the right people internally?
It has been again more than a month passed and there is no information about the page-level permission roadmap. I am wondering what can be the reason of not getting any information from the Coda Team?
Are they too busy with adding more and more AI capabilities? Are they avoiding to answer that they will not complete the road map? Are they facing technical issues with completing it? Maybe the finish is just so close they want to just come with the new feature in a couple of days instead of answering? OR
Can it be that AI already took over the complete company and there are no human beings working in Coda anymore? So many assumptions and stories could come up without an answer…
I mean I don’t want to give the way out for them by suggesting answers, but it is very weird that after a lot of promotion and progress on this road map suddenly they stop communicating about it, seemingly waiting for us to forget, instead of just saying where they are.
Any hope you can actually get an answer to this?
Thanks a lot!
Ha, none of those AI-takeover scenarios, I promise. There are very much humans here, slightly sleep-deprived ones, racing toward a moment that has required pretty much an all-hands-on-deck focus, but humans doing human things nonetheless >
Page-level permissions has not been shelved or quietly abandoned. The silence has been a comms gap on our end during a crunch period, and I own that. What I’d push back on gently is the idea that we’ve been hoping it fades from memory: the energy we’ve put into getting community members involved in testing new features is a direct reflection of how much we need your input to get this right.
I’m going to DM you because I’d genuinely love to pull back the curtain a bit. There’s some stuff in progress I think you’d find interesting, and your perspective on it would be really valuable to us.
@Ruggy-Joesten No, no DM’s, I think that the community wants… public answers. Coda has promised many times (almost every time funding was raised) that the team is “working hard” on page-level permissions. As a paying customer of the Superhuman suite and as someone who guided others to switch to the suite rather than just simple doc makers… I am deeply disappointed in how the team is communicating and in the abysmal progress.
The team is failing to ship changes that affect how we, the users, work…
@Cristian_Nichifor totally fair, and I want to be clear: the DM wasn’t an attempt to take things private or avoid anything I wouldn’t say right here. Everything in my post I meant publicly, and it stands on its own. We understand the frustration; we own the communication gap, and there is something significant on the horizon that has had a real impact on the team’s focus.
The reason I reached out to Tamas directly is that the beta access we’ve been extending is, by nature, more of a 1:1 conversation. Use cases vary enough from person to person that a blanket open invite doesn’t really work, so we approach it individually. That’s the spirit behind it, nothing more.
Your frustration is heard, and so is the broader point: this community deserves public answers. So I’ll say it plainly: page-level permissions have not been forgotten, and the people who’ve been vocal about it, you included, have been heard.
I’m happy to extend the same invite your way if you’re ever curious about what’s in progress. Absolutely no pressure, though.
Since most of the page-level permissions conversation has lived in this thread, I wanted to flag that @Jason-Tamulonis from our engineering team just shared some thoughts in a dedicated topic here. Head over there to keep the conversation going. It’s the best place to consolidate feedback and make sure it’s in front of the right people.
> 
