Changelog

A small SEO improvement for libraries that use supersede chains.

One document, one ranking

When you mark a document as superseded, its old page stays visible with the "superseded by" notice — but search engines used to treat old and new as competing pages. The old page now declares the current version as its canonical URL, so Google and AI answer engines consolidate ranking signal onto the live document instead of splitting it across every version you've ever published. If the newer version is restricted, public pages don't point at it.

Fixes & improvements

• The plugin description on wordpress.org now opens with a plain one-sentence definition of what FileDeck is.

A focused fix for sites using lead capture together with multi-select zip downloads.

One form, whole selection

With lead capture on, clicking Download selected as zip now opens the same "enter your details" form as a single download — and one submission covers the whole selection, so your visitors aren't asked once per file. Previously the zip request was refused outright (every document in it required a lead that was never collected) and the button failed without saying anything.

Fixes & improvements

• If a zip download does fail, the button now tells you — "Download failed — try again" — instead of failing silently.
• Bulk leads are recorded like any other lead, so nothing is lost from your lead list when visitors download in bulk.

FileDeck 2.12.0 adds client areas to Pro: assign people to a category and it becomes their private portal — the biggest new capability since cloud storage.

Per-client document portals

On any document category, enter your client's usernames or email addresses and that category becomes their space: only they (and site managers) can see it — in libraries, search, downloads, single pages, even WordPress' own APIs and sitemaps. An accountancy's per-client folders, an agency's deliverables, a consultancy's project rooms — one library, privately partitioned.

Client-area documents don't appear as padlocked rows in public libraries the way role- or password-restricted documents do. They're simply not there. A client's document titles are themselves private, so outsiders see nothing at all.

The "Your documents" page

Drop the new [filedeck_my_documents] shortcode on a page and every client who logs in sees just their own spaces — each area as a section with its name, description and library. Add uploads="1" and each area gains a Send us a document form: files clients send land in your moderation queue, never published until you approve them.

They hear about it before they ask

When you publish a document into a client area, its assigned people are emailed automatically — with the document name, the area, and a link. No more "I've uploaded it, go look" emails.

Fixes & improvements

• Client-area restrictions stack with role and password rules on the same category, and files vault automatically like any other restricted document.
• Everything composes: versions, review cycles, expiry, acknowledgments and (on the AI tier) per-recipient watermarking all work inside client areas.

FileDeck 2.11.0 adds two protection features to the AI tier, built for the documents you'd rather not see forwarded: dynamic PDF watermarking and view-only mode.

Dynamic PDF watermarking

Turn on one switch and every PDF FileDeck serves is stamped — at the moment of download — with a footer naming who received it, from your site, and when. Board packs, salary reviews, draft contracts: if a copy ever turns up where it shouldn't, the copy itself says whose it was. The stamp applies to single downloads, every PDF inside a zip, and view-only streams, so there's no unstamped side door. Logged-in users are named by email; visitors get the site and time only — FileDeck doesn't put IP addresses in documents.

We frame this honestly: a watermark is deterrence and provenance, not DRM. It doesn't make copying impossible — it makes every copy attributable, and that changes how people treat a document. If your server can't stamp (Ghostscript missing), FileDeck serves the original and logs it — protection never becomes an outage.

View-only documents

Some documents should be read, not kept. Tick View-only on a document and visitors read it in the browser — while the download button, zip inclusion and the raw file URL are all switched off (the file moves into the protected vault automatically). The library shows a View button that opens in a new tab; access rules and lead capture still apply. Signed share links you mint still download, by design.

Pair the two: a view-only document with watermarking on means what's on the visitor's screen already carries their name.

Fixes & improvements

• The activity log records view-only reads as view events and any watermark failure as watermark_fail, so both are auditable.
• Developers: new extension points on the serve path (filedeck_serve_path, filedeck_zip_entry_path, filedeck_force_stream, filedeck_doc_row) and watermark customisation filters (filedeck_watermark_text, filedeck_gs_path).

FileDeck 2.10.0 puts you in charge of what happens when someone clicks Download: whether the file saves or opens, who gets told about it, and how many downloads a person gets per day.

Force download or open in browser — per document, free

Until now, what happened after the click was up to each visitor's browser: PDFs usually opened in a tab, Office files usually saved, and no two setups behaved alike. Every document now has a Delivery setting — *force download* or *open in browser* — so the behaviour is yours to decide and identical for every visitor. "Open in browser" documents get a View button that opens in a new tab, so readers never lose their place in the library. Included in the free plugin.

Per-download notifications (Pro)

Know the moment a document is downloaded. Turn on notifications in Documents → Settings → Downloads and FileDeck sends an email (to any addresses you list) and/or a JSON webhook per download — including each file inside a zip selection. Point the webhook at Slack, Zapier or Make and download events flow straight into your tools. Emails are sensibly flood-capped; the webhook never slows the download itself.

Daily download quotas (Pro)

Give each user role — and logged-out visitors — a daily download ceiling. It's a fairness rule for members' areas and an anti-scraping brake for public libraries: over the limit, visitors get a polite "resets tomorrow" message. Zip downloads count per file so they can't sidestep the limit, and signed share links you mint stay exempt.

Fixes & improvements

• Documents set to "open in browser" are streamed with the correct headers even when they're in the protected vault, so the setting works for restricted files too.
• Developers: a new filedeck_downloaded action fires once per counted download, and the filedeck_download_allowed filter is the final allow/deny gate on every download and zip entry.

Following the table refresh, the AI chat box got the same treatment. Same questions, same grounded answers — it just looks and behaves a touch more polished.

A header that says what the box is

The Ask box now opens with an AI mark and a subline — "Answers come from 66 documents, with sources" — so visitors know exactly what they're talking to and where its answers come from before they type a word.

Citations that look like citations

Source chips under each answer now carry a small document icon, sit under a divider, and tidy up long document titles with an ellipsis. Answers the AI couldn't ground in your library render as an outlined bubble, and errors get a red tint — you can read an answer's trustworthiness at a glance.

Fixes & improvements

• Messages ease in with a subtle animation, which switches itself off if your device asks for reduced motion.
• The send button now stays dimmed until a question reaches the three-character minimum, instead of accepting a click and silently doing nothing.
• A cleaner send icon, visible keyboard-focus outlines throughout the box, and corner styling that matches the refreshed document table.

The table layout got a design pass. Same columns, same settings, same shortcode — your library just looks a lot more polished, with no action needed on your part.

The table is now a self-contained card

The search box, filters, and document count sit in a header strip at the top of a bordered, rounded card, with pagination in a footer. Column headers are compact and stay pinned to the top of the screen while you scroll a long library, and the search box gained a proper magnifier icon.

Clearer rows at a glance

Document titles now lead each row in bold, categories render as quiet pill tags instead of underlined links, and the Download button is outlined at rest — filling in on hover — so a 100-row library no longer reads as a wall of solid blue buttons. Preview and Download picked up crisp inline icons that render identically on every device (goodbye, eye emoji).

Fixes & improvements

• The document count now reads "66 documents", switching to "12 of 66" while a search or filter is active, instead of the cryptic "66 / 66".
• Keyboard users get a visible focus outline on every link, button, and filter.
• Multi-select checkboxes follow your accent color.
• The default accent is now FileDeck blue. If you've set a custom accent color in Settings or on a block, nothing changes — your color still wins.

A maintenance release. We ran a full security review across FileDeck and its supporting infrastructure, and this ships the resulting hardening along with a handful of reliability fixes. We'd encourage updating at your earliest convenience.

Fixes & improvements

• Security and reliability improvements.
• Saving settings no longer cleared your AI and chat provider keys on sites that pin the OCR key with a constant or environment variable.
• Indexing a very large or heavily compressed Office document no longer stalls the search index rebuild for the rest of your library.

Two small touches that make a library quicker to scan — an icon that matches each file's type, and a folder icon you can choose per category.

File-type icons on download buttons

If your download links use the icon or button with icon style, the icon now reflects the document's file type — a distinct mark for PDFs, Word documents, spreadsheets, presentations, archives, and images, with a plain document icon for everything else. Nothing to set up: pick the link style under Documents → Settings → Display and each button shows the right icon automatically.

A folder icon for each category

In the folder layout, every category can carry its own icon instead of the plain folder — a book, a briefcase, scales for legal, a clipboard for forms, a chart for reports, and more. Edit a category under Documents → Document Categories, pick a Folder icon from the built-in set, and save. Categories you leave on Default keep the standard folder icon, so nothing changes until you choose one.

Fixes & improvements

• The icons come from a small built-in set — no uploads to manage — and are decorative only, so screen readers still read each download's label and each folder's category name.

Search shows instant matches the moment you type, then keeps looking inside your documents' contents (and, on the AI plan, by meaning) a beat later. That second wave of results used to appear with no warning, which could look like the list was jumping on its own. Now a small spinner in the search box tells you when a deeper search is still running.

A spinner while the deeper search runs

The instant results still appear right away. While FileDeck keeps searching — inside file contents, or semantically on the AI plan — a subtle spinner shows in the search field and clears the moment those extra matches land. So a growing result list now reads as "still working," not "something glitched."

It applies everywhere: quick libraries that filter in the browser, and large libraries that fetch each page from the server.

Fixes & improvements

• The document search box now shows a progress spinner while a content or semantic search is still resolving, so late-arriving matches no longer look like an unexplained jump in the results.
• The spinner respects your system's reduced-motion setting and announces its busy state to screen readers.

The Documents menu just got shorter. The Search Index and AI Index screens are now tabs inside FileDeck → Settings, so everything you configure lives in one place instead of scattered across the menu.

Search Index and AI Index are now Settings tabs

Open Documents → Settings and you'll find Search Index and AI Index alongside the other tabs. Every control is exactly where it was — rebuild the content index, watch background progress, send scanned PDFs for OCR, or rebuild your AI embeddings — just reached from a tab now rather than its own menu item.

Fixes & improvements

• Trimmed the Documents menu by folding the two index screens into Settings, so the sidebar is shorter and the index tools sit next to the settings they use.

The front-end submission form got more capable and easier to protect, and all three front-end tools are now blocks you can drop in without touching a shortcode.

Submit several files at once

The [filedeck_submit] form now accepts more than one file in a single go — each file becomes its own document, sharing the title, category and fields you enter. Handy for a supplier sending a batch, or a team member uploading a set of related documents.

Keep bots out, without a plugin

If you open submissions to logged-out visitors, you can now turn on Cloudflare Turnstile — a free, cookieless CAPTCHA — right in Settings → Submissions. Paste your Turnstile keys and the form shows the challenge and verifies it on submit. A hidden honeypot and a per-visitor rate limit are always on, and there's a hook for virus-scanning uploads if your host offers it.

Blocks for submit, my submissions, and edit

The three front-end tools — Submit Document, My Submissions, and Edit Document — are now Gutenberg blocks, so you can add them from the block inserter with a live preview and simple settings instead of typing shortcodes.

Fixes & improvements

• Multi-select custom-field filters now show live per-value counts on large libraries, matching how they already worked on smaller ones.

Contributors can now add and fix documents entirely from the front of your site. Add a submission form, show people their own submissions, and let them edit them — all with the moderation, versioning and access rules you already rely on.

A submission form, with moderation

Drop [filedeck_submit] on a page and visitors can add a document: title, description, category, file, and any custom fields you've defined. Everything arrives as Awaiting review in your Documents list — nothing goes live until you approve it. You can require a consent checkbox, fix submissions to one category, and reviewers get an email when something comes in. There's a hidden honeypot and a per-visitor rate limit built in, plus a hook for a CAPTCHA plugin if you open submissions to logged-out visitors.

"My submissions" and front-end editing

[filedeck_my_submissions] gives each person a list of their own documents with their status, and — pointed at an edit page — a link to fix them. [filedeck_edit] is that edit page: a pre-filled form for the title, description, category, custom fields, and the file. Replacing the file keeps the previous version (restore it any time from Version History) and re-applies file protection automatically. People can edit their own documents while they're still in review, but published documents stay locked to your team — so approved files don't change under you.

Fixes & improvements

• Submitted documents now carry any custom fields filled in on the form.
• Replacing a file from the front end archives the old version, exactly like replacing it in wp-admin does.

Your library can now hold whatever information your documents actually have — department, policy number, publication date, owner, jurisdiction, status — and your visitors can filter by any of it. Define the fields once; every document gets them, and any library can show and filter on them.

Build your own fields

Under Documents → Fields, add the fields your library needs. Each one can be text, a number, a date, a dropdown, a multi-select, a URL, a user, or a simple yes/no — and you can limit a field to certain categories, so a "Policy number" only appears on policies. Fill them in right on the document editor, or in bulk from a spreadsheet: every field is a cf:<key> column in CSV import and export. Already using Advanced Custom Fields? FileDeck reads your ACF values directly, and can import your ACF field groups in one click.

Show them as columns, filter by them with counts

Add any field to a library as a column — dates and numbers sort by value, not alphabetically. Mark a field filterable and it becomes a filter in the library: dropdowns show a live count next to each value ("Finance (12)"), and date and number fields get a min/max range. Filters combine, the counts update as you narrow, and the current view is saved in the URL so it can be bookmarked or shared. On large libraries the filtering and counts run on the server, so they stay fast however many documents you have.

Fixes & improvements

• Custom-field columns now sort by their real value in large (server-mode) libraries, not just small ones.
• A document’s custom-field values are matched by the library search box when the field is marked searchable.

If your library is big enough to run in server mode — around 500 documents and up — a search could leave matches out and tell you a result count that was too low. Both are fixed. Nothing to change; it applies to every large library automatically.

Every match counts, and the count is honest

Two different limits used to apply to a single search. Matches on a document's contents stopped at 500, while matches on titles, categories and tags ran to 2,000. Because the tighter limit hit first, the results most likely to disappear were the ones from inside your documents — exactly what full-text search is for. Worse, when a limit was reached the total simply reported the capped number, so there was no sign anything was missing.

Now both kinds of match share one limit, so content is never dropped ahead of titles. When a search does reach the ceiling, the library says so rather than presenting a truncated list as the whole answer.

If you run a very large library and want a higher ceiling, the filedeck_server_search_limit filter raises it.

Fixes & improvements

• Searching a 500+ document library no longer omitted matches found inside document text while keeping title matches for the same term.
• A search that hit the internal result ceiling no longer reported the ceiling as the true number of matches.

Housekeeping for scanned-document OCR: a clear fair-use limit on the shared service, and the ability to configure it from the server so the endpoint and key can't be changed from the admin screen.

A fair-use limit you can count on

The managed OCR service is shared across sites, so it now processes up to 100 scanned documents per day for your site (each up to 40 pages). If you switch OCR on for a large backlog of scanned files, they're handled a batch at a time and the rest continue automatically over the following days — nothing is skipped or lost. Running your own OCR service removes the limit entirely.

Fixes & improvements

• The OCR Service URL and Site key can now be set on the server (via constants or environment variables); when they are, the settings fields show as read-only.
• The OCR Service URL is validated so a document can't be sent to an internal/reserved network address (security hardening).

The compliance feature we've been asked about since day one, on the AI plan: prove who has read your policies.

Assign, confirm, chase

Edit any document and tick the roles that need to read it under Read & confirm — optionally with a "confirm by" date. Anyone in those roles sees a one-click confirmation on the document page (a plain form — it works with JavaScript off), and a new [filedeck_acks] shortcode gives each person their own "still to confirm" list for your intranet homepage.

Documents → Acknowledgments is the chase list: every assigned document with who's confirmed and who hasn't, a "send reminders" button for the stragglers, and weekly reminder emails that go out automatically until everyone's done.

Evidence your auditor will accept

Every confirmation records who, when, and which version of the document they read. When a policy changes, hit "Require re-acknowledgment" — everyone shows as outstanding again, and the previous confirmations are kept, marked as superseded. The whole history exports to CSV, and each person's confirmations appear in WordPress's built-in personal-data export.

Safeguarding policies, health & safety procedures, HR handbooks — if you've ever chased signatures on a paper circulation slip, this replaces it.

A cleanup release: a batch of admin buttons that quietly stopped working after the 2.0 rename now work again, cloud-storage connection is restored, and a few more security corners are tightened.

Buttons that work again

After the 2.0 internal rename, several admin actions were pointing at the old address and silently did nothing. These are all working again: CSV export and the sample CSV, activity-log and content-gap exports, lead export, Run scan now on Library Health, Generate missing thumbnails, and Mark reviewed.

Cloud storage connection restored

The OAuth connect flow for Dropbox, Google Drive and OneDrive couldn't complete — its callback pointed at a stale address. Connecting your cloud storage now works end to end.

Fixes & improvements

• Zip downloads now honour lead capture — a multi-select zip no longer skips the "leave your details first" form that a single download requires.
• The ⌘K command palette no longer lists documents protected by a WordPress post password.
• CSV export returns only published documents for authors who can't edit other people's posts (no draft or private documents leak into the export).
• Category-password unlock gained a per-category daily failure cap on top of the existing per-IP throttle, to blunt distributed guessing.
• The optional OCR service was updated to a newer image library.

A maintenance release with security and reliability improvements across access control, credential storage, and the library health check. There's nothing you need to do — updating is enough, and your existing settings and provider keys carry over unchanged.

Security and reliability improvements

• Tightened the permissions required to publish documents through Bulk add and CSV import, so only roles that are meant to publish can.
• Provider API keys (AI and OCR) are now encrypted at rest, matching how your cloud-storage credentials are already stored. Existing keys keep working.
• Hardened the weekly broken-link health check against being pointed at internal addresses.

We recommend updating at your convenience.

A big round of improvements to FileDeck's AI (available on the AI plan). Answers are markedly more accurate, the Ask box is now a proper chat, and you can finally see what your visitors are asking — including the questions FileDeck couldn't answer.

Much sharper answers

We fixed an indexing bug that was quietly splitting every document into ~150 tiny fragments, which badly hurt relevance and often stopped Ask from finding content that was right there. With that fixed, semantic search and Ask return far better matches. After updating, rebuild your index once — Documents → Settings → AI → Rebuild (or wp filedeck embed --rebuild).

Ask is also more honest now: when a question is only loosely related to your library, it says so plainly instead of straining to answer from weak matches.

A familiar chat interface

"Ask this library" is now a real chat — message bubbles, a typing indicator, clickable example questions, and inline links to the source documents behind each answer. It's still zero-dependency vanilla JavaScript, so it stays fast and adds nothing to your page weight. You can seed the starter questions with a new attribute: prompts="How do I get a refund?|What's your warranty?".

See what your library gets asked

A new AI Questions tab in the Activity Log shows what visitors are actually asking — and, most usefully, the questions Ask couldn't answer. Each unanswered question comes with a one-click Create a document button, so the gap in your library becomes the next thing you write. Questions stay on your own server, carry no IP address, and are automatically pruned after 90 days. (Requires activity logging to be switched on.)

Fixes & improvements

• The Ask box could load without its settings on some themes (block themes especially), leaving it unresponsive — its configuration now travels with the widget, so it works wherever you place it.
• Ask answers now render bold text and bullet lists properly, instead of showing the raw ** and - markers.
• On desktop, the Ask box focuses its input when it scrolls into view (without jumping the page), and the example questions flow in a neat wrapping row.
• The Download button on single document pages could appear invisible on themes that didn't supply an accent colour — it now always has a visible style.
• The layout-picker cards in the setup wizard no longer render with a broken border.
• After choosing a file in the document editor, the "no file yet" notice and button label update immediately instead of waiting for a save.
• For developers: the Ask widget now dispatches a neutral filedeck:ask DOM event after each answer (question, outcome, sources) so you can wire your own analytics. The event fires in the visitor's browser and FileDeck transmits it nowhere — it's purely an extensibility hook for your own code.

A quality-of-life fix for Pro's full-text search on big libraries.

No more timeouts

"Rebuild search index" used to re-extract every document's text in one long request — fine at a few hundred documents, a timeout at a few thousand. It now runs in the background in small batches: click the button, get a "queued" confirmation, and leave the page. The Search Index screen shows live progress (refresh to update), and your visitors' search keeps working from the existing index the whole time.

If a batch is ever interrupted — a server restart, say — the rebuild picks up where it left off rather than starting over.

Libraries with thousands of documents now load as fast as small ones.

One page at a time, automatically

Until now, a library rendered every document into the page and paginated in your visitor's browser — fine at 200 documents, slow at 5,000. Past roughly 500 documents, FileDeck now renders the first page only and fetches search, filter, sort and pagination results from your server as your visitor needs them.

There's nothing to configure and nothing changes visually: it engages by itself on large libraries, and smaller libraries keep the instant, everything-in-page behavior they've always had.

Search works exactly the same

Searching a large library matches the same things it always has — titles, summaries, categories, tags, filenames and file types, accents ignored — and on Pro, matches inside your files' contents are included too.

Small print

• The folders layout is unchanged (it shows every category by design).
• On large libraries, sorting by Filename or Author isn't available; every other column sorts as before.
• Semantic (AI) matches aren't part of large-library search yet — that's coming.

A round of improvements to FileDeck's cloud storage connections — Amazon S3, Dropbox, Google Drive, and OneDrive.

See file sizes for cloud files

Files you browse and attach from a connected cloud account now show their size in your library and on the document page, exactly like files uploaded to WordPress. Previously a cloud-backed document listed no size; now the grid, table, and single-document view all show it.

Fixes & improvements

• Scheduled cloud pulls no longer occasionally add the same file to your library twice when a manual sync and the automatic hourly sync overlap.
• Security and reliability improvements across the cloud storage connections.

A fix for anyone browsing a document library on a phone.

One page at a time on mobile again

On phones, a table library set to paginate was showing every document in one long scroll instead of the current page — the responsive card layout was quietly overriding the paging. It now shows one page at a time on mobile, exactly as it already did on desktop, so long libraries are quick to scan and scroll again.

Fixes & improvements

• No change to your settings — your existing "documents per page" is simply respected on mobile now, the same as everywhere else.

A small housekeeping release for the WordPress admin: the Documents menu is shorter and better organised, so the screens you use daily are easier to reach.

Library Health now lives in Settings

The Library Health screen (Pro) has moved from its own menu item into a Health tab on Documents → Settings, alongside the rest of your configuration. Everything works exactly as before — run a scan, review missing files, broken links and never-downloaded documents — it just no longer takes up a slot in the sidebar. The weekly automatic scan and email digest are unchanged.

Fixes & improvements

• Activity Log moved to sit directly above Settings in the Documents menu, so content screens stay together at the top and tools live at the bottom.
• FileDeck admin screens now sign off with "FileDeck is made with ❤️ in London" in the footer.

This release makes adding documents a lot quicker and puts you in control of hover previews — plus a round of smaller fixes.

Add documents by dropping files in

Adding files used to assume you were writing a post. Now, Add New starts with an uploader: drag in one file or a whole batch, and FileDeck creates a document for each — title, type and size filled in for you. It's the fastest way to stand up a library from a folder of PDFs, and it's in the free version.

Hover previews are now yours to switch off

The little preview card that appears when you hover a document is handy, but not everyone wants it. There's now a Hover preview cards switch under Settings → Features so you can turn it off. It stays on by default.

Fixes & improvements

• Downloading a file from its own document page no longer asked you to "enter your details" a second time when lead capture was switched on.
• Dropdowns in the library (filters, sort) now match the site instead of flipping to a dark theme on some devices.
• The document preview lightbox is now off by default, so previews only appear where you've asked for them.
• The admin Settings screen is tidier: Display and Features now live in their own tabs, and other plugins' notices no longer crowd the page.
• Security and reliability improvements.

The new AI tier turns your document library into something you can talk to — answers you can trust, because every one is grounded in your own files.

Ask this library

Type a question in plain English — "what's our refund window?", "which form do new starters fill in?" — and FileDeck answers from the documents you've published, with a citation to each source so you can open the original in one click. It only ever draws on files the person asking is allowed to see, so a restricted document never leaks through an answer. Bring your own AI key and the content stays on your site.

Find documents by meaning, not just keywords

Search now understands what you mean, not only the words you typed. A search for "time off" will surface your "Annual Leave Policy" even though the words don't match. Open any document and you'll also see Related documents — the nearest things in your library, so people discover the form or policy that goes with the one they're reading.

Fixes & improvements

• Category links in the library now point at the real category archive, so they work when opened in a new tab or shared.
• Clearer wording throughout the AI setup screen about which key does what.
• Faster first paint on large libraries.
• Security and reliability improvements.

FileDeck 1.0 is here. Two headline features for organisations: search that reads the contents of your documents, and real protection for the ones that shouldn't be public.

Full-text search inside PDFs and Office files

Search no longer stops at the title. FileDeck Pro reads the text inside your PDFs, Word and Excel files and indexes it, so a search for a clause, a product code or a person's name finds the document that contains it — even if none of that appears in the title or tags. Scanned PDFs are handled too.

Protected files that are actually protected

Hiding a page never protected the file behind it — the raw URL still worked. Protected documents in Pro now move to a deny-all vault and stream only after FileDeck re-checks the visitor's permission, so a restricted file has no working public link by default. When you do need to share one, you can issue a signed link that expires on its own.

Fixes & improvements

• The library table now stacks neatly into cards on phones.
• Bulk actions in the admin let you recategorise many documents at once.
• Per-document QR codes for print-to-web hand-offs.
• Security and reliability improvements.