This article is about the Proxi admin app at app.proxi.co.
Listings and collections work together, but they answer two different questions:
A listing answers "what do we know about this place?" It's the one shared profile for a business or place in your workspace — its description, website, phone, hours, logo, and photos — reused everywhere instead of retyped.
A collection answers "which places belong in this project?" It's a group of places organized for a purpose, with its own columns. Your maps, directories, and passports all read from a collection — edit the data once and every experience stays in sync.
An Example
Say Harvest Moon Bakery is one of your downtown businesses. You create one listing for it, holding its description, website, phone, hours, and photos.
That one listing can then appear in two collections:
Downtown Businesses — powering your year-round map and directory.
Holiday Market Vendors — powering this year's market map, with its own columns like Booth Number ("A-12") and Market Special ("Peppermint croissants").
When the bakery gets a new phone number, you change it once on the listing — and both collections, the map, and the directory all update. The booth number, though, lives only in the Holiday Market collection, because it's about that event, not the bakery itself.
What Lives Where
On the listing (shared everywhere) | On the collection row (just for that project) |
Description, website, phone, hours, logo, photos | Booth or stall number |
Contacts — the owner or manager who keeps it current | Category and fields for that map's markers and filters |
Your private labels and internal notes | Event- or project-specific details ("Market Special") |
A rule of thumb: if it's true about the business everywhere, put it on the listing. If it's only true for one map, event, or program, put it in the collection.
Connecting Them
On a collection page, click Add from listings to pull listings in. Each place stays in sync with its listing — edit the listing once and it updates here too.
Open any row in a collection and you'll see whether it's connected. A connected row shows a From the listing section with the shared info; an unconnected one says "Not connected to a listing" with Connect and Create listing buttons.
Starting fresh? When you create a new collection, choose From my listings to build it straight from the profiles you already have.
When You Want One Place to Look Different in One Collection
Sometimes a place needs a different name or spot for one project — say the bakery's holiday stall sits in the market square, not at the bakery. When you edit a connected row, you'll get the choice:
Save to listing — changes the listing itself, so every map and collection showing it updates.
Save for this collection only — overrides the value just here. The row shows an "Overridden for this collection" note, and you can switch back anytime with Use listing data for all.
Deleting: Two Different Things
Deleting a row from a collection removes the place from that project only — the listing is untouched and still appears everywhere else.
Deleting a listing removes the shared profile. Rows that used it stay on their maps, but they stop pulling the listing's info, and the listing's contacts lose their portal access.
One More Reason Listings Matter: The Portal
You can add a contact — the owner or manager — to any listing. They get a sign-in link to your self-service portal where they can update their own description, hours, and photos. Because everything reads from the listing, their updates flow to every map, directory, and experience automatically — no more chasing businesses for their new hours.