Skip to main content

How storage works

Buckets and objects​

A bucket is a container in one app. An object is one file in a bucket, identified by a path you choose. Paths can include slashes, such as invoices/2026/march.pdf.

Each bucket has:

  • a default visibility, private or public;
  • a maximum file size and an optional list of allowed file types;
  • a category, assets or attachments, which sets its starting access policy;
  • a provider, S3 or SharePoint, fixed when the bucket is created.

Each object has its file content, path, size, type, and optional metadata. An object's visibility always follows its bucket; to change it, change the bucket's visibility.

Isolation​

Files are stored under your site, app, and bucket, so one site's files are never reachable from another site.

Visibility​

A file without its own visibility uses the bucket's. Anyone can download a public file without signing in. A private file can only be downloaded by a signed-in caller whom the bucket's policy allows to read it.

Providers​

S3 is the default. SharePoint adds in-browser viewing and editing of Office documents. See Providers.

Access​

Bucket administration requires an organization owner or admin, or another cloud user with access to the site. Every file operation also checks the bucket's access policy. See Security and limits.

Quotas​

You can set an optional maximum total size or object count on a bucket. Usage is recalculated periodically rather than on every upload, so a quota flags a bucket that has grown past its limit but does not block the next upload.

Listing and browsing​

  • List returns files that match filters across the whole bucket — see the filter reference.
  • Browse returns one folder level at a time, like a file explorer, and always requires sign-in.

Copy and move​

Copy and move work within one app and one provider. To get a file from an S3 bucket into a SharePoint bucket, or the other way round, download it and upload it to a bucket that uses the other provider.