Skip to content

Where your files are stored

Learn it in the academy: Files and storage (video)

Every organisation gets storage on the platform by default, and can instead connect its own S3 bucket or WebDAV server. The choice is made once, for the organisation, by an administrator with the storage permission — it is not a per-project or per-file setting.

Files are held in the platform’s own storage in Frankfurt. Nothing needs connecting and nothing needs paying for separately — the space available is the one your plan includes.

That answers most data-residency questions on its own. The honest limit: the hosting provider is US-headquartered, so a European region does not by itself answer an objection about US legal reach. If that is the question being asked, connect your own storage.

Where an organisation chooses platform storage or connects its ownOpen /a/settings/organization in the app
Where an organisation chooses platform storage or connects its ownWhere an organisation chooses platform storage or connects its own

Two kinds are supported:

S3, or anything that speaks the S3 API — AWS, and the many providers that implement it. You give the connection a Name, then supply an Endpoint, a Region, a Bucket and an access key pair.

WebDAV — Nextcloud, ownCloud and similar. You supply a Server URL, a username and password, and a Base path under the server root (for example /remote.php/dav/files/anw). Leave the path empty to use the root itself. WebDAV has no region, so that field does not appear.

A few things that surprise people:

  • The region is stored exactly as you type it and is never guessed from the endpoint. It is frequently a compatibility value rather than a real place — Infomaniak, for instance, documents us-east-1 for data physically held in Switzerland. Copy whatever your provider’s documentation says, even when it looks wrong.
  • Connecting does not move anything. Files already stored keep living where they were written. The backend you choose applies to new uploads.
  • A connected backend cannot be disconnected while it still holds files. The attempt is refused rather than orphaning them.
  • Nothing is deleted from your own storage without someone asking. Files moved to the trash on your own S3 bucket are not cleared out after 30 days, as they are on platform storage; they stay in the trash until someone deletes them permanently.
  • Credentials are write-only to you. They are stored encrypted and never shown again, and the activity log records which bucket was connected — never the secret.

The bucket is created in your provider’s console, not here. The platform needs a private bucket and a key pair scoped to it — never your account’s root credentials.

  1. Create a private bucket. Public access must stay off: every file is served through the platform, which mints a short-lived link per download, so nothing needs to be world-readable.

  2. Create an access key limited to that bucket, and grant it these actions — reading, writing, deleting, and the four that large uploads are split into:

    GetObject · HeadObject · PutObject · DeleteObject · CreateMultipartUpload · UploadPart · CompleteMultipartUpload · AbortMultipartUpload

    Without the multipart four, small files upload and large ones fail.

  3. Add a CORS rule — only if you want Direct uploads. Skip this and the connection still works on the proxied lane. The rule must allow PUT, GET and HEAD from https://actionnetwork.world, and — the part that is easy to miss — it must expose the ETag response header:

    [
    {
    "AllowedOrigins": ["https://actionnetwork.world"],
    "AllowedMethods": ["PUT", "GET", "HEAD"],
    "AllowedHeaders": ["*"],
    "ExposeHeaders": ["ETag"]
    }
    ]

    ExposeHeaders is the one that fails silently. Without it the upload returns a perfectly good 200 and the browser simply cannot read the ETag back, so the file is rejected with nothing in the bucket’s logs to explain why.

  4. Check Path-style addressing before connecting. It is on by default, and that default is right for almost everything — most S3-compatible providers require it. AWS itself does not: turn it off for a real AWS bucket.

  5. Connect it, then press Test. Connecting writes and reads back a test object first, so wrong details are caught here rather than on somebody’s first upload. A green Direct uploads is the CORS rule working; Uploads via ANW means the test could not read the ETag — the files still arrive, and the file library works either way.

The connect dialog: provider, endpoint, bucket and credentialsOpen /a/settings/organization in the app
The connect dialog: provider, endpoint, bucket and credentialsThe connect dialog: provider, endpoint, bucket and credentials

Most S3-compatible providers work unchanged. Two things to expect:

  • The region is often a dummy. Infomaniak documents us-east-1 for data held in Switzerland. Type whatever their documentation says; it is stored verbatim and never inferred.
  • Some cannot do Direct uploads at all. OpenStack Swift — which Infomaniak’s S3 API runs on — cannot expose ETag to a browser, so those connections stay on the proxied lane however the bucket is configured. That is not a misconfiguration and there is nothing to fix.

Nextcloud, ownCloud and anything else speaking WebDAV. The connection authenticates with a username and password over Basic auth.

  1. Create a dedicated login, or an app password on an existing account. On a server with two-factor authentication an app password is usually the only credential that will work over Basic auth at all — and a separate one can be revoked without disturbing anything else.

  2. Find the base path. It is the path under the server root where files should live, not the whole URL. On Nextcloud it looks like /remote.php/dav/files/your-username, optionally with a folder under it. Leave it empty to use the root.

    It must start with / and contain only letters, digits, dots, dashes and slashes.

  3. Connect it. On connect the platform checks that it can reach the server with those credentials and that the base path is a folder. The check only reads — it writes nothing to your drive. Whether the login may write is found out by the first real upload, which says plainly if the server refuses it. A failure at connect names what the server refused; a base path that does not exist yet must be created on the server first.

  4. Expect Uploads via ANW. WebDAV has no pre-authorised upload link a browser can use, so there is no Direct-uploads lane to enable.

A connected WebDAV server is not used as hidden storage behind the file library. It is a drive your organisation already works in, so the file manager shows the drive itself, live, with the folders and files already on it — and nothing the platform keeps about it. The drive and the platform’s own storage are never mixed in one view.

  • You can upload, download, create a new folder, rename and move. A project’s files go in a Projects/<project title> folder on the drive, created the first time something is saved there.
  • Nothing is overwritten unless you say so. Uploading a file whose name already exists asks whether to replace it, keep both or skip it, and a move or rename onto an existing name is refused.
  • Deleting asks first, says what a folder holds before it goes, and needs the file-management permission. It deletes from the drive itself: the platform’s trash does not apply, though your drive may keep its own.
  • Starring, sharing, history and the platform’s trash belong to the platform’s own storage and are not available on a drive.
  • The usage bar is not shown: your plan’s storage allowance says nothing about the space on your own server.

A workspace belongs to no single organisation, so it has no drive of its own. An organisation with a connected WebDAV drive can lend it to a workspace, beside the workspace’s Google Drive link, which it does not change.

Lending needs someone who is both a coordinator of the workspace and holds the storage permission in the lending organisation. It is offered when the workspace is created, and later under the workspace’s Settings → Storage. The workspace then gets one folder of the drive, Workspaces/<workspace title> (…), which its members open under Files: everyone in the workspace, from any organisation, can open it; coordinators and partners also upload and rename; only coordinators delete.

Either side can end it. The workspace’s coordinator can Stop lending there, and the lending organisation can Take back a drive from its storage settings, under Lent to workspaces — without being a member of the workspace. Nothing is deleted either way: the folder stays on your drive. A lent drive also stops being available while the lending organisation is off the Org plan, and it cannot be lent to a joint proposal.

A connected backend shows one of two labels.

Direct uploads — files go straight from your browser to your bucket. Fastest, and the platform never handles the bytes.

Uploads via ANW — files are routed through the platform on their way to your storage. Slower for large files, identical in every other respect, and the file still ends up in your own bucket.

WebDAV is always the second one, and no amount of configuration changes that. WebDAV has no concept of a pre-authorised upload link a browser can use, so there is nothing to enable. It is a property of the protocol, not of your server.

For S3, the lane depends on your bucket’s CORS configuration, and there is a Test button that settles it. The test has to run in your browser and cannot be done for you on the server: a server does not enforce CORS, so a server-side check reports success for a bucket no browser can actually reach. Some providers also cannot expose the response header the test needs through their S3 API at all — OpenStack Swift, which Infomaniak uses, is one, so those connections stay on the proxied lane no matter how the bucket is configured.

If the test fails, nothing is broken. You are on the proxied lane; fixing the bucket’s CORS rules and testing again moves you to direct uploads.

Some files are deliberately kept on platform storage no matter what your organisation has connected:

  • Verification documents. They are evidence about your organisation held for compliance, so the subject of that evidence must not be able to delete them.
  • Anything published publicly — organisation page images, post assets and the renditions social networks fetch. A private bucket would break those the moment someone shared a link.

A video on a project update is not stored here at all: it is uploaded to your organisation’s own YouTube channel or Facebook Page. The Video provider card, on the same Storage tab, chooses which. Only one is used at a time, and only the organisation’s admins can change it.

Where an organisation chooses YouTube or Facebook for update videosOpen /a/settings/organization in the app
Where an organisation chooses YouTube or Facebook for update videosWhere an organisation chooses YouTube or Facebook for update videos
Provider Takes video on Who can watch
Facebook Public updates only Anyone — it appears on your Page as soon as it is uploaded
YouTube Updates and evidence Public and listed on your channel for a public update you publish; otherwise only people with the link

Connect the account first. YouTube is connected on the card itself, with Connect YouTube and a Google sign-in. Facebook is the Page your organisation connected for posting: the card sends you to Settings → Integrations to connect it. A provider that is not connected cannot be chosen.

Without a choice, Facebook is used if it is connected, otherwise YouTube. The same applies when the chosen account is disconnected later.

Three things follow from how YouTube is set:

  • Its setting is decided when the upload starts. A video uploaded to a draft stays link-only after the update is published; change it in YouTube Studio.
  • Evidence videos are link-only unless the person uploading makes one public.
  • A partner’s video in a joint project is always link-only, because partners do not publish.

Switching provider changes where new videos go. Videos already uploaded stay where they are.

https://actionnetwork.world/a/settings/organization

Something wrong on this page? Report it