Manage design assets
Design assets are the binary files render variants and designs point at: logos, background images, SVG and PDF templates. They are content addressed, so the same file uploaded twice is one asset with one URI, shared by every design that uses it.
Complete first: Onboard a tenant.
Steps and why they come in this order
| Step | Why here |
|---|---|
| 1. Review the asset library | Assets deduplicate. Check what is already stored, and which designs use it, before uploading or replacing anything. |
| 2. Upload assets | A render variant or issuer design can only reference a URI that exists, so upload comes before variants. |
| 3. Serve and remove assets | Check the public URL before a credential depends on it, and delete only once nothing references the asset. |
Two APIs, one store
The credential-design API exposes design-scoped asset operations (tenant asset upload, per-design
locale slots, public hash URLs). The asset API exposes the tenant library by namespace (design for
credential design, brand for theming) and is the only API with a delete. Both store content-addressed
bytes; use the design API when attaching to a design and the asset API to manage the library.
Deeper reference
Assets has the captured
uploads from 11 Credential Designs. Design assets
describes the per-design slots.
Next journey
Continue with Build render variants.