Configure an app's storage browser

Limit visible connections, allowed operations, and the target for imported snapshots.

Storage Browser lets app users browse permitted connected storage and optionally import file snapshots into the app's own file list. Configure its authoring policy in Properties under Storage settings.

Choose connections

Select All viewer-visible storage connections when each signed-in viewer should browse the connections available to them. Select Selected connections to allow only the listed ids, then check the appropriate connections.

Selected connections remain subject to the viewer's permissions. Choosing a connection in the definition does not give another viewer access to it. Each viewer can access only their own and tenant connections that the platform authorizes for that context.

The editor marks connections with non-active status. A previously selected id that is no longer available appears as Unavailable connection and can be removed. If the connection list cannot load, Retry rather than treating an empty picker as proof that no connections exist.

Choose operations

Enable only the operations the app needs: create file, create folder, upload, rename, delete, copy, move, and import. These choices narrow the component's interface; the provider and current user must still support and permit the operation.

For example, a document-selection app may need browse and import without offering delete or move. A storage-management app can expose broader operations to its authorized users.

Set the import target

Under Import snapshots into, choose the app's File Upload/File list component. The target receives dragged storage snapshots. No App file list leaves no configured app destination for that handoff.

Imports copy a snapshot into the app's document workflow; they do not turn the app into a live two-way mirror of the source item. A later source change needs a new import or the app's documented synchronization path.

Save the app and test with the intended viewer account. The owner's available connection list alone cannot prove another viewer's access. See Storage, File Upload, and Post-upload behavior.