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

# Bynder

> Connect Gradial to Bynder for digital asset management — search, curate, tag, and upload assets from a single flow.

Connect Bynder once and Gradial can work across assets, collections, metaproperties, tags, automations, and uploads without leaving your workflow.

***

## What You Can Do

<CardGroup cols={2}>
  <Card title="Asset discovery" icon="magnifying-glass">
    List and keyword search assets. Filter by Bynder property queries (e.g. `property_Status: Approved`). Run text-based similarity search to find lookalike assets across the portal.
  </Card>

  <Card title="Asset management" icon="images">
    Read asset stats and versions. Update name, description, tags, and metaproperty values. Add or remove metaproperty options. Fetch download locations and request dynamic transformations.
  </Card>

  <Card title="Collections" icon="folder-open">
    List, create, read, update, and share collections by email. Add or remove assets from a collection. Manage collection media.
  </Card>

  <Card title="Uploads" icon="cloud-arrow-up">
    Prepare multi-chunk uploads, push base64-encoded chunks with SHA-256 verification, and finalize uploads to land new assets in Bynder.
  </Card>

  <Card title="Metaproperties" icon="tags">
    List, create, read, update, and delete metaproperties. Manage options on a metaproperty. Bulk add or remove tags on assets.
  </Card>

  <Card title="Automations" icon="gear">
    List configured Bynder automations so downstream syndication workflows stay in sync.
  </Card>
</CardGroup>

***

## Prerequisites

* Admin access to your Bynder portal to create tokens or OAuth apps
* A Gradial organization **Administrator** role to complete setup

***

## How to Connect

<Steps>
  <Step title="Get your authentication details from Bynder">
    Sign in to your **Bynder portal** as an account admin and open **Settings → Apps & Integrations** (or **Permanent Tokens**, depending on your portal version).

    Choose the auth method that fits your security requirements:

    **Permanent Token (simplest)**

    1. Create a dedicated permanent token for Gradial.
    2. Scope it to the operations you want available: asset read/write, collections, metaproperties, tags, automations, uploads.
    3. Copy the token value.

    **OAuth2 Client Credentials (recommended for production)**

    1. Create a dedicated OAuth2 app for Gradial.
    2. Grant it the asset, collection, metaproperty, tag, automation, and upload scopes.
    3. Copy the **Client ID** and **Client Secret**.

    Also copy your **Bynder Base URL** — your portal origin, for example `https://acme.bynder.com`.

    <Warning>
      Always create a dedicated token or OAuth app for Gradial rather than reusing a shared credential. Grant only the scopes needed for your workflows.
    </Warning>
  </Step>

  <Step title="Add the integration in Gradial">
    1. In Gradial, go to **Settings → Integrations**.
    2. Find **Bynder** and click **+ Add**.
    3. Fill in the connection details:

    | Field                          | Value                                                                                      |
    | ------------------------------ | ------------------------------------------------------------------------------------------ |
    | **Integration Name**           | A display name (e.g., `My Bynder Portal`)                                                  |
    | **Bynder Base URL**            | Your portal origin — HTTPS required, no path or query (e.g., `https://example.bynder.com`) |
    | **Authentication Method**      | Permanent Token or OAuth2 Client Credentials                                               |
    | **Token / Client ID + Secret** | From step 2                                                                                |

    4. Click **Save**. Gradial validates the connection to confirm it can reach your portal before any agent work runs.
  </Step>

  <Step title="Assign to an Environment">
    1. Go to **Settings → Environments** and select the Gradial Environment where Bynder should be available.
    2. Add the Bynder integration to that Environment.
    3. Repeat for any additional Environments.
  </Step>
</Steps>

***

## How It Fits Into Broader Workflows

| Use case                    | How to use it                                                                                                           |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Campaign asset sourcing** | Use Bynder as the source of truth for approved creative when generating, editing, or QAing content elsewhere in Gradial |
| **Collection curation**     | Curate audience- or campaign-specific collections without context-switching to the Bynder portal                        |
| **Metadata governance**     | Bulk-apply Status, Channel, Campaign, or other metaproperty options across assets discovered by search                  |
| **Tag management**          | Tag and re-tag assets so downstream Bynder automations, search, and syndication keep working as campaigns evolve        |
| **Asset ingestion**         | Upload newly generated creative back into Bynder so assets stay under DAM governance from day one                       |

**Example workflow — Assemble a campaign in Bynder from Gradial:**

1. Search Bynder for `keyword: "spring campaign"` and filter by `property_Status: Approved` to find existing approved candidates.
2. Open one asset to review stats, versions, and current metaproperty values.
3. Apply campaign-specific tags and metaproperty options in bulk.
4. Curate the assets into a new collection and share it with stakeholders.
5. Upload any newly generated creative into Bynder, then tag and add it to the same collection.

***

## Support

Contact your Gradial onboarding lead or email [support@gradial.com](mailto:support@gradial.com) for help with setup.