DAM setup guides

Bynder

Connect Bynder with your portal URL and a permanent token.

What you'll need

  • Your Bynder portal URL — the full domain you use to reach Bynder
  • A permanent token with permission to read assets and add new versions

Create the token

Create a permanent token in your Bynder portal settings, granting the permissions needed to read assets and upload new versions of them. Copy it when it's shown.

Name it Inverity so it's identifiable in your token list later.

Connect

  1. In the Inverity dashboard, open Connectors and choose Bynder.
  2. Enter your portal URL exactly as it appears in your browser, and paste the token.
  3. Select the collections you want watched.

How write-back works

Inverity adds the optimized file as a new version of the asset. Your master is not overwritten, and Bynder's version history records the change. See How write-back works.

Good to know

  • The portal URL must match exactly, including the subdomain. A "domain not found" error is almost always a mismatch here.
  • Existing assets need a run. Watching a collection covers new uploads; run optimization on the collection to process what's already there.
  • Derivatives. Bynder generates its own derivatives from the asset. Confirm on a test collection that the derivatives your teams consume behave as expected before running a full library.
  • Consider a conservative profile. A DAM usually holds source-of-truth assets that get re-edited downstream. See Quality and profiles.

Disconnecting

Remove the connector in Inverity, then revoke the token in Bynder.

Troubleshooting

  • "Domain not found" — check the portal URL character by character.
  • "Token is invalid" — the token may lack upload permission, or may have expired.

See Connector errors.

Previous
BigCommerce