FILE STORAGE

Shared file storage for your team

One directory structure for applications and teams that need shared files. Plan clients, permissions and concurrent access together.

Shared paths, coordinated access

Clients work with files and folders through a supported network filesystem protocol. Confirm protocol and locking behavior against your applications.

Client A
Client B/shared
/projects
/assets

ACCESS PLAN

Example roles to discuss before configuration. Actual permissions depend on the selected protocol and service.

Example access responsibilities
Client	Responsibility
Application	Read and write its own working directory
Backup process	Read protected sources to create copies
Administrator	Manage access and recovery

Keep a shared directory structure for project files and assets. Access rights should follow the responsibilities of each client.

Confirm operating-system support, mount options and behavior when several processes write to the same files.

Keep clients and the share on compatible networks. Latency and bandwidth affect interactive file operations.

An object, a key, an API

A volume connected to your server

THIS STORAGE TYPE

Shared paths, coordinated access

Are NFS and SMB both available?

Protocol support is confirmed for the specific configuration. The catalog does not imply that every file storage service supports both protocols.

Is storage the same as backup?

No. A working copy can be overwritten or deleted. A recovery strategy needs separate copies, retention rules and a tested restore procedure.