Configuring the document storage provider

This article shows administrators how to configure which provider MobilityManager uses to store uploaded files, and which settings each provider needs.

Who can change storage settings

Storage configuration requires the settings:manage permission, typically held by SystemAdmin. There is a single, platform-wide storage configuration, and only one provider is active at a time. If no configuration exists yet, the platform starts with the Local provider and a default base folder.

How secrets are handled

Sensitive values — Azure connection strings, S3 access and secret keys — are never typed directly into the storage settings. Instead you supply a secret reference: the configuration key under which the real secret is provided (for example through environment variables or a secret store). The platform resolves the reference at runtime. If a reference cannot be resolved, saving fails with a clear message so you never end up with a half-configured provider.

Configure the Local provider

1. Set the provider to Local.
2. Enter a base path for stored files. This is required. An absolute path is used as-is; a relative path is rooted under the server's temporary directory.
3. Save. The platform verifies the folder exists (creating it if needed) and confirms it is writable with a quick write-and-delete probe before accepting the setting.

Configure the Azure Blob provider

1. Set the provider to AzureBlob.
2. Enter the container name (required).
3. Enter the connection string secret reference (required) — the config key that holds your Azure Storage connection string.
4. Optionally enter a blob service URI.
5. Save. The container is created with no public access on first use if it does not already exist.

Configure the S3 provider

1. Set the provider to S3.
2. Enter the bucket name and region (both required).
3. Enter the access key secret reference and secret key secret reference (both required).
4. Optionally enter a service URL for S3-compatible stores such as MinIO; this enables path-style addressing.
5. Save.

Warning: Switching providers changes where new files are written and where downloads are read from. The platform keeps a single active configuration and does not migrate existing files between providers. Plan a provider change carefully so previously stored files remain reachable.

Note: When you switch provider, fields for the other providers are cleared. Re-enter the details if you switch back. Encryption settings are handled separately from provider choice — see the encryption article.

Related

• Where documents are stored: Local, Azure Blob, and S3 providers
• Encryption at rest and the encryption key
• How documents work across the platform
• Tenant scoping and document isolation