Automatic export of recordings

A workspace on the Business plan can have every finished call recording copied to the workspace's own Google Drive or OneDrive. It's for peace of mind: the recordings your hosts make also live in storage the workspace controls, under its own agreement with Google or Microsoft, for as long as it likes.

It's set up by an Owner or Admin in Org Settings → Recordings → Automatic export, on a computer. Call recording has to be switched on for the server first.

Connecting a destination

1. Choose Connect Google Drive or Connect OneDrive.
2. Confirm with your password and second factor.
3. Sign in to the account recordings should go to, and allow Missived to add files.

Use an account the workspace owns — a shared admin account — not someone's personal one. The connection belongs to the workspace and remembers who connected it. If that person leaves the workspace or stops being an Owner or Admin, the destination pauses and the other Owners and Admins are told to reconnect it.

Missived asks for the narrowest permission each service has:

A plan allows 2 destinations at once, so a workspace can copy to both.

By default only recordings that finish after you connect are copied. Tick Also copy the recordings already kept here when connecting to send the existing ones too.

What is copied

• Voice channels and Stages (on) and meetings (on). Switch either off.
• Video files (off): sound is about 22 MB an hour, video about 0.7 GB.
• Channels to skip: any voice channel you list.
• Members-only channels are copied only when someone who manages the channel, and is in it, ticks Copy this channel's recordings. An Owner who isn't in a members-only channel can't hear its recordings in Missived, so we don't copy them to the workspace's drive either.
• Shared categories are never copied (they can't be recorded in the first place).

Everyone in a recorded call is told where it goes: while export is on, the recording banner says "When it ends, it is copied to this workspace's Google Drive."

Folders and file names

The pattern is {workspace}/{channel}/{date} {time} {title} by default, giving for example Missived recordings/Harbor Builders/standup/2026-11-01 1004.ogg. You can use {workspace}, {channel}, {meeting}, {date}, {time}, {title} and {id}; a / makes a folder. Dates and times are in the workspace's time zone. Names are cleaned (no / \ : * ? " < > |, no leading dot, 200 characters a part) and a clash gets (2).

Meeting titles can be personal, so Put meeting titles in file names can be switched off; the meeting's folder is then just Meetings.

Sound is the Opus .ogg file as recorded and video the .mp4. Drive and OneDrive play both.

How copying works

• A recording is queued when it's sealed. The server copies it in resumable chunks (8 MiB to Drive, 10 MiB to OneDrive). If the server restarts mid-way it asks the service how far it got and carries on from there.
• A copy counts as done only when the service reports the same size and the same checksum (MD5 for Drive, quickXorHash for OneDrive) as ours. Otherwise it's sent again.
• A failure waits 1 minute, then 5, 30, 2 hours, 6 hours, then every 12 hours, for up to 3 days; a service's Retry-After is honoured. After 3 days it stops, the recording stays in Missived, and the Owners and Admins are told once. Try again in Org Settings sends them again.
• Some problems need a person, so the destination pauses at once and the Owners and Admins get one notice (Activity and email): the connection needs signing in again, the storage is full, the folder was deleted, the permission was taken away, the person who connected it is no longer an Owner or Admin, or the plan no longer includes export. Reconnect or Resume fixes it, and the recordings that were waiting go then. Nothing is lost while paused.

Each recording in Org Settings → Recordings shows Copied to Google Drive ✓ (and Open in Google Drive) once it's there. Only Owners and Admins see these marks and links.

Deleting from Missived after copying

After copying can delete a recording from Missived once copied, or 1, 7, 14 or 30 days after (never later than the workspace's retention). A recording is deleted only when every connected destination has each of its files (so a recording with video waits until Video files too has copied the video as well), the service still has each file with a matching checksum, and it isn't marked Keep. If the file is gone from the drive, it's copied again instead. Whoever started the recording and the Owners are told, as with any recording that goes.

Email when a recording is ready

This works without any destination connected. Under Email when a recording is ready:

• Whoever started it (on by default) gets one email when the recording is ready.
• Also email: pick workspace members (up to 50; never Guests). Someone is sent one only if they can open that recording when the mail goes, so a members-only channel's recording reaches only its members.

The email is a plain link to the recording in Missived: the channel's view, or the meeting's page. There's no secret in it. People sign in to open it, so a forwarded email gives nobody access, and the link stops working when the recording is deleted. Someone who turned off message text in notifications (or whose workspace did) gets the email without the channel or meeting name.

Attach the sound is an Owner's choice, off by default. When it's on, the members chosen above (not the starter by default) also get the audio file attached, when it's 10 MB or less (about 25 minutes); bigger recordings get the link only. Video is never attached, and nothing is attached for someone who turned off message text in notifications. The recording itself then goes into their mailboxes: it's outside Missived's retention and security, and mail systems keep copies. Each email is recorded in the audit log as recording.emailed (attached or not, never an address or a name).

Disconnecting

Disconnect stops copying to that destination, skips the ones waiting, revokes Missived's access and forgets the connection. Copies already in the drive stay there: they're the workspace's. Connecting again later is a fresh start: only new recordings are copied unless you tick Also copy the recordings already kept here, and with Google Drive the same Missived recordings folder is used again.

Privacy

Emails go through the email provider Missived already uses (on the subprocessor list); an attached recording does too, only when an Owner chose it.

The copies are in an account that belongs to your workspace. Google or Microsoft hold them under your workspace's own agreement with them, not as Missived's subprocessor. Missived records that a recording was copied (its id, the service, the size), never the file's name, folder or the account's address, in the audit log (recording.exported, recording.export_failed, integration.recording_export_*).

For self-hosters

Each service is off until you set its two variables, using OAuth apps of your own made only for this, with the redirect URL https://<your host>/recording-export/callback:

• Google: a Google Cloud project with the Drive API on, an OAuth client of type Web application, and the https://www.googleapis.com/auth/drive.file scope on its consent screen. Set RECORDING_EXPORT_GOOGLE_CLIENT_ID and RECORDING_EXPORT_GOOGLE_CLIENT_SECRET.
• Microsoft: an Entra app registration for accounts in any organizational directory and personal Microsoft accounts, a Web redirect URI as above, a client secret, and the delegated Microsoft Graph permissions Files.ReadWrite.AppFolder and offline_access. Set RECORDING_EXPORT_MS_CLIENT_ID and RECORDING_EXPORT_MS_CLIENT_SECRET.

The self-hosting guide's CONFIGURATION.md lists them under Automatic export of recordings.