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. Search render variants' logo and backgroundImage URIs to see which cards use an asset. |
| 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; delete only unused brand library assets. |
Uploads and deletes need the tenant-admin role (or platform-admin for an operator). Reads need a token for the enterprise-blob audience.
Two APIs, two stores
Credential design assets go through the credential-design API: tenant upload, per-design upload,
list, and the public URL /public/assets/design/{hash}.{ext}. The asset API is the tenant library for
theming and branding (namespace brand), and its public URL is
/public/assets/{tenantId}/brand/{hash}.{ext}. The two stores are separate. The asset API's delete
does not remove credential design assets, and the credential-design API has no delete.
Deeper reference
Assets has the captured asset uploads. Design assets describes the per-design slots.
Next journey
Continue with Build render variants.