CEDX Drive · Workplace
Forty-eight shared drives, 360 items in view, 140 active shares — and 22 anyone-links with no expiry date, each one scored, click-counted and queued for a forced 14-day expiry.
Ask where the latest board pack is and the answer includes its location, its version — and the fact that it is shared on an anyone-link with no expiry at risk 94. The risk is part of the answer, not a separate report.
Runs on demo data. Files, drives and people named on screen belong to the demo workspace.
What it is
Every drive lists its manager, members, external count, storage, waste and policy — allowed, allowlist or restricted. Field ops runs 9.1 TB at 41% waste with 8 external members; legal holds runs restricted with none. Policy is a column, not a hope.
Files and folders carry sharing state, sensitivity, size, version count and days since access. A restricted folder on an anyone-link at 104 GB and a video master with 11 versions at 80 GB are exactly the rows this table exists to surface.
Every link and collaboration lists its role, external flag, expiry, risk and clicks. The board pack's anyone-view link has 420 clicks and risk 99 — heavily used, completely undated. That row is the argument for forced expiry, made by the data itself.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/drive.
01 — Overview
External open 91, high risk 77, governance health 53% against a target of risk under 40. The root-caused alerts name the patterns: anyone-links without expiry, partner pricing shared two ways at once, external members sitting on high-sensitivity drives.
02 — Shared drives
Marketing assets runs 44% waste on an allowed policy; training videos runs 23% on restricted. Eight drives sit above the 35% waste line — the archive queue starts there.
03 — Items
Sort by access age and the 366-day-old external share rises; sort by versions and the 11-version video master rises. Cold storage and version piles are the 2.8 TB the waste model wants back.
04 — Shares
The 22 no-expiry anyone-links are a filter, not an audit project. Revoke or expire the top twelve and the do-this-next queue scores the risk reduction at 92.
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 the drives fleet and the storage bill. The 2.8 TB reclaim queue — cold folders, version piles — is the quarter's easy win.
reclaimable · 2.8 TB
Works the no-expiry list and the external memberships on restricted drives. Twenty-two links, one forced-expiry rule.
anyone · no expiry · 22
Sees their own drive's waste percentage and external count, and answers for both at the review.
drives over 35% waste · 8The 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
Files arrive on a shared drive with an owner, a manager and a policy — allowed, allowlist or restricted.
Links go out with a role and a risk score. Anything external is counted; anything undated is queued for expiry.
Access ages on the record. Ninety days cold and the item joins the reclaim candidates; five versions and the pile gets collapsed.
Ask across drives returns the file's location, version and risk in one answer — the board pack at version 6, risk 94, convert before the next cycle.
One record
A file is not a blob in a silo. Its sensitivity, links and expiry follow the same identity as everything else on the estate.
The platform's file record underpins every drive here — one identity, one permission model.
CEDX DocsVerified pages reference governed files; the file-drive connector is the search screen's next source.
CEDX SheetsEvery workbook is a file on a drive, with its external shares scored in both places.
CEDX SlidesExported decks inherit their links and expiry from the same share ledger the board pack lives on.
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 drives, your policies
Drive 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/drive. It runs on demo data — the files, drives and people belong to a demo workspace, not to a customer.
A per-link figure built from the link kind, the item's sensitivity, external flags and expiry — the board pack's anyone-view, no-expiry link scores 99 with 420 clicks. Sixty-five shares sit at 70 or above in the demo view, and they are a filter, not an audit project.
An org-wide rule the alert proposes: anyone-links get a 14-day expiry. Twenty-two current links are flagged as candidates, and the do-this-next queue scores expiring or revoking the top twelve at 92 impact — cutting peak external risk without blocking partner work.
It flags cold folders past 90 days and version piles past five versions — 2.8 TB reclaimable in the demo workspace, tabled per item with a waste score. The biggest single item is 134.8 GB of site photography at waste 86.
Yes — the answer bar on the overview. “Where's the latest board pack?” returns the file, its folder, its version, its last modifier and its sharing risk, with the source file cited underneath.
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 count your own anyone-links with no expiry.