> ## 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.

# Aprimo

> Connect Aprimo so Grady can file the assets and documents it produces directly into your DAM — as draft records, in the classification you nominate, ready for a librarian to review.

## Why connect Aprimo

Gradial produces real files. A generated hero image, a smart-cropped variant, a campaign brief, a copy doc, a QA report — all of it comes out of the work as an artifact. Without a DAM connection, getting those files into Aprimo is a download, a re-upload, and a metadata form filled in by hand, which is exactly the manual step the rest of the workflow removed.

Connecting Aprimo closes that gap. Grady uploads what it creates straight into your DAM, in the classification you specify, and confirms the record landed.

<Note>
  This integration is an **upload destination**. Grady files assets into Aprimo and verifies the resulting records — it does not read your existing Aprimo library or search it. For search and retrieval across your asset estate, see [Asset Search](/docs/asset-management/asset-search).
</Note>

***

## What Grady can do

| Capability                  | Detail                                                                               |
| :-------------------------- | :----------------------------------------------------------------------------------- |
| Upload assets and artifacts | Files Gradial created — images, documents, reports — into the configured destination |
| Create records              | Each upload becomes an Aprimo record in the classification you nominate              |
| Verify the result           | Grady confirms the record exists and reports its identifier back into the task       |

Records are always created with a **draft** status, so nothing Grady files enters an approved state without a person reviewing it.

***

## Prerequisites

* An Aprimo tenant and the subdomain used to reach it (the part before `.aprimo.com`)
* A **registered client** in Aprimo with a client ID and client secret
* The **classification ID** of the destination you want Grady to file into
* An Aprimo administrator to grant the client permission to create records in that classification

***

## Set up the connection

<Steps>
  <Step title="Register a client in Aprimo">
    In Aprimo, create an API client for Gradial and record its **client ID** and **client secret**. Grant it permission to create records in the classification you intend to use as the destination.
  </Step>

  <Step title="Find your classification ID">
    Open the destination classification in Aprimo and copy its ID. Gradial accepts either the 32-character form or the hyphenated UUID form.
  </Step>

  <Step title="Add the integration in Gradial">
    Go to **Settings → Integrations**, find **Aprimo** under Design & assets, and select **Connect**. Provide:

    | Field                  | Value                                                                                                |
    | :--------------------- | :--------------------------------------------------------------------------------------------------- |
    | **Tenant**             | Your Aprimo subdomain — the part before `.aprimo.com`                                                |
    | **Client ID**          | From the client you registered                                                                       |
    | **Client secret**      | From the client you registered                                                                       |
    | **Classification ID**  | The destination classification Grady files into                                                      |
    | **Allowed file types** | The MIME types Grady may upload, in `type/subtype` form (for example `image/png`, `application/pdf`) |
    | **Maximum file size**  | The upload ceiling for this connection, up to 250 MiB                                                |
  </Step>

  <Step title="Validate">
    Save the connection. Gradial validates the credentials against your tenant and reports the result immediately. If validation fails, the message names the field at fault.
  </Step>
</Steps>

<Tip>
  Keep the allowed file types deliberately narrow. The list is an allowlist, so anything not named is rejected before an upload is attempted — which is the cheapest place to catch a misdirected file.
</Tip>

***

## Rotating credentials

To rotate the client secret, reopen the Aprimo integration in **Settings → Integrations** and enter the new secret. Gradial re-validates on save. The client ID and tenant can be changed in the same step; changing either requires the secret to be re-entered.

***

## Who this is for

| Role                              | What this unlocks                                                                                                                    |
| :-------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
| **DAM Librarian / Asset Manager** | Gradial's output arriving in the DAM as draft records in the right classification, instead of as files in someone's downloads folder |
| **Campaign Manager**              | Generated and adapted assets filed as part of the campaign, not as a follow-up task                                                  |
| **Brand Manager**                 | A review step preserved by design — everything Grady files is a draft                                                                |
| **Creative / Agency**             | Deliverables and their variants landing in the system of record automatically                                                        |

***

## Availability

**Access:** Must be enabled for your organization. Contact your Gradial team to get access.