You assign a folder
The recipient is a group or a single student, and every file inherits the folder's recipients. "A1 materials" is set once, not on each of forty separate files.
All modules
Materials
E-learning
A lesson ends and the teacher wants the A1 group to have a worksheet by tomorrow, and one absent student to get extra practice. E-learning is that shelf on the student's side.
Materials 24
Recipients 1
New · 7 days 2
MaterialRecipientsSizeSeen by
czasowniki-a1.pdf Materiały do A1 no recipients1,2 MB Team
sluchanie-03.mp3 Materiały do A1 no recipients6,4 MB Team
powtorka-b2.pdf Nadrabianie J. Kowalska2,1 MB Students
auto student materials · folder “Materiały do A1”
E-learning
What this module does
40
file extensions the storage accepts
200 MB
ceiling on a single uploaded file
15 min
lifetime of a signed download address
10 GB
space on the Pro plan, shared with DocHub
No walls inside the team
Whatever one person with the module uploads, everyone else with it sees at once: a methodologist prepares the material, someone else teaches it, and nothing has to be shared.
Students see one list
The same address shows a student only what was assigned to them: name, folder with a stripe in its color, size, type, date and a pinned download button.
The "new" mark
It lands on any file uploaded in the last seven days, so it is the same for the whole group and fades on its own. No per-student read trail is collected here.
Uploads three at a time
A whole batch goes up in a queue of three, dropped straight from the desktop if you like, and the overlay shows a bar per file. Storage is shared with DocHub.
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 and file in the school, with who each one is assigned to. | Everything, other people's folders too: name, color, recipients, deletion. |
| Methodologist | The same as the owner: the school's whole list of folders. | The same. They also prepare material for groups they do not teach. |
| Teacher | Every folder in the school: inside the team there are no walls here. | Uploads, assigns to any group, deletes their own. Cannot rename another's. |
| Student | One list: whatever is assigned to them or to their group, and nothing more. | Nothing. They download files; only the team uploads. |
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 download trail - who opened the file stays between them and their browser
- assigning a single file - the folder carries the recipients and the file inherits them
- students handing work back - only the team uploads
- file versions, in-browser preview or a folder tree - one level, and the file downloads
Because they are two different sentences about access. DocHub is the team's cabinet: a folder can be private, it is shared by name, and a student has no way in at all. E-learning is the student's shelf: inside the team there are no walls on it, and the only wall stands on the school-student border. The cloud space is shared, because the provider's bill is one; the file count stays separate.
From the mark on the file, and from nowhere else: this module sends no mail and rings no bell. The mark is counted from the upload time rather than from whether anyone looked, so it is identical for the whole group and fades on its own after a week. A “since your last visit” variant would need a per-person trail, and that is deliberately not collected.
There is no way for them to: the assignment saves correctly, but without an account there is nothing to log in with. That is why the recipient picker shows such a student in amber, in the list and on the badge, and a line under the save says how many of them there are. The mark warns, it does not forbid: the account usually follows, and the assignment waits for it.
Its recipients change, and in both directions: a file from a folder with no recipients drives onto a group's screen, and one assigned to a group vanishes from it. None of that is visible from the “folder” cell alone, so the move is confirmed in a dialog that names who gains and who loses access. The same path for one row as for a selection.
In a cloud provider's bucket, not in the database. An upload takes two steps: the API signs an address and the browser sends the bytes straight there, bypassing the panel; then the API asks the bucket for the real size, because the one the browser reported is only a promise. That is why the ceiling is checked twice. A download uses a signed address good for a quarter of an hour and saves the file, never opens it.
Forty extensions from a list: documents and spreadsheets, images, audio, video and archives. Programs, no. The sieve sits in the API rather than in the file field on screen, because that one is a hint and can be bypassed. The largest single file is two hundred megabytes, and every upload takes space shared with DocHub - so a refusal talks about the school's space, not about the module.
It stays. Archiving a group does not take its folders away, because the course ends but the textbook stays with the student. It disappears only together with the student: an archived one has their way into the school closed, so there is nothing to log in to. There is no archive for a single file and there will not be - deleting takes the bytes, because space costs money every month.
No and no. This module keeps no download trail, so the screen does not pretend to know. “How they did” is a different module altogether: Exercises, because that is where the content a student solves lives, along with the attempts and the score. Here there is a file and who may download it. That border is chosen, not temporary.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.