Feature request: Preserve the originating connected view in comment notification links

1

Hi Superhuman Docs team,

I’d like to suggest an improvement to comment notification links for connected views.

When someone is @mentioned in a comment on a connected view—such as a Board or Kanban view—clicking the notification currently opens the underlying base-table row. If that base table is intentionally hidden, this can be confusing because the user is taken away from the curated view where the team normally works.

Steps to reproduce

  1. Create a base table.
  2. Create a Board or another connected view of that table.
  3. Hide the base table from normal navigation.
  4. Add a comment to a card in the Board and @mention another user.
  5. Have the mentioned user open the notification link.

Current behaviour
The notification opens the row in the hidden base table.

Suggested behaviour
It would be very helpful if the notification could:

  • open the same connected view where the comment was created;
  • preserve the originating view in the deep link; or
  • allow makers to choose a preferred destination view for comment notifications.

Why this would help
Many teams keep base tables hidden and present users with curated Board, List, or Calendar views. Preserving the originating view would maintain the intended workflow, reduce confusion, and keep implementation details out of sight for end users.

This would be especially valuable for task-management workflows where most collaboration happens directly from Board views.

Thank you for considering this feature request!

2

That’s really a nuisance for me as well and not only with comments notifications but with notifications in general. Where possible I have to include an additional link to the table view, hoping that the user will click that and not the default one at the bottom of the message received.

3

thank you @Gaurang_Ruparelia for detailng a long standing pain point (notifications link to the base table, not to the view of the table like cards). A workaround is the combination of email with an openRow() logic that opens the intended view. But it is cumberstone. It should be solved. cheers, christiaan