> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sources

> See where a gig came from (Luma, HubSpot, Flex, an event page or a spreadsheet) and push title, date and venue changes back to Luma.

Many gigs start somewhere else: a Luma event, a HubSpot deal, a Flex quote, a Partiful or Eventbrite page, or a row in a spreadsheet. The **Connected systems** section at the top of the gig's **Links** tab lists every system the gig is linked to, with a link back to it and when it last synced.

![Links tab on a gig with the Connected systems editor open](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/gigs/sources-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=5570c4d17780b64046668526b8b48bdc)

Only people who can manage gigs see a gig's sources. Crew see the HubSpot and Flex links on gigs where they could before.

## Where sources come from

Soundcheck adds a source whenever a gig comes in from another system:

| Source | Added when |
| - | - |
| **Luma** | You import events from your connected Luma calendar. |
| **HubSpot, Flex** | The HubSpot and Flex pipeline creates the gig, or someone pastes the deal or quote link into **Connected systems**. |
| **Event pages** (Partiful, Eventbrite, DICE, Resident Advisor and others) | You create a gig from an event link. |
| **Spreadsheet** | You import gigs from a file. |
| **Pasted text** | The gig came from text pasted into an import. |
| **Jotform, Form.io, Tally** | The gig came from one of those form tools. |
| **Soundcheck**, **Clerk** | Labels Soundcheck uses for records it created itself. |

The gig header also shows a small logo for each connected system, such as HubSpot, Flex, QuickBooks, Slack, Google Drive, Dropbox, Luma or Brex. Each one opens the source in a new tab. Crew don't see these logos.

Sources are on the web only. The mobile app doesn't show them, and AI assistants connected through MCP can't list or push them today.

Editing **Connected systems** changes only the HubSpot and Flex links. Other sources are added by the import that created the gig.

## Push changes back to Luma

When you change a Luma gig in Soundcheck, the Luma event does not change on its own. To update it, open the gig's **Links** tab and choose **Push changes** next to Luma. Soundcheck reads the event from Luma and compares three things:

* **Title**
* **Date and time**, in the gig's time zone
* **Venue**, by Google place when both sides have one, otherwise by address

Each difference shows the Soundcheck value and the Luma value side by side:

| Label | Means | Pushed by default |
| - | - | - |
| **Changed here** | Only Soundcheck changed it since the last sync. | Yes |
| **Changed in both** | Someone also changed it in Luma since the last sync. | No: tick **Overwrite Luma's …** to replace Luma's value |
| **Empty here** | The gig has nothing to send (for example, no start time). | Never |

Fields that already match are not shown. Choose **Push to Luma** to send the ticked fields. If someone changes the event in Luma while the dialog is open, Soundcheck refuses the push, shows the new values, and asks again.

Luma emails guests when an event's name, time or place changes. Soundcheck turns that email off unless you switch on **Let Luma email guests about the change**. Luma still sends guests a push notification for a new time or place.

Gigs imported from Luma before this feature have no record of what Luma held at import, so the first push asks you to confirm every difference. After that first push, only fields changed in both places need confirming.

Every push is recorded in the gig's activity as **Changes pushed to source**. Organization owners, admins and gig coordinators can push. Luma must be connected in **Settings → Apps & data → Integrations**.

## What does not sync back yet

Soundcheck can only push to Luma for now. HubSpot, Flex, event pages and spreadsheets are read-only sources: their link opens the original, and changes there still come in through their import or pipeline.

## Gig links and the public link page

Below **Connected systems**, the **Links** tab holds the gig's link list, such as tickets, the organizer or a join-online link. Organization owners, admins and gig coordinators can add, edit, remove and reorder links. Everyone else who can open the gig sees the list read-only.

Turn on **Public link page** to share the links on one page that anyone can open without signing in, like a link in bio. The page shows your organization's avatar, the gig name, its dates, the venue and one button per link. Copy the address from the box under the switch. You can turn it on once the gig has at least one link. A draft, template, cancelled or deleted gig never shows on the page. Turn the switch off to take the page down. Turning it on again gives the page a new address.

## Related

> [card] [Documents](https://docs.soundchecklive.io/features/gigs/documents.md)
>
> How this fits with the rest of a gig's paperwork.

> [card] [Forwarded confirmations](https://docs.soundchecklive.io/features/gigs/documents/forwarded-confirmations.md)
>
> Bring booking emails into a gig.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.