Referenced by

The Referenced by field shows every record that points at the current one through a Reference field, giving a live two-way view of cross-project relationships.


The Referenced by field shows every record that points at the current one through a Reference field — giving you a live, two-way view of cross-project relationships without leaving the record.

Where a Reference field tracks “this record points at which other records?”, a Referenced by field flips it around: “which other records point at this one?”

Use cases

  • Customer 360 — on a Customer record, surface every deal, ticket, invoice, or task that links back to it.
  • Reverse traversal — see all child records linked to a parent without opening every related project.
  • Cleanup safety — before deleting a record, see everything that depends on it.
  • Feed Lookups — a Referenced by field can feed a Lookup, letting you pull data back along the relationship (see Bidirectional Lookups below).

Configuration

A Project Administrator sets up the field once per project:

  1. Add a new custom field and pick Referenced by.
  2. Choose the source workspace — the project that contains records pointing back here.
  3. Choose the specific Reference field in that workspace that creates the link.
  4. Optionally apply a filter to narrow the list of referenced records (e.g. only show open tasks).

Once configured, the field stays live: any record that gains or loses a matching Reference value updates here automatically.

Behavior

  • The field is read-only — you can’t manually add or remove entries. It mirrors the Reference field that points at this record.
  • Clicking a referenced record opens it in a side panel without leaving the current view.
  • Removing or changing the source Reference value also removes it from the Referenced by list, instantly.

Bidirectional lookups

Because a Referenced by field exposes a list of records, a Lookup field can read from it just like it reads from a Reference field. That means a lookup can travel either direction along a relationship — pulling data back to the referenced record, not just forward to the referencing one.

On a Customer record with a Referenced by field configured against a Tasks workspace, drop in a Lookup pointed at the Referenced by field to pull the due dates, statuses, tags, or assignees of every task linked to that customer — no extra Reference field on the Customer side needed.

Combine Reference, Referenced by, and Lookup to model many-to-many relationships across projects without duplicating data.