I have used the new page embed to share selected information with a client in a separate doc. That worked well. Anyhow, I needed to indicate which pages were new or have been updated. Therefore, I have created a table, where each row links to each page.
I would like to have the option to create such a table linking all pages in a document. This would allow to enrich the table with relevant attribute data.
Check out Scott Weir’s Doc Explorer pack, sounds like it might help out? Doc Explorer Pack, extend Coda with Doc Explorer - Coda
It will give you a table that keeps track of when the last time each of your pages was updated. But most importantly it gives you an automatically updating table with a row for each page in your document, so you can then expand upon that page list with the further attribute data you’re wanting to present.
This is fairly close to solving the issue brought up in this thread, but not quite.
First, it doesn’t actually roll up the things you type out on each of your pages to be accessible in the table. So things you type on a Coda page stay as “dumb” data.
Second, as it stands, its a chore to surface that attribute data onto the actual page since as far as I can figure out the only way to display it is basically a completely manual process of adding a custom formula to each page you make. Maybe a Coda master could find a better way, but when I looked into it I hit a dead end because there’s really very little to work with pages in Coda’s formula system.
More reason to properly implement what Paul is suggesting and give pages better support! I actually made a suggestion box post for this feature a little while back before this discussion even started, give it a +1 if you want: Create Auto-syncing Pages Based on Row Data
1 Like
I don’t think it have anything to do with ‘getting used to free.’ Some of us already use free tier or paid tier AI solutions elsewhere, and the quantity of usage comes with a cost. That is absolutely normal.
But why would I move my AI workflow to Coda when it will cost a lot more for my usage? I can simply get a subscription for OpenAI, and it will be cheaper.
If there is some special integration in Coda that will allow me to use AI in a unique way and simplify my workflow more than an external tool, I don’t mind paying.
But for now, the AI assistant functions in Coda don’t justify the pricing (paying additional seat for a few credits).
And for the most part, we all still mainly use generative AI.
Some of us are voicing their opinion about the marketing message that now we get ai included for free while it’s barely useful (because of the limitations) in most people usages. Not because we want everything free.
2 Likes
Thank you. I will install the pack and check it out.
Let me know if you have any questions! Happy to help out (as I made the pack for this purpose)
1 Like
Same here. We have 50 users that may need to create pages once in a while. Feelw unfair to get the pricing change when you just started migration from Notion and Clickup. There is no way we can afford $15k a year as subscription. And it’s a huge pain in UX to make people ask someone to create page for them.
AI features are also not free at all. With the way how you calculate credits you need to buy docmaker licence for almost all active users.
1 Like
1000+! The decision to limit page creation to editors is truly “genius”. And yes, that’s sarcasm. What worries me is this disturbing tendency to cut functionality that, on the contrary, needs to be improved. And even if the developers decided to make this limitation, how about offering some improvement of this functionality on another plan? For example, block the ability to display hidden pages. One possibility would be to provide granular access within a single doc. Then maybe it wouldn’t be so frustrating.
I reread the posts above that explain this ingenious solution. It only brings a smile to my face. A depressing smile. Users use the functionality as it is convenient for them, it is not worth explaining to them that they did it wrong and did not understand the principle of work in Coda at all. It was convenient for them and that’s it!
1 Like
I bought coda during the AI beta, and had a blast, and used it tons. As soon as you implemented AI credits, I no longer use it, well, I do for something Im too lazy to export, but you get the gist.
Have you guys on the product end notice a decline in usage among newer-ish users that come on during the AI Beta?
For me and my workflows, and the example Shishir used in the 4.0 update (the “…she hit a button and all of her clients had emails created and sent…”) those are extremely resource intensive on AI credits and I’m sure I’m not alone. Will be interesting to see how this plays out long term.
Respectfully,
“Super” Mario Lopez
Founder | Super Mario’s Digital Assistant
3 Likes
I’m a solopraneur and for 2 years I’ve been using coda for personal budget keeping and it is the best tool around. No tool comes even close.
Now, I planned to use it for my business, upgraded the plan to Teams (even tough it is only me), and spend like 2 hours looking into coda’s AI… it is great, awesome really, and the possibilities are endless. But the “free” AI for doc makers is just not true.
There is nothing free about the AI… it is 3000 credits per member on the teams plan. And these credits burns quicker than literally EVERY single tool in the market that offers AI.
It is really sad that I have to switch to an inferior tool like notion or clickup, just because coda charges an UNBELIEVABLE high price. It really is something like 20x what you pay for chatgpt4 api. It really is.
If you write like 10 emails with it, the 3000 credits are gone.
For a solopraneur to be confortable with the AI usage for a whole month (including project planning, marketing content, etc), coda needs to offer something like 100x to 300x the amount of credits per doc maker it is currently offering.
Look, I don’t mind paying a reasonable price. If I had to pay $50 per month to have unlimited usage, like notion ($10) or clickup ($5), I would. I would GLADLY pay. Because coda is SO MUCH BETTER.
But it seems that coda is trying to become something like salesforce. Only fortune 500 should ever look at it… Really sad.
4 Likes
If the OpenAI API is so much less, why don’t you just use that, via the great pack that already exists? Save the Coda AI for the things only it can do.
Saying this suggests you have no understanding how Coda AI manages retrieval augmented generation (RAG).
If you try to use the AI Pack, you must build a RAG system around it. This is impractical and near impossible.
What are the things only it can do?
The OpenAI pack is fine. It works well in a narrow set of contexts, generative AI in a cell for example, but here are a few contexts where it doesn’t work and for a variety of reasons.
- Chat with your doc or subsets of your doc.
- AI Blocks can’t use a formula in a pack.
- Column and row data cannot be used to make inferences.
Coda AI (intentional past tense) was good at providing the underlying infrastructure that performed several RAG functions. Expanding a pack to do these processes is very complex, maybe not possible.
1 Like
Does this change mean that Editors can’t view hidden pages? We’ve been doing this forever, and now suddenly today it shows the following:
Tried with people in our workspace and people outside of it.
It’s fine if we send people a link directly to the hidden page.
This is super annoying and almost totally broke what we use Coda for (teaching students w/ help from mentors)
1 Like
This is a huge, and immediate negative impact to my team. The fact that only Doc Makers can add and manage pages in a doc is a huge and sudden crippling of my team and the way we work. I was pushing for my company to get a wide enterprise license but now will have to reconsider. This has directly impacted my team as of today.
Very disappointed in Coda.
3 Likes
Hey Nikil—that’s correct, one of the Coda 4.0 changes was making showing hidden pages unavailable for editors.
One way this can still work for you is to have editors bookmark the page in their bookmarks. Your Editors can go ahead and bookmark the specific hidden pages they need regular access to in their docs, and they can access them as needed via My bookmarks at the top of the page list.
1 Like
Hi Jim, I’m sad to hear this has had a negative impact on your team. Have you reached out to our support team at support@coda.io yet? We’d love to help find a solution that works for your team!
Hey Daniel, thanks for the candid feedback on AI.
@DavidK just shared our short- and medium-term roadmap for credits today, and we’re planning to include an unlimited option:
1 Like
And it doesn’t even support the “fortune 500” usecase because
A) The tables only support ~10k to ~20k rows before grinding to a total halt
B) The API is super rate-limited, and the queue to write rows can sometimes take several HOURS to commit your changes
1 Like
Hey Brian,
Me and some of my friends are doc makers with their own subscription.
We used to collaborate in docs that we share with each other, but with the new rules (page management, hidden pages, new pages, etc.) this has become a bit more complicated.
Do you think it would be an option for Coda to allow doc makers to have full rights in docs that are shared with them? Also think about supporting third parties, which is now quite a bit more complicated. After all, the people I am talking about, have a doc maker subscription, which is what this whole idea was all about.
Consideration: I think it should be a choice when sharing a doc to grant an ‘external’ doc maker full maker rights or edit rights. Imagine the situation where someone tries to get ‘smart’ with us by getting his own subscription and from then on have full maker rights without the doc owner being aware of that - or being able to prevent that. Therefore an extra sharing option (maker). When allowing someone the ‘maker’ share, obviously it should only work that way if this person has a valid subscription with Coda.
5 Likes