en	File storage, which acts as an entry root point to a file-based structure. See it like a drive or a hard drive volume in your local machine.

en	Disabling the storage will result in removing it from any listings in the backend. Existing file relations will still exist.

en	If you set up a file storage, it will show up on any folder lists, thus allowing to basically browse through the files in this file repository. If you set this checkbox, this storage will be excluded from any listings in the backend. Any existing file references will still exist further.

en	The visible identifier for this file storage.

en	The label entered here will be shown as the name for the entry point in the TYPO Backend. Be sure to make it descriptive and logical for your editors.

en	A description of this storage.

en	This description field is used to explain e.g. the location of the storage, also what this storage is meant for or what it contains.

en	Choose the driver as the technical backbone of the storage. Once you've chosen a driver, and saved it, additional configuration will show up.

en	The driver is the technical background of a storage, and thus also defines whether the location of the storage is local (= on the same machine as this TYPO3 installation) or remote like a WebDAV server connection. Search for extensions in the TYPO3 Extension Repository that extend this driver list.

en	Defines the directory on this storage to be used to save temporary files like resized images.

en	If set, backend users can browse through this storage. Otherwise it will show up as a unselectable item in the list.

en	If set, then the files in this storage can be linked directly from the outside world. If this is not set, make sure to provide additional possibilities to access the files in this storage.

en	If set, then users are allowed to modify, add, delete files/folders on this storage.

en	This flag is usually set. If TYPO3 cannot connect to this storage (because it maybe temporary down), then the flag will be checked, and the storage will behave like it is non-browsable in the TYPO3 backend. The admin needs to manually activate it again if it was offline.