CMS reference fields currently only work in one direction: if Collection A references Collection B, there’s no way to access that relationship from B’s side.

Example: A “Projects” collection references “Team Members.” On a project page, you can show the team but on a team member’s page, you can’t list their projects without manually duplicating the reference.

Request: When a reference field is created from A → B, automatically generate a reverse reference on B → A (offer a toggle like Notion). This would allow filtering and displaying referencing items from the other side.

This unlocks most relational content patterns (posts ↔ tags, products ↔ collections, events ↔ speakers) without workarounds or manual sync