Copying an asset and its updates to another site
You can copy some assets and any future updates from one site to another. Doing so links the two so that any updates made in the original asset are reflected in the copy. If additional assets are created from the copy, then they, too, receive updates from the source asset if it is updated. For example, if an article is copied with updates, and then an Apple News Article is created from the copy, then changes made to the source article will cascade down to its copy as well as the Apple News Article.
To use this feature, content sharing between sites must first be enabled. For details, see Enabling content sharing between sites.
To link an asset and its updates to another site:
- Ensure you are on the site to which you intend to link the original asset and its updates. For details, see Switching sites.
- Click the search bar to open the search panel.
- Under Misc Filters, select the site containing the original asset that you want to link to your current site.
- Search for and open the original asset that you want to link to your current site.
- From the content edit page, click to open the content edit actions menu, then click Copy with Updates.
- Complete your site's workflow and publish the asset.
When opening the original asset, Brightspot includes a note that any updates made to it are shared to the copy.


Brightspot also includes a message on the copy.


By default, if you were to archive the source asset, its copy and any other assets downstream remain untouched; however, you may choose to override this setting so that archiving the source asset also archives any copies. To do that, developers can override SharedContent#shouldArchiveSharedContentCopies
in the data model file (like Article.java
), as shown in the following example. If this measure is taken, then restoring the source asset to a non-archived state will not restore the copies to a non-archived state. The copies will instead need to be individually restored.
@Override
public boolean shouldArchiveSharedContentCopies() {
return true;
}