White-Label Configuration Options

The instance runs on your own hostname, and it carries your own product name throughout the interface. Invitations and notifications leave from your mail server, with your sender name and address, so nothing a participant receives mentions us.

You set where a participant lands after leaving a meeting, which support address appears when somebody needs help, and which imprint and legal pages are shown. For a participant who has never heard of Veeting, there is nothing to notice.

The room has more settings than any other area. They cover which authentication a meeting requires, whether participants may raise the video quality, what happens to participant names in an off the record meeting, which sounds play when somebody arrives or the room closes, and whether dial-in and recording are available by default.

You can also put your own tool in the room. A custom tool is your own web page shown beside the video, under a label you choose. Customers use it to bring a case file, a checklist or an order form into the meeting rather than sending people somewhere else. It is documented for developers on the meeting room widgets page.

The AI assistant is no different. You can turn it off entirely, or point it at your own endpoint and your own model, which is what you do when nothing may go to a service you have not approved.

This part matters to partners rather than to a single organization running one instance. The platform is arranged in four levels. The system sits at the top, then distributors, then resellers, and each white-label instance at the bottom.

A setting takes its value from the lowest level that defines one, falling back up the chain, so a new instance inherits everything and its operator sets only what differs. That is what makes an unlimited number of instances practical to run, because creating one means setting the handful of values that differ, not copying a configuration.

Where a value must hold everywhere beneath you, you lock it. A lock is enforced rather than advisory. The setting disappears from the editor at the levels below, a direct write to it is refused, and the parent's value is what the platform reads at runtime. Commercial settings work the same way, so nobody running a white-label instance can switch on billing for themselves.

None of this is work you do before you can start. Every setting resolves from a default, so an instance is configured the moment it exists, and the only ones left empty are those nobody but you can supply, such as your own mail server or certificate. Most customers rely on our defaults and change only a handful of values.

The settings are also not a menu to work through. They are there so that when a requirement turns up that is not the usual one, the answer is a setting rather than a development project. If you are measuring us against a specific rule you have to meet, talk to us and we will tell you plainly whether the answer is already a setting.