One Storage Layer Under Every Photo and File, Not a Separate App
BeeNet doesn't ask you to run a media library alongside the platform. A recap photo and an attached document both upload through the same storage layer, wherever the module that created them lives. There's no standalone gallery to browse; each file stays attached to the context it belongs to.
What Makes This Different
Four specific, checkable mechanisms — not adjectives.
Shared Infrastructure, Not a Bolt-On App
Media, Files, and file-settings are platform features every module calls into — a recap post and a document upload use the same underlying storage handling, not two different systems glued together.
Files Live Where They're Used
An uploaded photo stays attached to the recap post, document record, or message it belongs to. BeeNet does not maintain a separate, browsable media library — this is a scoped storage layer, not a gallery product.
Uploads Are Embedded, Not a Detour
On mobile and in admin, adding a file happens inside the screen you're already on — composing a recap, attaching a document — instead of routing you out to a dedicated upload tool.
Centrally Governed File Rules
File handling behaviour runs through a dedicated FileSettings feature rather than being hardcoded per module, so the same storage rules apply consistently wherever an upload happens — this runs under the hood, not as a settings screen you manage.
What the Storage Layer Actually Does
The infrastructure other modules build on — photos, documents, and recap images all pass through it.
Backs Every Upload Across the Platform
Recap images, attached documents, and other files created inside other modules are all handled by the same Media and Files features under the hood, instead of each module inventing its own storage.
Documents Stay With Their Record
A file attached to a document or recap post is retrievable from that record — not filed away in a separate library you'd have to search independently.
Upload Happens Inline
Both the admin portal and the mobile app add files from inside the relevant screen — composing a recap or attaching a document — rather than a dedicated media-upload workflow.
Centralized File Settings
A FileSettings feature governs file handling behaviour for the platform, so upload rules aren't duplicated and drifting differently in every module that touches a file.
Recap Photos Ride This Layer
The images attached to a recap post are stored and served through this same underlying media handling — the recap feature doesn't run its own separate image pipeline.
How It Works
Upload from inside the module you're using
Attach a photo or file directly in the recap composer, document form, or wherever the upload is relevant — there's no separate media tool to open first.
The shared storage layer handles it
The Media and Files features process and store the upload under the platform's FileSettings configuration, the same path every module's uploads take.
The file stays attached to its record
The photo or document remains retrievable from the recap post or document record it was uploaded into — that's where you find it again.
See It in Action
A recorded walkthrough of this specific module is coming soon. Book a live demo to see it today.
Module Preview Coming Soon
A recorded walkthrough of this specific module is in production. Book a live demo to see it working today.
Book a Live Demo →Why It Matters for a School
Recap images, documents, and other uploads share the same infrastructure instead of each feature running its own separate storage handling.
Staff and families upload from the screen they're already on — there's no additional gallery or media tool to open and manage.
A file lives on the record it was uploaded to, so it's found by going to that recap, document, or message — not by browsing an index.
Common Questions
Does BeeNet have a photo gallery or media library where I can browse everything uploaded?
No, and we'd rather say so than let you assume it. There is no centralized media library or gallery in the admin portal or the mobile app today. Uploaded photos and files stay attached to the recap post, document, or record they were uploaded into — you find them by going to that record, not by browsing a standalone library.
Can administrators set or manage storage quotas?
Not yet. There's currently no admin interface for managing storage quotas. File handling runs through the FileSettings feature, but quota management as an admin-facing tool isn't built.
Where do uploaded documents and recap photos actually go?
Through the same underlying Media and Files storage layer, regardless of which module triggered the upload. A recap image and an attached document both pass through this shared infrastructure — it's just not exposed to you as a separate destination to manage.
Do I need to train staff on a separate media tool?
No. Uploading happens inline, inside whatever screen you're already using — composing a recap or attaching a document, for example. There is no dedicated upload workflow or app to learn on top of that.
Is this a feature we can demo on its own, like a gallery module?
Not as a standalone screen — it doesn't have one. What we can show you is how it works underneath the modules that do have screens: a recap photo, an attached document, and how each one is stored and retrieved from the record it belongs to.
See Where Your Files Actually Live
Book a demo and we'll show you a recap photo and an attached document going in — and exactly where each one stays retrievable afterward.
Request Demo