Module 08 · Admin and Security
Secure video conferencing for companies that need to know who can start a call, who can change a policy and what happened afterwards. Vebex puts single sign-on, roles, audit log, retention and encryption in transit in the admin console, not in a sales promise.
Vebex is a video conferencing platform for business. The security module is included from the Business tier, and the price basis is the host licence per month plus any retained storage or dial-in selected in the proposal. There is no online checkout and no binding price hidden behind this page. Tell us the largest meeting you run and we write the number down.
The admin console answers the questions that appear after a meeting goes wrong. Who admitted an external guest? Which administrator changed retention? When was a role granted, and by whom? Who pulled a recording down before it expired? A live status dot is not evidence. An audit entry with an actor, action and timestamp is evidence you can inspect.
Vebex has run since 2017. Thirty-eight people build and support it, most of them engineers. We do not attach a certification name we were not given, and we do not print an uptime percentage we cannot measure from our own status data.
Connect your identity provider and make the workspace follow your join and leave process. SSO is for people who should sign in with the company account, not collect another password in a spreadsheet. We confirm the provider and domain during rollout.
Workspace owner, administrator, host and attendee do not get the same reach. Hosts can run calls. They cannot change retention or invite another administrator unless you grant that role. The least powerful useful role is the right default.
Role changes, sign-in events, policy edits and retention actions sit in a chronological log. Filter by actor or action, export the result, and keep the record for the period your policy requires. The log is not a decorative dashboard.
Set recording and message retention to 7, 30, 90 or 365 days. At the end of the period the media is deleted. Pinning is an explicit admin action, and that action is itself logged. If your policy says seven days, the product should not quietly keep a year.
Meeting audio, video, chat and control traffic is encrypted while it moves between participant devices and Vebex services. A browser joining from a weak connection still gets the transport protection; a bad network does not turn into a clear-text exception.
This page does not claim end-to-end encryption. That phrase has a specific meaning, and a service that still provides moderation, recording and dial-in should not use it as a loose synonym for encrypted transport.
Waiting rooms, admission controls and host permissions stop a meeting link from being the whole policy. A host can keep an attendee out, remove a participant and end the call. External access can be turned off for a workspace that does not need it.
Dial-in remains part of the design. Dial-in is how the site foreman joins from a truck with one bar of signal. Security controls that only work for a laptop are not controls for the whole meeting.
Recording and transcripts use a retention window you choose. One hour of 1080p is roughly 600 MB, so the storage question is not abstract. A year of recordings is a storage decision and a review decision. The recording module shows the arithmetic.
We do not score who looked away from the camera. That feature does not exist here and will not. The audit log tells an administrator what changed in the workspace; it does not turn participants into a behavioural report.
We record hosts, attendees, external guests, administrators and the identity provider you already operate.
The licence follows the largest meeting, not the headcount. That also tells us where admission and role pressure will sit.
Choose whether external links, recording, dial-in and guest access are available at workspace level.
Test the join and removal paths with a small group. Nobody needs to discover the wrong default during a town hall.
Make a policy change, inspect the event and export it. A control is not finished until the evidence is visible.
Every first proposal starts monthly. Annual terms only happen when you ask for them.
It is a catalogue module, included from the Business tier. The proposal still spells out the tier, host count, largest meeting and retained storage. There is no feature paywall inside a live call.
No certification is stated here. We describe the controls we supply and the limits around them. Ask for the operational detail you need in your inquiry.
A team that needs a purchased compliance badge more than it needs a readable access policy should not start here. Neither should a team unwilling to manage its own identity provider and administrator accounts.
You can get the basis before the call. Admin and Security is included from Business tier. The written proposal supplies the actual USD amount after we know hosts, meeting size, retention and any other modules. Use the deployment configurator for the tier and storage sketch.
Tell us your identity setup, host count and largest meeting. We will reply with a written proposal rather than a generic security deck.