Managing Assets

Overview

Managing assets correctly keeps large configurators stable, easy to update, and free from duplicates. This guide explains how to find assets, organize them, track their usage, and safely perform replacements, deletions, and basic bulk cleanup in Amaspace.

Location: Amaspace Dashboard → Assets

What “Assets” are in Amaspace

Assets are reusable building blocks that power every configurator.

Typical asset types:

• Models (GLB/GLTF/ZIP imports)
• Materials (created/edited in Amaspace)
• Textures / Images (used inside materials)

Assets can be reused across multiple products, attributes, and PCOs.

When to use

In Amaspace, assets are used in every product—at minimum as a base model and a basic material setup, and often as shared materials/textures reused across multiple attributes and products.

Use the asset library workflow to:

• Avoid duplicates and keep one “source of truth”
• Reuse the same models/materials/textures across multiple products
• Update visuals without rebuilding configuration logic
• Keep libraries clean and scalable as projects grow

Asset library overview

All assets are managed through the PCO & Assets → Assets panel.

From this panel you can:

• View all uploaded assets
• See each asset type (Model, Material, Texture)
• Reuse assets across attributes and products

This is the central place for asset management.

Search and filters

Search

Use the search field to find assets by name.

Tip: Search works best when naming conventions are consistent.

Filters

Use the filter (funnel) icon to narrow results by:

• Asset type (Models, Materials, Textures)
• Date (recently added or updated)
• Tags

Filters are essential for large libraries and faster navigation.

Asset usage tracking

Assets can be reused in multiple places.

To check where an asset is used:

1. Click the usage icon (linked chain).
2. Review all attributes and PCOs connected to the asset.

Rule: Before deleting or replacing an asset, always verify its usage.

Replacing assets

Assets can be replaced without rebuilding the entire setup.

Typical use cases:

• Updating a texture version
• Fixing geometry issues
• Improving visual quality

When replacing an asset, verify that:

• Naming remains consistent
• The new asset matches the expected scale and format

After replacement, preview the product to ensure everything still renders and behaves as expected.

Deleting assets

Delete only assets that are no longer used.

Before deletion:

1. Confirm the asset is not assigned to any attribute or PCO (via usage tracking).
2. Preview the product after removal.

Deleting active assets can cause missing visuals or broken options.

Bulk operations

For large projects, cleanup is essential.

Common bulk tasks:

• Removing unused assets
• Replacing outdated textures
• Consolidating duplicate assets

Rule: Perform bulk changes carefully and always review the product afterward.

Organization best practices

Folder-based organization

In addition to naming conventions, Amaspace supports folder organization.

Asset folders:

• Create folders in the Asset Menu on the main platform dashboard
• Move assets between folders
• Separate assets by product, configurator, or project

Using folders makes large libraries easier to manage and reduces the risk of mixing assets from different configurators.

Common issues

• Duplicate assets with similar names
• Unused textures increasing project size
• Deleting assets still used by PCOs

Best practices

• Use consistent naming conventions for predictable search
• Rely on usage tracking before replace/delete operations
• Prefer replacing assets over creating duplicates
• Keep folders organized per configurator/project
• Do regular cleanup passes on large projects

Summary

Good asset management improves performance, reduces errors, and makes configurators easier to maintain.

Use search, filters, usage tracking, folders, and careful cleanup to keep your asset library clean and predictable.