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

# Share an asset with one partner only

> Give one partner a document no other partner can see, such as a signed agreement or a joint business plan, and surface it in their portal automatically.

Not all partner content is program content. A signed NDA, a countersigned reseller agreement, a joint business plan, a pricing addendum: each of these belongs to exactly one partner and must never surface to another. A partner-specific asset covers that case. Rather than controlling who may open a shared file, you make the file the partner's own, then let their portal pick it up through a section that fills itself. This guide takes you from creating the asset to the partner opening it in their portal.

## What you'll achieve

A document tied to a single partner, visible to that partner and your own team and to nobody else, listed in their portal in a section that populates itself for every partner you do this for. No segment to maintain, and no separate portal to build per partner.

<Note>
  This is a different mechanism from audience filters. A filter decides which partners may open a **shared** library asset, so one file reaches a group and access changes as partners qualify. A partner-specific asset is **owned** by one partner: it never appears in the general library or a general Asset Hub, and it carries no access settings at all, because ownership is the access. Use filters for content that goes to many partners (see [Share assets at scale](/features/content/asset-hub/guides/share-assets-at-scale-with-filters)); use this guide for content that belongs to one.
</Note>

## Before you start

<Steps>
  <Step title="Have the partner in Introw">
    The document is attached to a partner record, so the partner must exist before you upload. The partner also needs a portal experience if you want them to see the asset there.
  </Step>

  <Step title="Confirm write access">
    You need write access to assets to add the document. Deciding where it appears in the portal additionally needs write access to experiences; without it you can still upload, and the placement field is read-only.
  </Step>

  <Step title="Decide where it belongs in their portal">
    Partner-specific assets appear in a Partner Specific Asset Hub section. Pick the stage and section that fits, for example a Contracts or Legal tab rather than the general enablement tab, so the partner finds it where they expect it.
  </Step>
</Steps>

## Steps

### Create the asset for the partner

<Steps>
  <Step title="Open the partner's assets">
    Go to [Partners](https://app.introw.io/partners), open the partner, and select the **Assets** tab. This is that partner's own library. Everything you add here belongs to them, and it is where their documents collect alongside any co-branded copies Introw generated for them.

    You can also start from the **Asset library** and switch to the **Partner assets** view, which lists every partner-owned asset across your program. Start there when you are handling documents for several partners in one sitting; start from the partner when you are working one account.
  </Step>

  <Step title="Add the document">
    Use **Add asset** and pick how the content arrives:

    * **Upload** - a file from your machine, for example the countersigned PDF. This is the usual path for agreements.
    * **Import folder** - a whole folder at once, for a partner who arrives with a set of documents rather than one.
    * **Web page URL** - a link instead of a file, for example a shared plan that lives in another system and must stay editable there.
    * **Create folder** - a container first, when the partner will accumulate documents and you want them grouped, for example Contracts and Business plans. On the **Partner assets** view the folder dialog asks which **Partner** the folder belongs to; on the partner's own **Assets** tab it is already theirs.
  </Step>

  <Step title="Set the type and the owner">
    In the dialog, work down the fields:

    * **Name** - what the partner will see in their portal. Name it for them, not for your filing system: "Reseller agreement 2026" reads better than "MSA\_v3\_final".
    * **Type** - choose between **Regular**, an asset for your shared library, and **Partner Specific**, an asset owned by one partner. Started from the partner's **Assets** tab, this is already **Partner Specific**. Started from the **Asset library**, set it yourself.
    * **Partner** - the owner. It is prefilled when you started from the partner, and you pick it when you started from the library. Only this partner will ever be able to open the asset.
    * **Include in partner experience** - where the asset shows up in that partner's portal, listed as stage and section. Set it now if the experience already has a Partner Specific Asset Hub; otherwise leave it and come back after the next phase.
    * **Categories** - optional tags. Useful once a partner holds more than a handful of documents, because they drive the filters in the hub.
    * **Language** and **Variants** - the document's language, and optionally a file per additional language when your program runs multilingual portals.

    Save. The asset now belongs to that partner: it is listed on their **Assets** tab and in the **Partner assets** view of the library, and it is absent from the general library and from every general Asset Hub.
  </Step>
</Steps>

<Note>
  A partner-specific asset has no **Access** tab. Segments, portal-wide, and public visibility apply to shared assets only. Here the partner link is the access rule, which is exactly why it suits contracts and other one-to-one documents.
</Note>

### Surface it in their portal

<Steps>
  <Step title="Add a Partner Specific Asset Hub to the experience">
    The asset stays internal until the partner's experience has somewhere to show it. In the experience builder, open the stage that should carry it and add a section: **Smart sections**, then **Asset hub**, which asks whether you want to share general or partner-specific assets. Choose **Partner Specific Asset Hub**, the one described for NDAs, agreements, and co-branded material. Its sibling, the **General Asset Hub**, lists your shared library and will never show partner-owned documents.

    The hub is dynamic. It shows each viewing partner only their own assets, so you add it once to the experience and every partner using that experience gets their own list. Layout, search, filters, and columns work exactly as they do for a general hub; see [Add and configure an Asset Hub](/features/content/asset-hub/guides/add-and-configure-an-asset-hub) for those options.
  </Step>

  <Step title="Point the asset at the hub">
    Back on the partner's **Assets** tab, open the asset and go to its **Include** tab. Pick the placement, listed as stage and section, and the asset is added to that hub for this partner. An asset with no placement stays internal, which is a useful default while a contract is still being negotiated.

    If the tab offers no placements, the partner's experience has no partner-specific hub yet: it links you straight to the experience so you can add one, then come back.
  </Step>

  <Step title="Publish and check the partner's view">
    Publish the experience so the section reaches partners. From the asset's **Include** tab, use the link to view the asset in the partner experience and confirm it lands in the right stage, under the right heading, with a readable name.
  </Step>
</Steps>

### Repeat without repeating the setup

<Steps>
  <Step title="Add the next partner's document">
    For every other partner on the same experience, only the first phase repeats: upload on their **Assets** tab and set the placement. The hub is already there and fills itself, so the portal work is done once for the whole program.
  </Step>
</Steps>

## Verify it worked

Open the portal as the partner who owns the document: the hub lists it, and they can preview and download it. Open the portal as a different partner on the same experience: the same section is there and their own documents are in it, with no trace of the first partner's file. In the library, the asset appears under **Partner assets** and not in the general library, and views are recorded on it like any other asset, so you can tell whether the partner actually opened their agreement.

## Related

<CardGroup cols={2}>
  <Card title="Add and configure an Asset Hub" icon="book-open" href="/features/content/asset-hub/guides/add-and-configure-an-asset-hub">
    Configure the hub that lists each partner's own assets.
  </Card>

  <Card title="Share assets at scale" icon="book-open" href="/features/content/asset-hub/guides/share-assets-at-scale-with-filters">
    Use audience filters when content goes to many partners instead of one.
  </Card>

  <Card title="Create and share co-branded assets" icon="book-open" href="/features/content/co-branded-assets/guides/create-and-share-co-branded-assets">
    Generated copies land as partner-specific assets automatically.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full asset library configuration options.
  </Card>
</CardGroup>