Using tables would be a little more convenient if it were possible to add a description to the table or column.
@Nurlan_A Hello,
You can add a description in a canvas for example like any other element of a page that would allow you to indicate the information you want.
Sincerely,
Thierry
1 Like
Thierry,
I have a use case that is not quite met by your answer to the above question. I would love to be able to have metadata and a schema (ERD) that helped me find existing resources (tables) in more of a file folder hierarchical manner.
Eg my outer most layer could be Department (CX vs UXR vs data science, etc), then within department i select team. I can operate at the level of granularity that makes sense for the tables metadata classification (some should be organization wide, some department wide, etc). That way, when I want to reference a table that I suspect exists (eg CX Sprint Planning) but don’t know the exact name of, i can do that heuristically in the “schema browser” pop up that comes as the dialogue when I want to add a view somewhere.
I’d be excited to talk more if this is of possible interest but not quite making sense!
Sarah
1 Like
@Sarah_Heyborne
Hello Sarah,
I understand better now what you want to achieve. However, at my little level of expertise and to my knowledge, except for the use of a formula with a filter or even the use of an interactive filter on a specific table or column, I don’t have any other idea in mind but I will look for some on my side to help you the best I can 
Sincerely,
Thierry
1 Like
Hi, I’m Paul, a software engineer at Coda. Thanks for sharing this feature request with us — I’m happy to announce that we’ve now implemented column descriptions in Coda!
Within the column options menu, select the “Add description” option to add helpful context or reference notes about a given column. We hope this makes using tables in Coda smoother for you and your teams — let us know what you think!
5 Likes
This is a great feature! Do you have plans to introduce the table descriptions?
4 Likes
Hi, Yes I agree. Table description would be really great. Especially for the scenarios mentionned above.
1 Like
I arrive at this post 3 years after it was originally posted wondering if this is anywhere on the roadmap. I’m usually making office tools for my coworkers to use, and not everyone “gets” what tables and views are for. I would love to have the table title visible, with the option to put in a short description or instructions for users to review before they interact with the table. This could be similar to the subheadings for pages, and column descriptions.
It would be great for them to be collapsable or appear in a pop-up window on hover. The link could be under or to the right of the table edge, near to the “options” link, but remain always visible.
One work around are to add your own heading, then write your instructions/description, then hide the table title, but this gets old quickly and has the consequence of not knowing the name of the table you are working with when you are writing formulas for it (without toggling the title on and off again). It also complicates the use of page outlines and managing table title heading levels so they don’t appear in the outline along with your custom text heading.
3 Likes
I don’t have a good idea or anything to add, but I did ask a reasonably Coda-competent AI agent what it might recommend as a workaround. Use with CAUTION, but here’s what it said and this is what it created.
The document it created doesn’t seem complete, but it might be a good start. I think Coda MCP is still weak at creating buttons, especially in formulaic aspects. But it seems to have made a pretty good effort documenting its approach.
You be the judge - helpful?
I personally recommend that you create a backend UI for managing your docs, separating the original databases from the views, put all original databases in the backend, and use views to build the frontend for the user. This is important when working with other people because you don’t want to work on the same page as your users, so as not to distract them when they see you adding a new work-in-progress column to the table.
Keep everything organized and separated, so the users will not see what you are doing and stay focused on what they have to do. It also prevents you from changing too many things on the frontend, and when users come back 1 hour later, the page is completely different, making the users feeling lost.