Administration and Security

This page is for the administrator who provisions access and the security, privacy, or compliance reviewer who must approve the tool. It explains how meetings inherit your workspace identity rather than standing up a second silo, who can host, who can join, what is logged, how meetings are paid for, and, plainly, how audio and video are encrypted and what is and is not available around recording. Where a capability is not available, this page says so rather than implying it.

One Identity: Access Follows Your Workspace

After this section you will know that meeting access is not a separate account. Backbuild Meetings is part of the Backbuild workspace. The people who can use it are the active members of your organization, signing in the way they sign in to everything else, with the same multi-factor and passkeys. There is no conferencing login to provision and no second directory to keep in step. See Signing In and Account Security.

• Offboarding is one step. When you remove or deactivate a member, they lose access to meetings with the rest of the workspace.
• The people you invite are the people you already have. Inviting by name draws on your organization's directory, not a separate contact list.

Who Can Host, and Who Can Join

After this section you will know where the boundaries are.

• Any active member can host. Every member of your organization can create a meeting, and the creator is its host. There is no setting to limit hosting to certain roles.
• The host holds the controls. Admitting and denying, locking, spotlighting, and removing belong to the host of each meeting. There is no co-host control yet.
• Only members join. A meeting admits members of its own organization, signed in. People outside the organization cannot join by link yet; to meet with someone outside it, add them to the organization as a member with a role that grants only what they need.
• No one enters without the host. Everyone except the host waits in the waiting room until the host admits them, and a locked room accepts no new requests. A forwarded invitation therefore never puts anyone straight into the room. See The Waiting Room and Moderation.

What Is Logged and How Meetings Are Isolated

After this section you will know what is recorded for governance and how tenants are kept apart. Creating, renaming, starting, ending, and deleting a meeting, sending invitations, admitting, denying, and removing people, locking the room, and posting in the meeting chat are written to your organization's audit trail with the person who did it. Meetings belong to your organization and are isolated from every other organization on the platform.

Billing: Meetings Draw Your Organization's Credits

After this section you will know how meetings are paid for and where the spend shows. There is no meetings subscription and no per-host license. Meetings run on your organization's universal usage credits on every plan, including Free, at the per-participant-minute rate the Meetings hub shows (current pricing; the pricing page is the authoritative source).

• The organization pays, never the attendee. The whole meeting bills to the organization it belongs to. Attendees are never asked for payment.
• Entry needs credits; a live meeting is never interrupted. Joining needs available credits, and members are told plainly when the balance stops them. Once people are connected, the balance running out never cuts them off.
• Charged per billing period. Meeting minutes are totaled for each monthly billing period and charged when the period closes. The charges appear in your credit history as Meetings usage on the Billing & Usage screen.
• Only meeting time draws meeting charges. Scheduling, the meetings list, and the whiteboard add none. Invitations are ordinary email against your outbound allowance.

Encryption and Connections: the Honest Posture

After this section you will answer the encryption question accurately. This is the question reviewers scrutinize most, and the one where an overclaim is worse than a limitation:

• Audio and video are encrypted on every connection. Media travels directly between the participants' browsers over encrypted real-time connections (the standard DTLS-SRTP protection browsers use for calls). It is not sent in the clear and does not pass through a Backbuild media server.
• Call setup goes through Backbuild. The messages that set up a call, and the meeting chat, travel to Backbuild over TLS.
• Not described as end-to-end encrypted. Because Backbuild's servers relay the call setup and the app offers no way for participants to verify each other's keys, Backbuild does not describe Meetings as end-to-end encrypted. Do not represent it as such to your own reviewers.
• A public address-discovery service sees network addresses. To find a direct route between participants, each browser contacts a public address-discovery (STUN) service, which sees that participant's public network address.
• No relay server yet. Because media is never relayed, a network that blocks direct connections between browsers (some corporate firewalls and carrier networks) can stop audio and video from connecting, while chat and the whiteboard keep working.
• Data at rest. Meeting records, the meeting chat, and whiteboards are stored with the same encryption at rest as the rest of your Backbuild workspace.

Recording, Transcription, and Consent

After this section you will know precisely what exists, so you can set policy.

• No recording. Backbuild Meetings does not record meetings. The host's toolbar shows a Record control, but pressing it does not start a recording, and the room may report that recording could not start. No audio or video is stored.
• No transcription. Meetings are not transcribed, and no transcript is produced or stored, although the hub's price line mentions transcription billing; nothing is charged for it.
• What participants can keep. The meeting chat and the whiteboard are kept with the meeting. Treat them as meeting records under your own retention policy.

Retention and Deletion

After this section you will know what is kept and how to remove it. A meeting is a record in your workspace: its title, its schedule, who took part, its chat, and its whiteboard if one was used. The host deletes a meeting from its row in the Meetings hub, and a live meeting is ended first. A meeting whose whiteboard was used cannot be deleted from the hub yet: the hub refuses and the meeting stays in the list, so plan to keep such meetings, and keep notes you may want to delete in the meeting chat or a Backbuild Docs document instead.

Frequently Asked Questions