Shared drive
- ClientX_final_v3
- USE THIS
- signage pack (copy)
One library for the event. Not three places to search on Monday morning.
One folder in Magicbox
Three sources, one searchable Magicbox library.
Files still live in shared drive, SharePoint, and Portfolio on the left. Scrolling moves each source into the Magicbox on the right and lists the gathered folders under the sign-in form.
Monday morning is three searches for the same event. None of them is the folder you can hand to the next person.
The same pack sits in folders called final, v3, and USE THIS. Copying it for this year is slow, and it is easy to overwrite the good one.
You can find the photo. The working files are somewhere else, and you still have to guess which folder is current.
Search finds someone's copy. When they leave or tidy their folders, the brief goes with them, and a linked job will not open like a normal folder.
Find the file
Staff lose minutes every day hunting SharePoint, the shared drive, and Teams — and still open the wrong copy. Magicbox is built so the job you half remember becomes a query across every team workspace you can access.
Minutes every day just to find one file
SharePoint, then the shared drive, then a message on Teams.
Search returns the wrong file, or nothing
You know the name. It still does not show up in the place you expect.
Do you have final, final_v7, and FINAL_use_this?
Too many copies. Nobody knows which one is right.
Shipped today
Ranked library search
Search names, tags, and folders across Personal and the libraries you can access.
Filters that narrow the hunt
Kind, date, and catalog facets — plus trash when you need to recover something.
Preview without a download
Open images, PDFs, Office, video, and more in the portal before you copy or share.
One file. Clear versions.
Version history on each file — a current tip you can restore, not another folder called FINAL_use_this. Identical bytes store once.
Next on the catalog
Planned: semantic search and AI tagging so a vague memory — “the teal signage from the 2023 client event” — becomes a query, not a treasure hunt.
Take the pack that worked and place it in this year’s job. Last year’s folder stays where the team left it — and each file keeps a clear version line instead of anotherfinal_v7 on the share.
Last year stays last year
Starting this year’s job does not overwrite the folder everyone already trusts.
This year’s folder is its own
You take the pack that worked and place it in the new job.
You can see where it came from
The new folder remembers which job it was copied from.
Versions, not filename archaeology
Upload a new revision on the same file — browse v1, v2, v3, and restore — instead of spawning final_v7 beside the real one.
A wrong delete is not the end
Deleted files sit in the recycle bin, and an admin can still recover them after that.
Copied into ClientX 2025 — source recorded for audit
Permissions, placements, and content-addressed files are the substrate agents need. Magicbox is designed so Harry-specific workflows — find a prior event, branch the pack, tag and assemble — run on the same catalog staff use every day, with people in the loop.
ReBAC permissions and explicit placements mean automation respects the same rules as people — not a shadow copy on someone’s OneDrive.
Advanced search ships today. Next: vectors and tags on the same files you Copy to…, then agents that draft event packs from proven folders — with approval gates.
Events, signage, production, and design each have different folder habits. The platform is meant to automate setup steps specific to how Harry runs jobs, not generic M365 chat.
The folder belongs to the job. It does not depend on whose OneDrive it was saved in, or on who remembers the path on the share.
The job is a folder of linked files. It has to open the way it does from a normal drive, for the next person as well as you.
The brief, photos, and working pack live with the event. Library search and tags replace Monday-morning hunts across SharePoint and the share.
Search and reuse ship today. Semantic findability, a knowledge graph, and Harry-specific agents follow in deliberate phases — on the same permissioned catalog, not a separate tool.
Shared libraries, reuse without duplicating bytes, and library search across names, tags, and folders. Large copies and uploads run in the background; Copy to… records source for audit.
Semantic search and AI tagging on the same catalog — so staff find prior events when filenames are gone from memory.
A company-wide knowledge graph links related assets, events, and templates.
Agents draft and assemble Harry-specific project packages — events, signage, exhibition builds — from proven folders.
Ready to open the archive?
Sign in with your Harry the Hirer account to browse project assets.