Document management that doesn't mean "shared drive"

Every event generates a small mountain of documents. Exhibitor insurance certificates. Speaker presentations. Venue contracts. Sponsorship agreements. Electrical plans. Logos in four formats, three of which are the wrong version. Risk assessments. Accessibility plans. Fire safety compliance forms. The list keeps growing until it's hundreds of files per event.

Most teams manage this with a shared drive and optimism. Some use Dropbox. Some use email, which is worse. A few have graduated to SharePoint folders with names like "Exhibitor Docs - FINAL - v3 - USE THIS ONE."

The problem isn't storage. Storage is solved. The problem is context.

Documents without context are just files

A shared drive gives you a place to put files. It doesn't give you any connection between those files and the things they relate to.

An exhibitor's insurance certificate lives in a folder called "Insurance." Their logo lives in "Logos." Their booth electrical plan lives in "Venue Docs." Their signed agreement lives in "Contracts." Four documents, four folders, zero connection to the exhibitor record they all belong to.

When someone asks "has Exhibitor X submitted everything we need?" you're opening four folders and cross-referencing against a spreadsheet. Or you're searching your inbox. Or you're asking a colleague who might remember.

Version control is the other pain point. A speaker submits their presentation. Then they submit an updated version. Then a "final" version. Then a "final final" version the night before. Which one is current? The one with the most recent timestamp? The one Sarah confirmed via email last Tuesday? The one in the shared drive, or the one that came through as an attachment?

These aren't edge cases. This is every event.

Documents tied to entities

ema takes a different approach. Documents belong to the things they're about.

An exhibitor's insurance certificate, logo, electrical plan, and signed agreement all live on the exhibitor's record. Not in a folder named after a category — on the actual entity they relate to. When you open an exhibitor's profile, you see their documents. All of them, in one place, with version history.

Speaker presentations live with the speaker record. Venue contracts live with the venue. Sponsorship agreements live with the sponsor. The document is part of the context, not floating separately in a file system.

This means "has Exhibitor X submitted everything we need?" is a question you can answer by looking at one screen, not four folders and an email search.

Version tracking that works

Every document in ema has a version history. When a speaker uploads a new version of their presentation, the previous versions are still there. You can see who uploaded what, when, and which version is current.

No naming conventions required. No "v2_FINAL_REVISED" filenames. No guessing which attachment in a 47-message email thread is the latest one.

Permissions that make sense

Here's where shared drives really fall apart: permissions.

In a shared drive, you either give someone access to the whole folder or you don't. There's no practical way to let Exhibitor A see their own documents without also seeing Exhibitor B's insurance certificate and Exhibitor C's electrical plan.

ema's document sharing is permission-aware. Exhibitors see their own documents. Sponsors see theirs. Speakers see theirs. Your team sees everything. Nobody's rummaging through files that aren't relevant to them, and you're not managing folder permissions for 50 individual exhibitors.

SharePoint integration

For teams already using Microsoft 365, ema integrates with SharePoint. Your documents live in the ema context — tied to entities, version-tracked, permission-controlled — while staying accessible through the tools your organisation already uses.

This isn't about replacing your file storage. It's about adding the layer of context and structure that file storage alone can't provide.

The point

ema isn't trying to be a better Dropbox or a better Google Drive. File storage is a solved problem. What isn't solved is making those files useful in the context of running an event.

Documents that live with the entities they belong to. Versions you can track without a naming convention. Permissions that don't require a folder-per-exhibitor workaround. That's what document management looks like when it's built for events, not bolted on as an afterthought.