Keep your organization's files in your own storage

Connect your own S3-compatible or Azure Blob storage, so the organization's files are kept there, and move earlier files in - or back out.

In short

An organization on the Business or Enterprise plan can keep its files in its own storage. That covers board, note and chat attachments, API Tester files and evidence, UI Tester pictures and videos, candidates' CVs and export archives. Files kept there do not count toward the plan's storage limits, and downloads come straight from your storage.

Before you start

• Who: "Change organization settings".
• Plan: your own file storage is part of the Business and Enterprise plans. Files kept there do not count toward the plan's storage limits.
• First: an S3-compatible bucket or an Azure Blob container that is private, and the keys to reach it (see the section for your IT team).

Steps

1. Open Organizations, choose the organization, then "Settings" › "Connections", and go to "File storage".
2. Choose the "Storage": "S3-compatible (AWS, MinIO, Cloudflare R2, Oracle)" or "Azure Blob Storage".
3. Fill in the fields. For S3 these are "Region", "Bucket", "Access key id" and "Secret key", and "Endpoint" when it is not AWS. For Azure they are "Storage account", "Container" and "Account key".
4. Press "Check connection" and wait until every step passes.
5. Press "Save". New files go to your storage from now on.
6. To bring the files {{brand}} already keeps, press "Move earlier files here" and confirm.

Result: "Saved. New files go to your storage from now on." A move shows "Moving files into your storage: 120 of 400".

Good to know

• Avatars, the organization's logo, screening recordings and run snapshots stay with {{brand}}.
• The secret is stored encrypted and never shown again; "Change the key" replaces it.
• {{brand}} checks the storage every few minutes. When it stops answering, members see "Your organization's storage can't be reached right now. Your admin has been told." and the admins get an inbox notice and an email.
• "Stop using it" moves the files back into {{brand}} storage, one by one and checked. Your copies are left as they are, and the files must fit the plan's storage limits.
• When the plan no longer includes own storage, files already there still open but new uploads are refused until you move them back.

Keep the bucket private The check fails a bucket anyone can read. Never make the bucket public; downloads use signed links.

Details for your IT team

• The check finds the host, connects with TLS, signs in, writes, reads and deletes one small test object, and checks the bucket is not public.
• "Folder prefix" keeps the files under one folder of the bucket. "Use path-style addresses" is for storage such as MinIO.
• If a firewall protects the storage, allow {{brand}}'s outgoing addresses.
• Every failed step names a code; /help/settings/fix-a-company-connection says what to change for each.

If something goes wrong

• "Not saved: the storage did not pass every step." - open the failed step and press "How to fix it".
• "Your own file storage is part of the Business and Enterprise plans."
• "The move stopped. Write to support if it does not go on."

Related

• /help/settings/fix-a-company-connection
• /help/organizations/own-database
• /help/settings/storage-limits