Asset Management Center

The Asset Management Center (AMC) is the single place to upload, preview, share, and manage every kind of asset that appears across your QuickBox Pro dashboard. It is organized into categories — Local Assets (your upload library and personal storage), Brand Assets (the instance branding slots), Application Logos (the icon shown for each application), Avatars (profile pictures), and Application Backups (config backups of your installed apps) — with a segmented switcher at the top of the page to move between them.

Who can access it

The categories you see depend on your account level and permissions — access is governed by who you are, not by which tool you use:

If you have access to only one category, the page opens straight to it with no switcher. Within each category, individual actions are governed by the relevant permission described in that section.

The categories

Key features

Local Assets

Local Assets is your upload library. It is the default category when you open the Asset Management Center.

Uploading assets

Click the upload button or drag files onto the upload zone. A broad range of file types is accepted, and each previews differently:

File types are detected from the actual file contents — renaming a file’s extension does not change how the server treats it.

Browsing and managing assets

Assets display in a grid or list view with search and type filters. Each item shows a preview thumbnail (for images), file name, file size, and upload date. Your view choice (grid or list) is remembered. From the browser you can:

• View — Click an asset (or press Enter/Space when it is focused) to open the full-screen viewer
• Edit — Update the asset’s name and alt text
• Share — Create a public share link or send the asset to another user
• Set as brand asset — Promote an image into a branding slot (administrators with branding permission)
• Delete — Remove the asset after confirmation

Personal storage

When you upload to Local Assets as a managed user (someone with the media.library.use permission who is not an administrator), your files are stored in your own home directory on the server — not in a shared dashboard area.

This has a few practical consequences worth knowing:

• A storage usage bar at the top of your library shows how much of your disk quota you are using. It turns red as you approach the limit
• SFTP and the dashboard stay in sync — drop a supported file into your ~/.QuickBox/storage/ folder over SFTP and it appears in the Asset Management Center the next time you open it; delete one over SFTP and it disappears from the library
• There is no separate media quota for personal storage — it is your ordinary disk quota. If you are out of disk space, the upload is rejected with a clear message

Administrators uploading from the Local Assets category instead store files in the central dashboard area by default. Administrators see an extra System vs Personal chooser at upload time to pick where a file goes.

The full-screen viewer

Clicking an asset opens it in a full-screen viewer that overlays the dashboard. The viewer navigates through the assets currently shown in the browser, in the same order.

Zoom and pan (images)

• Scroll wheel — Zoom toward the cursor position
• Pinch — Zoom on touch devices
• Double-click / double-tap — Toggle between fitted and 2x zoom
• Drag — Pan around the image while zoomed
• Zoom buttons — On-screen controls for zooming in, out, and resetting

Zoom ranges from fit-to-screen up to 4x. Zoom resets automatically when you move to another asset.

Gallery navigation

• Arrow keys or the on-screen chevrons move between assets
• A counter in the header shows your position (for example, “3 of 12”)
• On touch devices, swipe left or right to change assets while at the fitted zoom level
• Esc resets the zoom if you are zoomed in; pressing it again closes the viewer

Non-image files

• PDFs render in an inline preview pane with a download fallback if your browser cannot display them
• Video plays inline in a themed player with play/pause, a scrubber, volume, playback rate, and fullscreen. A short “Preparing this video…” state may appear while the file is made ready to stream
• Audio plays inline in the same themed player with an art plate
• CSV files render as a table (large files are truncated with a note)
• Text, Markdown, and log files render inline — Markdown is formatted, everything else shows as plain monospaced text
• Office documents (DOC, DOCX, XLSX, PPTX) cannot preview inline and show a download card

A Download button is always available in the viewer header regardless of file type.

Per-asset access stats

Every asset card has a small bar-chart icon that opens an access-stats popover for that asset. It is hidden while you are multi-selecting assets, and you only see stats for assets you own (administrators can see any asset’s stats).

The popover shows:

• Views, Downloads, and Viewers (unique viewers) as three counters
• Last viewed as a relative time, with the exact timestamp on hover
• A 14-day views sparkline so you can see the recent trend at a glance
• A short Recent viewers list

An asset that has never been viewed shows an empty state instead of zeros.

Sharing

Each asset can be shared two ways from the Share action — a public link, or a direct share to another user on the same server. A toggle at the top of the share dialog switches between the two modes.

Public share links

A public share link gives anyone access to a file through a URL — no dashboard account required. Visitors see a branded viewer page: images display inline, PDFs render in a sandboxed frame, and video and audio play in a full themed player — play/pause, a scrubber, volume and mute, playback rate, and fullscreen for video (audio shows a “now playing” art plate). A download button is always available, and anything that cannot play falls back to a download card.

1. Pick an expiry — Presets for 1 day, 7 days (the default), or 30 days; Custom for an exact number of hours or days; or Never for a permanent link
2. Optional advanced settings — Set a maximum number of accesses (the link stops working once the cap is reached) and a label to identify the link later
3. Create — The dialog shows the full link with a Copy button

Permanent links are highlighted in the dialog as a deliberate choice — they keep working until you revoke them.

The share page is whitelabel-branded

The public viewer page carries your site’s branding, not QuickBox branding — your configured site name and logo in the header, and it follows your dashboard theme. Visitors see only the shared file and your branding, nothing about your dashboard or other assets.

Sharing directly to a user

Switch the share dialog to Specific user mode, search for a user on your server by username or email, and share the asset to them. They receive an in-app notification with a link to the asset. A direct share has the same expiry options as a public link but no access cap — a personal share should not exhaust itself.

Emailing a share link

After creating a public link, you can email it directly to a recipient from the same dialog. Email delivery requires:

• The share link email toggle to be enabled (it is on by default — see Share settings below)
• A Web Root configured in General Settings, so the emailed link points at your server’s public address

The recipient receives a branded email with the link and its expiration details.

Link states

Every link for an asset appears in the share dialog’s link list with a status chip:

Dead links remain visible in the list (dimmed) so you have a record of what was shared, including each link’s access count.

Revoking a link

Click Revoke on an active link and confirm. Revocation takes effect immediately — anyone holding the URL gets a generic “no longer available” page from that moment on.

What visitors see — and what they don’t

• The public page shows only the shared file and your server’s branding — nothing about your dashboard or other assets
• Viewing the share page does not count against an access limit; only downloads count
• Expired, revoked, and exhausted links all show the same generic “no longer available” page — visitors are never told why a link stopped working
• Unknown or mistyped links get a plain not-found page, and repeated guessing attempts are rate limited
• Shared SVG files download instead of displaying in the browser — SVG files can contain embedded scripts, so serving them as downloads keeps anything inside them from running

Share settings

The gear icon in the Local Assets header opens the share settings, where you can toggle email delivery for share links on or off server-wide. The toggle is on by default; turning it off disables the email option in every share dialog without affecting existing links.

Brand Assets

The Brand Assets category manages the instance branding slots and shows whether each one uses a custom or default image:

• Collapsed Logo and Full Logo — the sidebar and login page logos
• Favicon — the browser tab icon
• Default Avatar and Default Banner — fallback profile images
• Email Logo (Full) and Email Logo (Icon) — logos used in outgoing email

Uploading a brand asset

Each slot has a drag-and-drop uploader with a built-in cropper — drop an image, crop it to the slot’s shape, and it applies instance-wide immediately. There is no longer any need to type a file path. You can also promote an image you have already uploaded: open Local Assets, click the crown icon (“Set as brand asset”) on any image, then pick the slot.

The two Email Logo slots have no bundled default, so an empty one is labeled “Not set” rather than “Default.”

Brand assets can also be uploaded from the Branding section of General Settings and the Email Settings → Advanced panel — these use the same branding slots, so changes are consistent wherever you make them.

Application Logos

The Application Logos category is a searchable gallery of every application’s logo — the icon shown for that app throughout the dashboard. Each tile displays the app’s current logo, its name, and a badge marking whether the logo is custom or default.

By default, an application uses the bundled logo that ships with QuickBox Pro. A custom badge means an administrator has set an override for that app.

Replacing an application logo

Click the Replace logo action on an app tile to open the replace dialog, where you can drag and drop an image and crop it to set the app’s logo, or Reset to default to remove an existing override and fall back to the bundled logo.

Setting a logo here writes the application’s brand-icon override — the same override used by the App Templates editor. The gallery updates to show the new logo with a custom badge.

Avatars

What the Avatars category shows depends on your account.

Your avatar history (everyone)

A managed user sees their own avatar collection — a history of every avatar they have uploaded. Uploading a new avatar does not discard the old one: the previous picture is kept, and you can switch back to it at any time.

• Upload — Drag and drop or pick an image, crop it, and it becomes your active avatar
• Set active — Make any earlier avatar in your collection the active one again
• Delete — Remove an avatar you no longer want from your own collection

The currently active avatar is marked with a badge and a highlighted ring.

Avatar moderation (administrators)

Administrators instead see an admin gallery of every user’s avatar, used for moderation. Each tile shows the user’s avatar, their username, and a custom-vs-default badge. The gallery supports search and pages through the full user list.

For moderation, an administrator can reset a user’s avatar to the default. Click the reset action on a user’s tile and confirm — the avatar is replaced with the default image and the uploaded file is removed.

Application Backups

The Application Backups category lets you back up the configuration of your installed applications from the same hub — no terminal needed. It is shown to administrators and to non-admin users with the media.library.use permission; you only see backups for applications you own (administrators see standard users’ backups as well).

How backups work

The backup engine is the QuickBox Pro CLI — the dashboard hands the request to it and then lists the real backup files it produced. Creating a backup runs as a background job: you start it, and the new file appears in the list when it finishes, so a large backup never times out in the browser.

You can create three kinds of backup:

Managing backups

Each backup in the list shows its real on-disk filename and the time it was created. From the list you can download a backup, and — depending on your permissions — delete one. Backup files live under your home directory, in ~/.QuickBox/software/<app>/backup/.

Storage quotas

There are two distinct storage limits, depending on where a file lives:

• Personal storage (a managed user’s uploads in ~/.QuickBox/storage/) counts against the user’s ordinary disk quota on the server’s filesystem — the same quota that governs all of their files
• Central storage (administrator uploads to the shared dashboard area) is governed by a per-user media library quota with its own inheritance chain

The media library quota resolves in this order:

1. Per-user override — An explicit quota set for that user wins over everything else
2. Group default — The highest quota among the user’s groups that define one
3. Instance default — The server-wide fallback (5 GB unless changed)

Media library quotas are managed from two places:

• Per-user — In User Admin, expand a user row to see their effective quota, where it comes from (override, group, or default), and current usage
• Per-group — In the group editor, set an optional default media quota that applies to all members without an explicit override

Media permissions

Three permissions control which accounts can use media features. Grant them per group (all members inherit) or override them per user:

A user’s effective permission resolves in this order:

1. Administrator accounts are always granted every media permission
2. A per-user override is final — an explicit Deny beats any group grant, and an explicit Allow beats the default
3. Any group grant — if any of the user’s groups grants the permission, the user has it
4. Default — denied

Per-user overrides are set in User Admin (expand a user row), where each permission shows its current state and source — for example, “via group Media Team” or “override”. Group grants are set in the group editor.

Where files live

Files are stored in different places depending on who uploaded them and which category they belong to:

Both locations survive dashboard updates. Personal uploads stay in your home directory; central uploads live in the persistent dashboard data directory.

Best practices

FAQ

Related pages