Linked columns: showing a field from a related table — It belongs to the view, not to the table

This is the whole point of the feature, and the thing to be clear about before you reach for it. A Lookup field is a schema decision. Once it exists, it exists for everyone: in every view, in the REST API, in exports, in reports, and to formulas. That’s why creating one is an admin act. A linked column is one view’s lens. Nothing is added to the table, no migration runs, and nobody else’s screen changes — so any member can add one to a personal view and answer their own question without asking for a schema change. On a shared view it’s a view edit like hiding or freezing a column, so it takes the same permission. Reach for a Lookup when the route belongs to the table — when formulas should read it, the API should return it, or everyone needs it. Reach for a linked column when you need to see something while you work. The route is followed each time you read the view. Nothing is written onto the booking, so nothing can drift out of date.