CEDX Files · Platform
Three hundred twenty files and 120 share links in the demo workspace, and the console counts what file tools usually leave for the incident review: 46 links open to anyone, 99 files untouched in 90 days, and classification labels on only 63% of the library.
The finding that writes the page: a Confidential archive reachable through an anyone-link, no sign-in required. The console found it; nothing else was going to.
Runs on demo data. Northline shared files in the captures is the software's demo workspace, not a customer.
What it is
All files as one table: type, folder, share class, opens, size, idle days and owner on every row. The AI column is honest about its scope — 79 files processed, summary and Q&A ready, marked with a chip — and the stale and external counts are header cards, not filters you have to build.
Forty-eight team spaces with members, files, size, external-link count, policy and classification per row. The folders that matter sort themselves: a Confidential archive with 19 external links under an External OK policy is visible in the same glance as a Restricted folder with 10.
The links table shows type, opens, recipients, expiry and status per link — Anyone, Org or Named. The never in orange is the governance: most of the active links have no expiry at all, and the expired-and-revoked tab keeps the other 15 of the 120 on record.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/files.
01 — Overview
The health ring is blunt: 25%, driven by 46 open anyone-links, 99 stale files and 63% label coverage. The alerts are root-caused — the Confidential archive on a public link is named with its file, its class and its share type.
02 — All files
Three hundred twenty rows where opens, idle days and share class sit next to the filename. Sorting by opens puts a 420-open brief beside a 251-open zip on an anyone-link — popularity and exposure in one view.
03 — Folders
Folder rows carry the controls: a Board folder with 49 files and 15 external links, an Events folder at 23.4 GB, each with policy and class attached. External OK is a deliberate state — you can see which folders chose it.
04 — Shares
One hundred five active links with opens, recipients and expiry. An onboarding PDF opened 90 times through 120 recipients with no expiry is a different object from a named link expiring in September — and the table shows both.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns classification: 63% coverage today, and the 99 files idle 90 days or more that pollute search and storage alike.
stale files · 99
Owns the anyone-link queue — 46 open, one on a Confidential archive — and the never-expiring links the orange text keeps asking about.
anyone-links · 46
Owns the plan arithmetic: 18 GB of 500 GB used, 18K AI units of the 25K monthly plan, and the folders growing past 40 GB.
storage · 18 GBThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
A file arrives in a folder that already has a policy and a class — the boundary exists before the content does.
Classification coverage climbs toward 100%: 63% today, with the unlabelled share visible rather than assumed.
Links go out with a type and an expiry — or they do not, and the never shows in orange until someone owns it.
Ninety days without a touch makes a file stale; 99 of them are counted, so cleanup is a list, not a project.
One record
Files is where the estate's documents live — found by search, cited by the assistant, kept honest by audit.
The library is an index away from being findable — classification and staleness here are ranking signals there.
CEDX KnowledgeThe 79 AI-processed files — summary and Q&A ready — are the raw material a knowledge corpus is built from.
CEDX DriveDay-to-day sharing lives in Drive; the governance surface on this page is what watches it.
CEDX AuditExternal shares and anyone-links are exactly the events an audit trail exists to reconstruct.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your library, your policies
Files with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/files. It runs on demo data, which the page says next to the figures rather than in a footnote.
A share link that opens without sign-in. The demo workspace has 46 of them active, and the Overview alert that matters is one such link on a Confidential archive — reachable by anyone holding the URL. The console counts and exposes them; what you then revoke is your call.
Every link carries an expiry date or the word never, rendered in orange. Most of the 105 active links in the demo have no expiry — which is exactly the governance gap the column exists to make visible. Expired and revoked links stay on record under their own tab.
Scoped on the screen: 79 files have been processed for summary and Q&A, marked with an AI chip on the row, metered against an 18K-of-25K monthly units card. Nothing broader is claimed.
Ninety days without activity. The demo library has 99 of them, counted on the Overview header, because stale files pollute search results and storage budgets alike.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask how many anyone-links are open in your own file estate.