The base module. It is on for every event, it cannot be switched off, and it is the one job every conference has: getting the files out of the speakers.
What it is
A deadline-enforced collection point for presentation files. Speakers upload against a window you set, with an optional per-talk cut-off expressed in hours before they present. Files are versioned, so a replacement never destroys what came before, and the system chases anyone who has not delivered.
Because it is the base module, every other module in the pipeline assumes it. Review & Approval reviews what arrives here; Posters borrows its file-size limit; the Attendee App can distribute what it holds.
What it changes
The deadline stops being a date in an email and becomes something the software enforces and reminds against. Managers stop maintaining a spreadsheet of who has sent what, because the to-do list and the reminder sweep do that. Speakers stop asking where to send things.
The 24-hour rule
Set a per-talk cut-off so nobody is swapping slides while the previous speaker is still on stage. It is expressed relative to each presentation's own start time, not the event.
The staggered close
Leave the window open to the last day of the event but rely on the per-talk cut-off, so a Friday speaker is not held to a Monday deadline.
The quiet chase
Reminders at seven, three and one day out, sent at 8am in the venue's timezone, once per person per day, stopping automatically when the file arrives.
What you can do
- Set an upload window and a per-presentation cut-off, both in venue time.
- Cap file size per event — 1 GB per file unless you set your own limit.
- Version files — every replacement is kept, with history and rollback.
- Preview Office decks as PDF in the browser rather than downloading them.
- Group files by purpose, and nominate a primary file.
- Reuse a speaker's files from a previous event.
- Send file requests by hand from the Send Email wizard, and magic links that skip sign-in entirely.
Settings
| Setting | What it controls | Default |
|---|---|---|
| Upload open date | When uploading becomes possible. Blank accepts uploads immediately. | Event creation time |
| Upload close date | When uploading stops. Blank never closes. Must be after the open date. | 23:59, last day |
| Cutoff before presentation | Hours before each talk's own start time after which its files lock. The practical deadline for most events. | 24 hours |
| Max file size | Largest single file. A switch turns the event's own limit on and off; with it off, files up to 1 GB are accepted. Also governs poster uploads. | 1 GB |
| Send upload reminders | Master switch for the automatic chase. Off hides the three settings below but keeps their values. | On |
| Remind before deadline | Which days before the deadline a reminder goes out. Entered as a comma list; sorted for you. | 7, 3, 1 |
| Remind every N days | A repeating nag for people with no deadline at all. Zero means off. | Off |
| Send reminders at | Hour of day, in the venue's timezone. | 08:00 |
Nothing. It is enabled automatically on every new event, with the defaults above already written.
The file-size cap is shared with Posters — there is no separate poster limit. In-browser PDF preview of Office files depends on a conversion service that is configured per deployment; where it is not configured, previews quietly fall back to a download. There is no bulk download of every speaker's files.