---
schema_version: "1"
id: 87e81b1fd00e1365ebe73ca5636843f2471ebb5b592621c57d6debf4a802ce12
title: Retriever Support in Data Cloud One
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_ai_retriever_data_cloud_one.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_ai_retriever_data_cloud_one.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 36621d83998688e44baf8a4731f61a9d34239f1ca28970ae5271c6bb1c73c999
description: Learn about retriever capabilities and limitations when you work with Data Cloud One home and companion orgs.
products:
  - Data 360
release: "264"
---
# Retriever Support in Data Cloud One

Learn about retriever capabilities and limitations when you work with Data Cloud One home and companion orgs.

Understanding how retrievers work across Data Cloud One environments is based on two fundamental rules.

- You can edit or delete a retriever only in the org where you created it.
- Data Cloud One metadata synchronization happens in only one direction, from the home org to the companion org, not in reverse or between companion orgs.

## Constraints and Impacts

These constraints affect how you create and manage retrievers in Data Cloud One.

- Retrievers don't sync from Line of Business (LOB) orgs to home orgs or between LOB orgs. Each LOB org is isolated for locally created retrievers.
- Ensemble retrievers created in the home org are visible in companion orgs. When you create an ensemble retriever in the home org, it syncs to the companion orgs in the same way as an individual retriever. You can create an ensemble retriever in a local LOB org with retrievers in the same data space.
- Edit is possible only in the owning org. Switch between home and LOB orgs to tune and test retrievers.
- You can't test retrievers created in the home org in LOB orgs. You can edit, validate, and create new versions in the retriever playground only in the org that owns the retriever.

## Retrievers Created in the Home Org

This table shows what actions you can perform on retrievers created in the home org, depending on where you access them.

   
| Action | In Home Org | IN LOB OR Companion Org | In Other LOB Orgs |
| --- | --- | --- | --- |
| View (AI Models) | Yes | Yes | Yes |
| View (Prompt Builder / Flow picker) | Yes | Yes | Yes |
| Use at run time (Prompt Builder, Flow) | Yes | Yes | Yes |
| Edit | Yes | No | No |
| Delete | Yes, unless remote references exist in companion orgs. | No | No |
| Create new version | Yes | No | No |

## Retrievers Created Locally in a Line of Business or Companion Org

This table shows the actions you can perform on retrievers created in a LOB or companion org.

   
| Action | In that LOB Org (owner) | In Home Org | In Other LOB Orgs |
| --- | --- | --- | --- |
| View | Yes | No | No |
| Use at runtime | Yes | No | No |
| Edit | Depends on the creation method. | No | No |
| Delete | Yes | No | No |

If the retriever was created by Agentforce Data Library (ADL) in the LOB org, it isn’t editable in AI Models. Edit the ADL to change it. If a retriever was created using the retriever Connect API, you can edit it directly in AI Models.

## Ensemble Retrievers

This table shows the visibility and run-time capabilities for ensemble retrievers.

  
| Action | In Home Org | In LOB OR Companion Org |
| --- | --- | --- |
| Visibility | Yes | Yes |
| Run-time use | Yes | Yes |
| Managing Ensemble Retrievers | Create, Edit, and Delete: Yes for retreivers owned by the home org. | Create, Edit, and Delete: Yes for retrievers owned by the LOB or Companion org. |