We're listening: what we're up to at Coda

[Konrad_Mertner]

HOW DID NO ONE NOTICE IT’S FINALLY RELEASED SINCE TWO (?) DAYS?!

Thank you so so so so much on behalf of all the folks using comma as a decimal seperator!
Thank you 1.000.000,000 times! Or 1,000,000.000 times,… whatever floats your boat.
Wait.. whatever floats your float

How come there’s no official release post?

[Doug_Loud]

In the latest Dune version on MAX (Dune: Prophecy), they begin with a recap of how the Humans fought and won a war with the “Intelligent Machines”!!

[Agile_Dynamics]

the ‘Butlerean Jihad’ probably named after the Victorian philospher Samual Butler (1835-1902) who wrote about the rise of automatatio and machines to surpass humans as the smartest creatures on the planet.

[Doug_Loud]

Indeed and worth remembering!

[Dima_Petrov1]

Will this only work for new documents?

[Konrad_Mertner]

It looks like that… At least I couldn’t find a way to make it work in existing docs.

[Dima_Petrov1]

I really hope the team implements this in the settings of existing documents as well, as happened with the date format. This is a very necessary option and I would like to enable it on existing documents with a large amount of data

[Eva_Folch]

What??? Where did you find this setting? I want this! I need this!

[Ayuba_Audu]

@Konrad_Mertner—great eye and to see the excitement from everyone!

As @Jason_Tamulonis shared here we’re working on making it happen. We unintentionally made it live—our mistake, and have since turned it off so the team focus making sure everything is ready.

Once we have an update to share, there will be an announcement so stay tuned and thanks again for all the interest!

[Eva_Folch]

can’t wait! Thank you

[Astha_Parmar]

Huge plus one to a ‘published experience’ for the user but with log-in/sharing controls and separating databases out from views. It’s about creating a streamlined user experience without introducing complexity.

As context, the ‘table locking’ feature is not helpful in my user case – column locking, on the other hand, would be useful.

Permission clarity
I work in Coda almost every day, and I would be hard pressed to explain to someone what a commenter can do, what an editor can do, etc. These permissions are extracted from document editing and are a poor fit for an app-builder platform like Coda. In my case, I have users who need to:

• Interact with filters, view, and comment
• Everyday users who need to be able to add/edit data living in very specific columns and add rows/delete rows they added.
• Process and data owners who need to be able to edit table values and push buttons to take action, and then
• Doc/table makers.

Which leads us to
Column-level locking

• Use some columns to provide context, aka, non-editable columns (without the added complexity of creating shadow columns that are formulas).
• Have some columns that the user can edit and maintain.
  Example use case: Employee salary data where the user can ‘see’ the current salary and not edit it, but add the forecasted increase.

Row-level protection that becomes relevant in parent row scenarios

• Some way to make ‘delete rows’ a more intentional action. We had an OKR doc where people accidentally deleted org-level KR’s or deleted linkages with org-level KR’s.

Automation level simplification

• I find myself creating a lot of automations that push a row-level button when a row is added or a certain column is edited. And I wish I could see these in the button options themselves. That way, when I go back to a doc 6 months later, I am not digging around for 5 minutes to remind myself which buttons are tied to which automations…even with descriptions and documentation.

View level (tied to row permissions)

• This probably comes with the page-level permission sharing…but the ability to share a single page. Even more powerful – construct the url structure of a view with filtered rows that can then be sent to someone as part of their workflow to provide insights, take action, validate data etc.

Treating views as objects that can be replicated
It would save me so much work if views traveled with a table. So I could pull a table into another doc and say display it as this view. Now, it is possible that with the upcoming changes, the need for cross-doc itself diminishes.

And a huge shout out to the comment from @Ayuba_Audu about performance changes that would increase the 10,000 row pack limit. Super excited about that!

[Pawel_Polanski]

+1 to everything already mentioned. Just wanted to add another scenario:

Use case: I need to share a view with an external company or subcontractor so they can fill in only the specific fields I ask for — and nothing else. They do need to see some of the existing data to work with, so simple forms won’t cut it. And since this involves sensitive info, data security is key.

What I’d need is a user type that:

• can edit selected fields, comment, and view some content
• but has no API access (right now all editors do — which breaks a lot of potential workflows)
• doesn’t see Doc Map, Statistics, or other meta stuff

The API part is a big one — if every editor has full access via API, it’s really hard to safely collaborate with external teams.

[Mikhail_Mikhasev]

Oh gosh. And I was thinking of moving out of Notion due to its limitations. API access for editor by default? This is a ultra-black-security-hole for us.

[Harshita_Yerramreddy1]

Hi all! Just wanted to share that one of the features we shared in this post, Table Locking, is now live. Would love to hear any feedback

[Doug_Loud]

That would be a huge improvement and solve many problems for the legal and fnancial users.

[giuse.covino]

Thanks but we need a very simplified version (like just lock/unlock the DB structure or the whole page) for free (or pro) plan.. For users of Coda as a life/family organiser tool, to avoid unwanted changes the need to have a Team plan is too much .
Would it be possible? Notion has such a free generic lock/unlock feature.
Thanks

[Ayuba_Audu]

@Konrad_Mertner and everyone else who was following, number format options are now live—read more here!

[Jean_Marc_Dieu]

+1 !!! Been saying this for a while…

In 1985, Excel already supported 16,384 rows… In 1997 it supported 65,536 rows and in 2007, it went for 1,048,576 rows…
It is 2025 and Coda still supports 10k rows only… Probably enough for a shared to-do list, definitely not enough for Enterprise usage (we are forced to calculate summary statistics elsewhere before bringing it in to Coda, which increases complexity and limits use cases…)…

[Avalon_Cakes]

Currency symbol assigned at account or doc settings level?

[Attila_Szenes]

Hey Ayuba and the Mighty Coda Team!

Beside being very excited about the latest update on the look and feel, I am utterly curious about this new data layering and real filtering capabilites! How public are the states of this two gamechanger features?
I am (and probably many others) building an app/doc with some super sensitive data, that would be great to distribute in the very same doc between team members without worrying about data visibility or being overloaded by the many duplicated docs that serves not more but data filtering!

Thanks for any droplets of information here!

.sz