# Default row opening settings

**URL:** <https://connect.superhuman.com/t/default-row-opening-settings/60504>\
**Category:** Product Feedback\
**Created:** [April 27, 2026, 12:46pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504 "2026-04-27T12:46:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Echo3\_Echo3](https://avatars.discourse-cdn.com/v4/letter/e/e68b1a/32.png) [@Echo3\_Echo3](https://connect.superhuman.com/u/Echo3_Echo3)\
**Post date:** [April 27, 2026, 12:46pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/1 "2026-04-27T12:46:00Z")

</div>

Hi Coda Community,

I would like to suggest better table-level control for how rows are opened.

Currently, we can create an OpenRow() button and define exactly how the row should open. This works great. However, users can still open the same row through the default hover icon or other default row-opening actions, which may ignore the intended setup.

Two possible fixes would be very useful:

1. A table-level option to disable default row opening, while still allowing rows to be opened through buttons.

2. Table-wide default open-row settings, so no matter how a user opens a row, it always opens in the selected position and view, for example on the right side with a specific detail view.

Either of these would help doc builders control the layout and user flow more reliably, especially in team docs where it is hard to make sure everyone always uses the correct button.

---

<div class="post-metadata">

**Author:** ![Christiaan\_Huizer](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/christiaan_huizer/32/28269_2.png) [@Christiaan\_Huizer](https://connect.superhuman.com/u/Christiaan_Huizer)\
**Post date:** [April 27, 2026, 1:38pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/2 "2026-04-27T13:38:43Z")

</div>

thanks for bringing this up.  
the openRow() logic as it is suffers from sub optimal design to put it mildly.  
this blog post from a while ago points to a related problem. The day Codans believe this issue is serious enough to be fixed, they have something to start from --🙂

[https://huizer.medium.com/how-to-coda-a-vieworlayout-2acbed0391d7](https://huizer.medium.com/how-to-coda-a-vieworlayout-2acbed0391d7)

---

<div class="post-metadata">

**Author:** ![Echo3\_Echo3](https://avatars.discourse-cdn.com/v4/letter/e/e68b1a/32.png) [@Echo3\_Echo3](https://connect.superhuman.com/u/Echo3_Echo3)\
**Post date:** [April 27, 2026, 2:13pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/3 "2026-04-27T14:13:27Z")

</div>

Thanks for sharing this.

I understand this is not a new issue and has probably been around for a while. Still, I believe suggestions are being taken more seriously lately, so I really hope this problem gets addressed.

A lot of things in Coda can usually be solved with some kind of workaround, but unfortunately I have not found a reliable workaround for this one.

---

<div class="post-metadata">

**Author:** ![Max\_OBrien](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/max_obrien/32/49285_2.png) [@Max\_OBrien](https://connect.superhuman.com/u/Max_OBrien)\
**Post date:** [April 28, 2026, 2:33pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/4 "2026-04-28T14:33:11Z")

</div>

I always edit the layout of the default dialog for tables so the user sees the layout i want even if they open the row using the default UI widget.

---

<div class="post-metadata">

**Author:** ![Echo3\_Echo3](https://avatars.discourse-cdn.com/v4/letter/e/e68b1a/32.png) [@Echo3\_Echo3](https://connect.superhuman.com/u/Echo3_Echo3)\
**Post date:** [May 18, 2026, 3:04pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/5 "2026-05-18T15:04:20Z")

</div>

The more I work with Coda, the more that automatic **“expand row”** button annoys me.  
The easiest fix would be to add a table setting that allows users to disable the **“expand row”** button. If there is a **“Pin expand row button”** option, there should also be a **“Disable expand row button”** option. That would solve the issue completely.

Please, Superhuman and the Coda team, could you fix this?

@Ruggy-Joesten , I know your voice carries weight in this community – could you please push this internally?  
This really feels like an easy fix, but it would add a huge amount of customization and flexibility for users.

---

<div class="post-metadata">

**Author:** ![Ruggy-Joesten](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/ruggy-joesten/32/50260_2.png) [@Ruggy-Joesten](https://connect.superhuman.com/u/Ruggy-Joesten)\
**Post date:** [May 18, 2026, 4:53pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/6 "2026-05-18T16:53:35Z")

</div>

Hey @Echo3_Echo3!

Yes, and thank you for tagging me in here. Let me take this to the team and see if there are any immediate plans to address, or how quickly the fix can be enabled.

---

<div class="post-metadata">

**Author:** ![Shelley\_Garg](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/shelley_garg/32/26562_2.png) [@Shelley\_Garg](https://connect.superhuman.com/u/Shelley_Garg)\
**Post date:** [August 15, 2026, 12:46am UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/7 "2026-08-15T00:46:07Z")

</div>

@Echo3_Echo3 - curious to learn more about the request here! Where does updating the layout for the table you’re working with fall short? Are you looking to override the user’s row position setting? Thanks!

---

<div class="post-metadata">

**Author:** ![Echo3\_Echo3](https://avatars.discourse-cdn.com/v4/letter/e/e68b1a/32.png) [@Echo3\_Echo3](https://connect.superhuman.com/u/Echo3_Echo3)\
**Post date:** [October 8, 2026, 1:23pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/8 "2026-10-08T13:23:50Z")

</div>

Hi @Shelley_Garg , sorry for late reply.

**The main issue is that the built-in expand icon on the left of the table is always available, but I can neither configure how it opens a row nor turn it off.**

Of course, I can create a custom `OpenRow()` button that opens the row exactly where and how I want. But that workaround doesn’t solve the problem: the default expand icon remains there, and users can click it at any time. I can’t make my custom button the only way to open a row.

I show the main information in the table and design the detailed row layout for the right-side panel, so users can fill in the details while keeping the table visible. The default icon instead opens the row in the center and blocks the table.

I also have buttons inside the detail view that open other rows on the right. So a user can open one row in the center, click a button inside it, and suddenly the next row opens on the right. That inconsistency makes the workflow confusing.

I’d like the doc maker to control this for **each table and each table view** : either configure the built-in expand icon’s position and layout, or disable it and use custom buttons.

**Having a built-in action that cannot be configured or disabled means I can’t make the experience consistent for my team, regardless of how I design the document.**

---

<div class="post-metadata">

**Author:** ![tomldn](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/tomldn/32/50306_2.png) [@tomldn](https://connect.superhuman.com/u/tomldn)\
**Post date:** [October 8, 2026, 7:29pm UTC](https://connect.superhuman.com/t/default-row-opening-settings/60504/9 "2026-10-08T19:29:52Z")

</div>

Highly agree with this. It can get annoying to have a custom button built for routing layouts (especially when they need to be controlled dynamically) and still having the expand row button show up. I always have to provide a fallback layout which can be a little awkward.
