All of it lives in Settings, visible to the owner and admins. On the shared plan the branding fields are not shown at all: a dead field you cannot press is more annoying than one honest line saying this belongs to another plan.
Colour
The school's accent colour is set as a hexadecimal value — the one from your brand guide. The portal puts it on buttons and active elements and works out the text colour on top of it, so that a label stays readable on both a dark and a light accent.
A preview sits next to the field. It is drawn separately on purpose: until the colour is saved the portal theme is still the old one, and a real button would show you the old shade rather than the new one.
Logo
The logo travels into school files the same way a video lesson does: a record first, then a direct upload to storage, then a mark saying the file has arrived.
The branding settings store the file identifier, not a link to it. Links into storage are signed and live about fifteen minutes — a link written into the database would be stale within the hour. The portal fetches a fresh one every time it shows the logo.
On the branded plan that logo also goes onto the certificate, replacing ours.
A domain of your own
The domain is entered in the school card, but the entry alone does nothing: the domain has to be pointed at us at your registrar. That is why the screen shows not just a field but the exact record to create — copied whole with one button and transferred character by character.
The order is:
1Create the record the portal shows at your registrar.
2Enter the domain in the school settings and save.
3Wait for the change to propagate. Usually minutes, sometimes hours — that depends on the registrar, not on the portal.
Domains are unique: one that belongs to another school cannot be taken. If saving fails, the most likely reason by far is that the domain is already in use; the portal says so as a likely cause rather than as a fact, because the server does not give a precise answer in that case.
What branding never touches
The certificate verification page. It always looks the same and is shown on behalf of Voone. Otherwise a forged document could arrive together with a forged page confirming it.
The Voone app. It stays the Voone app: your students use it at no cost, but it is not "your school's app".
The technical sender of email. The school's name is in the From line and its address in Reply-To, while the technical sender stays ours — a message sent from somebody else's domain fails its authentication and lands in spam.