Skip to main content
How-To

Manage saved Project Assets

Learn how to set expiry, delete, or replace saved Project Assets when work changes.

Last verified 1 day ago

Project Assets are reusable files and generated assets saved to a project. You can manage them by setting expiry, disabling or deleting project copies, editing supported assets, and replacing outdated work with a newer version.

Project Assets list with search, filters, asset type labels, shared-org labels, and expiry dates.
The Project Assets list exposes filters, asset types, sharing scope, and expiry dates for saved assets.

Use these controls when a saved asset is stale, temporary, duplicated, or no longer safe to reuse.

Open Project Assets

Open the project library or Project Assets panel. Use search, asset type filters, sort, and expiry filters to find the item.

Select an asset to preview it. Some assets support preview/raw view toggles, editing, downloading, or print-to-PDF depending on the asset type.

Set an expiry

Open the asset's more-options menu and select Set expiry. Choose Never expires or Expires on a specific date.

When you pick a date, Ampere uses the local expiry cutoff shown in the dialog. Choose a future date. Expired items should not be treated as current project context.

Disable or hide an asset for a project

Some asset rows include an on/off control. Turn an item off when it should be hidden for that project without deleting the underlying history immediately.

Use this for stale context that you may want to inspect later but do not want Joule to rely on.

Delete an asset

Use Delete from the asset actions when the project copy should be removed. Deletion can remove access to the saved item, so confirm that the team no longer needs it.

If the asset is shared org-wide or appears in multiple contexts, check the source and sharing state before deleting.

Replace outdated assets

To replace an asset, create or upload the new version, confirm it appears in Project Assets, then disable, expire, or delete the older version. Keep both versions briefly if your team needs to compare them before switching.

For templated reports, save edits before printing or using the report as current context.

Was this article helpful?

Related articles