You share a folder
The folder carries visibility and the documents inside inherit it: private, named people, or the whole school, with a choice of who may add files there.
All modules
Materials
DocHub
A textbook PDF, a worksheet, a recording: today they travel by email and on flash drives, so nobody knows which version is current. DocHub is the one place for the school team.
Materiały zespołu Whole school
podrecznik-b1.pdf queued
sluchanie-u3.mp3 queued
karta-pracy.docx queued
nagranie-lekcji.mp4 queued
Storage used 6.21 GB of 10 GB
auto folder “Materiały zespołu” · a document inherits the folder's visibility
DocHub
What this module does
40
file extensions that get in at all
200 MB
the largest file that may be declared
3
files go up at once, the rest queue
15 min
the life of an upload or download link
Names, not a count
The "Shared with" column carries surnames and is typed into directly. Visibility follows from the sharing: a folder enters the named-people state when someone is picked.
Materials only
The gate is a list of allowed extensions: documents, images, audio, video, archives. The last extension is what counts, so "sheet.pdf.exe" bounces like any program.
Drop files from the desktop
Dragging files covers the screen with a drop zone, and after the drop each file gets its own progress bar. A batch with no refusals closes the overlay itself.
How much room is left
The footer shows megabytes used with a decimal, the limit and a bar. Deleting takes the bytes back at once: there is no archive here, and folders are one level deep.
Who sees what
A module is a permission, and which records may be touched is settled on write, not in the menu.
| Role | Sees | Changes |
|---|---|---|
| Owner | Every folder in the school, private ones included: school files, not personal shelves. | The name, colour, visibility and share list of any folder, without asking its owner. |
| Methodologist | The same as the owner: every folder in the school. | The same: settings and shares of any folder, not only their own. |
| Teacher | Their own folders, ones shared with them by name, and school-wide ones. Nothing else. | Their own folders entirely. In someone else's they add files, if given the right to add. |
| Student | No access to this screen. | Nothing. Material for students travels through E-learning, not from here. |
The details nobody asks about during a demo
The things that only surface in the third week of working with the module.
What this module does not do
- a folder tree - there is one level, because in a tree access changes silently
- an archive - deleting takes the bytes out of storage and frees the space at once
- file versions - a new worksheet is a new file, or a delete and an upload
- a public link - no address for a file leaves the school from this module
Whoever sees the FOLDER: a document inherits its visibility and has none of its own. There are three states - private, named people, the whole school - and the school-wide one adds a decision: do the others only read, or may they add too. So “A1 materials” is set once, not on each of forty files.
Yes, by dragging them off the desktop as well: the screen is covered by an overlay with a drop zone, and after the drop each file gets its own progress bar. Three go up at a time and the rest wait in the queue. Closing the overlay does not stop the transfer, and a batch with no refusals closes it by itself.
It bounces off the list of allowed extensions: forty entries in five families - documents, images, audio, video, archives. The LAST extension is what counts, so “worksheet.pdf.exe” is refused exactly like “virus.exe”. The same gate sits on renaming, otherwise a file could simply be renamed after it landed.
Two thousand files and 10 GB on the Pro plan, six thousand files and 30 GB on the School plan; the operator can raise either number on its own. Both ceilings are hard and both are needed: a file counter alone lets through one four-gigabyte film, and a byte total alone lets through ten thousand small things. Used megabytes, the ceiling and a bar sit in the footer.
No, and that is not a missing screen. The signed download link carries “attachment”, so a PDF or an uploaded HTML file is SAVED under its real name instead of rendering on the storage domain. The link is minted on the click and lives fifteen minutes, so forwarding it stops working before it is of use to anyone.
Because the folder is what carries access. A tree would need inheritance downwards, and dragging a branch would silently change access to dozens of files at once - the worst possible bug in a module about sharing. There is one level, files are seen after entering a folder, and the folder lives in the address, so the browser's back button leaves it.
The bytes. Deleting a file removes the object from storage along with the row and frees the space in the footer immediately - there is no archive here, because storage costs money every month while the rest of the panel archives happily. A folder with files will not be deleted: move or delete them first, so nobody's work goes with it.
No, and that is the edge of the module: DocHub stops at the team, and a folder can only be shared with someone on the staff list. Material for students has its own module, E-learning, where a folder is assigned to a group or to a single student. The two share one thing: the storage ceiling is counted for both together.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.