Launched: Coda 4.0!

Your understanding is correct. You will now need to shell out for all 40 editors.

well, there goes my ability to use coda and 3 months of work down the drain

1 Like

@Ariella_Messing I don’t think that’s the case just because of the new update, it all depends on your current docs structure and you can probably just make small adjustments to account for it.

1 Like

Woohoo, President Shir Shir [:arrow_upper_right:] strikes again! :upside_down_face:

Congrats everyone on the great work!

Super happy that you decided to not charge 2x the subscription for the AI unlike the N-word app :wink: And even if this means upgrading a couple more editors to makers (which is totally justifiable) it’s still gonna be a bargain compared to the competition.

Also SUPER happy on raising the limits for soloists! I’ve been long asking to raise at least the object limit as it was promoting bad practices (I didn’t mind the 1000 rows limit on free users though) but this is even better.

The 2-way sync, I knew it was coming but sadly was too busy to apply it to Sync Tables Pro or generally play with it :frowning: Gonna make time to test it out sometime soon.

Also many of my clients will definitely enjoy sync pages :slight_smile: Gonna test that one out as well! Wondering what the security implications are.


On the “only makers can make pages now” update, uhh… I actually welcome it? I mean, in my paradigm and the paradigm I teach to my clients, a maker is a person who set up the doc for everyone to use. It is up to the maker to set up all the necessary pages, and it’s actually good that regular users of the doc (i.e. editors) cannot mess this up or clutter this up. In fact, I take this idea further and suggest that in a client’s workspace, there’s a dedicated “Admin” Maker account (which can be the only one) with login/password access that is used to set everything up, but everyone else including the top management are mere editors.

I’m yet to encounter a use case when users of the doc would want to create ‘left pane’ pages in the doc. In my paradigm, they are meant for doc structure and not so much for casual writing. If users need canvases to type in, I give them a table with a canvas column to structure their page content — if I understand correctly, this isn’t tiered; anyone can still edit canvases.

(That said, I hope Coda implements a feature where canvas columns can be displayed as pages on the left panel :slight_smile: because for those wiki-ing use cases, of course seeing the pages on the left is much more convenient than in a table)

19 Likes

We use our Doc as a wiki. How are we supposed to adjust our Docs to allow Editors to maintain Wiki structures?

Thanks for the candid feedback, @Timothy_Choi. Your workspace admins should have received or be about to receive an email with more detail specific to your Coda account, and here’s a broader community post explaining the rationale.

A little more about why we made this change: over the years, we’ve added a lot of value at the page level, and pages have gained a ton of customization options, features, and flexibility - most recently with today’s launch of Coda 4.0. Our intent with Maker Billing has always been to only charge for makers — those who use Coda to create tools, processes, and rituals to enable their teams.

With this change, we’re realigning our roles and their definitions with this original intent. We know this will impact some teams’ usage, so we’re happy to help work with you to find a solution. We have a generous discount specifically for non-profits that might apply to you and your team. Check it out and let us know if you have any questions or would like to talk it through.

4 Likes

Congrats to the whole Coda team! :heart_eyes: :smiley:

2 Likes

I already have an Enterprise plan with Coda for one of my nonprofits because that’s the only way to get Groups if you don’t have GSuite (SCIM is nice but I can live without it); I’ve been told we’re ineligible for nonprofit discounts under Enterprise.

I’ve been planning to pitch Coda for another nonprofit that I work with but this pricing model change completely throws the plan out of the window. Guess we’re stuck with Confluence Data Centre for the foreseeable future.

1 Like

I love it!

“Other companies charge for AI features, but we’re making it FREE for doc makers!”

I love it :heart_eyes:

3 Likes

I agree with @Paul_Danyliuk and @Leandro_Zubrezki that this moves the paradigm closer to one of a developer/app with the makers being the dev’s and the users being the editors.

However we still have a few gaping holes. Publishing seems to be the closest to the app experience - it removes the search, hidden pages - and gives the users a more familiar app experience. However editors still can find the ‘edit version’ of the doc in their coda.io workspace. Can you fix this so we can provide our users a cleaner, more secure experience ?

4 Likes

Such exciting news! I have so many fond memories of the 1.0, 2.0, and 3.0 launches. Cheering for the whole :coda: team on this new milestone :clinking_glasses: :tada:

14 Likes

For anyone concerned about who can create pages, here’s my take on how you can make something like a wiki with far fewer pages and get your data in tables and canvas columns instead. This route is far more functional, scalable, and usable.

I hope it helps!

Table driven company wiki - video

11 Likes

How is that better than just… having pages? You lose all of the hierarchy that pages provide, and it doesn’t integrate with the sidebar.

1 Like

Hey @Timothy_Choi !

We can take a look at your non-profit discount, I’ll DM you!

2 Likes

Hi @Timothy_Choi,

Check out the video as it explains all the benefits. I’m not suggesting a workaround by doing this, I go through how this brings a doc build to the next level.

Check it out!

Table driven company wiki - video

I don’t need any of the advanced feature you mentioned in the video. I know my users will need to scan for pages in a hierarchy which naturally categorizes the pages anyway; a table cannot do this.

Coda’s original paged structure was perfect for Wikis. Why shoehorn it into tables?

1 Like

Amazing set of product launches. The current feel and polish on the product is second-to-none. Go team!!

5 Likes

I love how Coda 4.0 lets us move beyond the PROMPT as the only paradigm for harnessing AI.

Instead of being limited to long, complex, verbose prompts, we build AI functionality using Coda’s Formula Language (much more precise and reusable) referencing data in our Tables and content in document Pages.

This is a HUGE advance over the dark art of “prompt engineering” with all its secret incantations, obscure tricks, and long-winded hard-to-reproduce prose.

Now we can invest our ingenuity in building low-code FORMULAS that instruct the AI model with precision. And build up a reusable library of such formulas that have been properly tested.

Coda AI also allows the results from the AI model to be parsed, processed and stored in our Tables alongside all the regular calculations we are used to creating with formulas.

Prior to Coda 4.0, we had to rely on more advanced coding techniques using tools such as Langchain. Now our ordinary makers can exploit advanced AI techniques in their solutions using familiar formula methods.

This is a game changer!

9 Likes

Oh wow yes christmas has come early!! Been waiting for this since I started using Coda, and two-way sync now finally allows us to scale Coda’s use and get out of the one massive central doc issue.

Thank you Coda team!

1 Like

Hi @Timothy_Choi,

Check out the video as it explains all the benefits. I’m not suggesting a workaround by doing this, I go through how this brings a doc build to the next level.

Check it out!

Table driven company wiki - video

This almost highlights the problem here even more - why further un-empower pages through these pricing tier changes when inevitably Coda is flexible enough to have half a dozen ways to get around almost any roadblock imposed by a pricing model?

From a “Maker” perspective, pages are already not greatly utilized in Coda since anything that lives outside a table is losing out on a lot of the functionality that makes Coda great. If you’re a robot, having your wiki in a table makes sense. But pages are fundamentally intuitive to people and a great organizational tool for people who aren’t power users, and this pricing restructure takes it away from those people specifically. Just seems backwards to the stated intent of only charging for makers. I want pages to be better in Coda than they currently are, not something I need to avoid if I want to keep my costs down. Now they’re just canvases that you might have to pay extra to use.

The best thing about Coda is its flexibility. Although this change doesn’t completely invalidate any of my docs, it certainly has created a lot of work for me to make sure that all my docs will continue to thrive under this new imposition. I can also definitely see how someone who took a different tactic to building their docs out would suddenly now have to pay a much higher price just to keep their docs built out the way they prefer.

Coda is an insane bargain as-is, but only for a very specific use case. This change to page creation makes that use case even more narrow. It restricts approaches to how you can go about structuring your doc.

Love the app - you guys are absolute geniuses as far as I’m concerned and are way ahead of the competition on all fronts. Love the 4.0 release. Love the upcoming project management features. I am very much willing to pay you for the value you provide to me, I just don’t want to be slowly pushed into using Coda in an increasingly specific way as a consequence of optimizing for a more and more oppressively specific pricing structure.

3 Likes