Apps, sync & devices

Four settings connect your gallery to things outside it.

Apps

An app is an integration installed into your gallery — something a developer built against the platform's API. The important design point: an app owns its own credentials, so the integration keeps working after the developer who built it moves on. You're not depending on someone's personal login.

Installing one

There's no app store to browse yet. Apps arrive one of two ways: someone at your gallery creates one for an integration you're building, or a developer sends you an install link for theirs.

Creating one takes a name, a description, and the scopes it's asking for — which records it wants, and whether it needs to write as well as read. Scopes read plainly: Artworks: read, Contacts: read & write.

An editor can create an app, but only a gallery owner can install it, and installing means ticking approval for each resource the app asked for. The key is revealed once, at that moment. Copy it then; you can't retrieve it later.

Installing needs a plan that includes API access. On a free gallery you can create an app but it won't run.

Removing one

Uninstall stops the app and revokes its credentials, with a confirmation first. The record stays so you have the history. An app that was never installed can be deleted outright.

Builders are separate: removing a builder takes away that person's access to work on the app, but never stops the app itself.

Synchronization

Synchronization publishes your inventory to a website or portal and keeps it in step.

Each connection shows three states, which answer different questions: whether you're signed in, whether the field mapping is set up, and whether the sync is current.

Webflow

Webflow is the connection that works end to end today. You connect it by signing in to Webflow and authorising the platform. If your gallery site runs on Webflow, this is the one to use. There's an extra toggle for syncing exhibitions alongside works.

Other platforms appear in the list, but their connectors aren't finished. If you need one of those, tell us rather than setting it up and waiting.

Setting a connection up

Give it a name, choose the platform, and pick a source list — a list of works to keep in parity. Everything on that list syncs; nothing else does. It's the safest way to control what goes public, so build the list deliberately.

Then choose how much rope to give it:

• Manual — nothing happens without you approving each run.
• Notify — it checks on its own and tells you, you approve the writes.
• Auto — it applies changes unattended.

Field mapping

The platform inspects the destination and proposes which of your fields map to which of theirs. You confirm that mapping field by field before anything syncs. Nothing is guessed into production.

One deliberate limit

Synchronization never deletes or delists on the far end. Removing a work from your source list stops the platform updating it; taking the listing down is yours to do. That's intentional — an automated delist is the kind of mistake you can't undo from the other side.

Synchronization is editor-only.

Importing from Sanity

If your inventory lives in a Sanity project, you can bring it across.

Connect with a read-only token plus your project and dataset details. The token is encrypted and never shown again.

The platform then reads your dataset and proposes a mapping: which document type holds your works, and which of its fields correspond to title, artist, year, and the rest. Each suggestion shows how often that field is actually filled in, which is usually enough to tell a real field from an abandoned one. Adjust anything before continuing.

You then review a sample artwork as it would land, and confirm.

Two things worth being clear about:

• This is an import, not a live sync. It's a run you trigger. Your Sanity project and your gallery don't stay in step afterwards.
• It's repeatable. Your confirmed mapping is saved, so a later import reuses it rather than starting over.

The run history shows past, running, and awaiting-review imports, and you can discard one that's still waiting on you rather than committing it.

Editors can connect and import. Only a gallery owner or organisation admin can revoke a connection.

Devices

Devices is for traffic sensors — the hardware that counts visitors, and feeds the visitor traffic report. It isn't where you manage phones or the watch.

Each sensor shows its label, where it is, and its health: not paired, live, or silent. Silent covers both a sensor that has stopped reporting and one that was paired but never reported at all — either way it isn't counting, so it's the state to chase. The badge tells you how long it's been quiet.

To add one, generate a pairing code and enter it on the sensor. The code is shown once and expires after fifteen minutes — generate it when you're standing at the device, not before.

There's no unpair control here yet; ask us if you need a sensor removed.

Pairing is editor-only.