Skip to content

Zircon CRM / Marketing & brand

Runs in the browser · HU / EN / DE

Digital asset management where the link stays when the file changes

The media library in Zircon CRM keeps your company's logos, photos, documents and videos in one place, in folders and with tags. Every file gets a permanent, readable link that always serves the latest version, so nobody has to hunt down old links after a logo refresh. The same link delivers each image in the size you need.

Permanent, readable linksImage sizes set in the URLVersions you can restore

In short

What is the Zircon CRM media library for?

Digital asset management (DAM) is a central, searchable home for brand assets and documents. The Zircon CRM media library is a DAM: each file gets a permanent link that serves the current version after every replacement, images are resized and converted through link parameters, and earlier versions are kept. It is built for marketing and web teams and their own brand assets.

Sound familiar?

The logo lives in four folders, and all four are out of date.

If two of these ring true, your brand assets are still scattered.

  1. 01

    The old logo is still live after the rebrand

    The website header, three e-mail templates and the price list still show last year's logo, because each one points to a different file.

  2. 02

    Every size is exported by hand

    The newsletter needs 600 pixels, the social share card 1200 × 630, the website a retina size. Someone exports each one separately and starts again at the next change.

  3. 03

    The confidential price list sits on a public link

    A document sent to a partner still opens on the same link months later, and nobody knows who is looking at it.

  4. 04

    Nobody knows which version is right

    The shared drive holds "logo_final" and "logo_final2", and someone is using both.

What it does

What the Zircon CRM media library does.

One upload, one permanent link, and as many sizes and versions as you need.

Permanent, readable links

Every file gets a short, readable address such as …/dam/logo. It does not change when you upload a new version, edit the details or move the file to another folder. After a rename, the old address keeps answering too.

Versions you can restore

Upload the new file onto the existing asset and the earlier versions stay. A restored version is added as the newest one, so the history is never rewritten, and a link pinned to one version never changes.

Resizing in the link

Width, height, fit mode, quality and a retina factor can all be set through link parameters. Five presets come ready: thumbnail, a 600-pixel e-mail image and its retina twin, a 1200 × 630 social card and an avatar. When cropping, the focal point you mark, such as a face or a product, stays in the picture at every size.

WebP when it really is smaller

Browsers that accept WebP get WebP, but only when it is smaller than the original. Outlook for Windows and other clients that cannot show WebP get the original format. Each size is generated once and then served from the cache.

Private files and expiring links

An internal document can be set to private: only signed-in staff can open it, plus anyone with a temporary link valid for 1 hour, 1 day, 7 days or 30 days. Everyone else gets "not found", so the library does not even confirm that the file exists.

Embedding without writing code

On the sharing tab you pick a size and format with a live preview, then copy the URL, e-mail-safe HTML, retina-ready HTML for websites or Markdown.

Image picker in the text editor

In the editor for e-mail templates and knowledge base articles, the browse button opens the media library. Set the width, retina and alt text, then insert the image.

Its own REST API and AI access

The media library has its own REST API with its own keys and read, upload and delete permissions, so a website build can publish its images. Over MCP, an AI assistant searches, uploads and organises assets with the staff member's permissions.

How it works

A logo refresh in digital asset management, with no link changes.

  1. 01

    Open the logo

    In the media library, open the brand folder and click the asset called logo.

  2. 02

    Upload the new version

    Drop the new file onto the Versions tab and add a note, for example "2026 brand refresh".

  3. 03

    The link serves the new file everywhere

    From now on, …/dam/logo shows the new logo in the website header, the e-mail templates and the documents. The e-mail and social sizes are generated again on their next request.

  4. 04

    Roll back if something looks wrong

    Make the previous version current again. The old logo comes back as a new version, and the full history is kept.

Control

Who can upload, delete and see what.

Five separate permissions

View, upload and create folders, edit and replace, delete and manage the trash, and settings and API keys. You grant them per role or per staff member.

Thirty days in the trash

A deleted file goes to the trash, and its link stops working while it is there. By default it is deleted for good after 30 days; when restored, it comes back with its old name and link.

Security filters

Executable and script files can never be allowed, the library checks each file's real content, and scripts are stripped from SVG files. Uploads, replacements, moves and deletions are written to the activity log.

Presets only for outsiders

You can make visitors who are not signed in use presets only. That way nobody can fill the disk with renditions in arbitrary sizes.

Honestly

Good to know before you start.

  • WebP and AVIF output depend on the server's image libraries; rasterising SVG and handling TIFF and HEIC need ImageMagick. The settings show what your server supports.

  • Emptying the trash automatically needs the scheduled job (cron) running on the server.

  • The upload limit is 50 MB per file by default and can be raised only up to the server's own limit.

  • The media library sends no e-mails or notifications and has no customer portal screens. It is the home for your own brand's files.

Before you write

Fair questions. Straight answers.

  1. 01

    What happens to old links when we upload a new logo to the Zircon CRM media library?

    Nothing breaks: the same link now serves the new version on the website, in e-mails and in documents. The previous version is kept, and when a link must never change, Zircon CRM also gives you a link pinned to one version.

  2. 02

    Does every browser get WebP from the Zircon CRM media library?

    Only browsers that accept it, and only when the WebP file really is smaller than the original. Outlook for Windows and similar clients get the original format. Whether your server can produce WebP and AVIF depends on its image libraries, and the Zircon CRM settings show you which.

  3. 03

    How do we share a confidential document with an expiry date from Zircon CRM?

    Set the file to private in the media library and create a temporary link for 1 hour, 1 day, 7 days or 30 days. After that the link stops working, and the plain address still answers "not found" to outsiders.

  4. 04

    Can our website build upload its images to the Zircon CRM media library?

    Yes, through the media library's own REST API, with a key that has read and upload permissions. The upsert call either creates the asset or adds a new version to the existing one, and the version history shows the key's name.

  5. 05

    Can the Zircon CRM media library serve files from our own domain or a CDN?

    Yes: set a public base URL and every generated link uses it. The domain or CDN must forward requests to Zircon CRM. If the CDN does not tell WebP requests apart, give e-mail images a fixed format so Outlook can display them.

Let's talk.

The first call costs nothing
A human replies — not a bot

Bring one logo and an e-mail template that uses it. In the demo we upload it to the media library, add a new version and show the image updating in the template without touching the link.

Hours
Weekdays 9–17
Support
support@zircon.hu (existing clients)