A shared directory should have one clearly defined purpose
In training, a shared space is most often used to distribute materials or to collect results. Combining both functions without separate directories leads to files being overwritten by accident and to many versions named “final”. The participant should know straight away where the original is and where they are allowed to save.
The simplest layout consists of a read-only materials directory, a private directory for each participant and an optional exchange directory for team work. The names should match the language of the instructions. An elaborate hierarchy does not help if the instructor has to spend several minutes explaining where the first file is.
Starting materials must not change
Sample code, data and instructions should be read-only. The participant copies the file they need into their own directory and works on the copy. That way, accidentally saving changes does not affect the whole group, and the original remains the reference point.
Each edition of the material should have a version tied to the training programme. Quietly swapping a file during the sessions can leave half the group working on different content. If a correction is necessary, the instructor should announce it openly and say how to check the version, for example by a release name or the checksum of a larger archive.
Private results should not be visible to the whole group
Each account can have its own working directory, accessible to the participant and to the instructor to the extent needed for support. Solutions, notes and temporary data do not need to be readable by other people. This matters especially for assessed tasks, onboarding and technical recruitment.
For presenting results together, it is better to prepare a separate directory or to ask participants to publish a chosen file deliberately. Permission to write should not automatically mean the right to read the whole group's work.
Editing a file at the same time needs the right tool
A shared file system does not resolve semantic conflicts. Two people saving the same document can lose some of their changes, even if the operation technically succeeds. For working together on code, a Git repository is better, and for a document, a tool designed for concurrent editing.
A drive does, however, work well for distributing large files, collecting results and passing artefacts between the stages of an exercise. The instructions should state whether a file is a source, a working copy or a result to be handed in.
A test from a participant account catches most problems
Before the sessions, you should sign in as an ordinary user, open the material, copy it, save a result and check whether the instructor can collect it. A test from an administrator account will not reveal missing permissions or a wrongly mapped directory.
It is also worth checking names containing non-ASCII characters (e.g. Polish diacritics), larger files and behaviour after reconnecting. If the materials will be used both from a desktop in the browser and over SSH, the path should be clear in both ways of working.
Sensitive data requires a separate decision
A shared drive should not become a route for copying production data into the lab. Materials should be classified before the training, personal information removed and access limited to the people registered for the event. Access logging may be necessary, but its scope and the retention period for the logs should follow from the organisation's policy.
If participants have to work on company files, you need to decide whether they may download them to a local computer and where they may be stored after the end. The transfer settings in the remote desktop should be consistent with that decision.
The shared space should be closed down deliberately
Before the environment expires, participants are given a deadline for exporting their results. The organiser keeps only the materials that will be used again and deletes the working directories in line with the agreed period. Leaving the whole drive “for later” makes it hard to establish who owns the data and increases the risk of accidental access.
Shared materials are one element of the technical scope of a training environment. Their value does not come from the number of files, but from every participant receiving the right material at the right moment and being able to keep their own result safely.