One fixed code your whole team can reuse — no re-sharing a new code every time
SharingCast normally creates a fresh random code, such as SC-7K2QF, every time you start sharing. That is ideal for one-off transfers: the code is only useful for a few minutes and then it is gone.
But many people send files between the same devices again and again. A designer who moves files from their phone to their work PC every day, an office where one machine shares scanned documents, or a teacher who sends material from the same laptop to the classroom computer. For them, reading out and typing a new code every time quickly becomes a chore.
A static room code is a code that stays the same every time a particular device starts sharing. The code is saved in that device’s browser (or app), so the next time it shares files, it uses the same code automatically. The device on the other end can simply enter the code it already knows, without anyone needing to read out a new one.
The static code belongs to the device that starts sharing from the Send tab. The receiving device still enters the code in the Receive tab as usual; it just never has to ask what it is.
From now on, every time this device starts sharing, it uses the same code. Clearing the browser’s site data removes the saved code, so set it again if that happens.

A static code is convenient precisely because it does not change. That also makes it predictable: anyone who has ever seen it, overheard it, or read it on a sticky note knows it too. A password closes that gap.
Good practice for passwords on a static code:
For one-off transfers to people outside your team, a fresh random code is still the safer choice.
If several devices in an office use static codes, a simple naming pattern prevents mix-ups. Use the room or desk name (SC-RECEP, SC-STUD1, SC-MEET2), keep a short list of which code belongs to which device, and review it when equipment changes. Because codes live in each device’s browser, replacing a computer means setting the code again on the new one.
It also helps to agree on a simple rule: static codes are for internal, routine transfers between known devices; anything sensitive or external uses a fresh code and a fresh password.
Each code should belong to one sharing device at a time. Give every device its own code to avoid confusion.
Yes. The Windows and Android apps use the same SharingCast page, so the option is available there too.
It is more predictable than a random code, which is why a password is essential. With a strong password, only people who know both can receive.
Untick “Use a static room code” in the Send tab, and SharingCast goes back to creating a new random code each time.