Relution Files

For iOS, Relution offers the possibility to integrate local file shares, also called network drives, via SMB and WebDAV. By connecting to e.g. school or corporate server solutions, relevant documents and content can be accessed and data and work results can be stored securely on a central server.


Advantages of Relution Files

Data should not be stored in an unsecured cloud with servers outside the EU if GDPR-compliant work is required. Likewise, it is advisable not to store data directly on devices if devices are used by multiple users. Saving and storing documents on local servers via Relution Files ensures data security and data sovereignty for all users.


Configure local network drives for Relution Files

Local file shares can be set up in two ways: manually in the Relution Files app or automatically via a policy in Relution.

The manual setup is described in the app documentation: Files →

Automatic configuration of Relution Files via policies

A managed configuration, which the administrator carries out via the Relution Portal, removes almost every hurdle for the end user when setting up the device. In this way, file sharing can be used seamlessly.

A WebDAV or SMB connection can be prepared for use by configuring Relution File Shares in a policy. The configuration is also available for devices with User Enrollment →. If a policy contains the configuration, Relution automatically installs the Relution Files app as a mandatory app. A separate distribution of the app is not required.

Add opens the New share dialog. A configuration can contain several shares; at least one is required for saving. For each share, an optional Name, the Protocol (SMB or WEBDAV) and the Path (mandatory) are specified. Without a name, the last path segment is used. For SMB, the path must contain the actual share (e.g. server/share; the prefix smb:// is predefined in the field). WebDAV connections always use HTTPS (the prefix https:// is predefined in the field).

The option Use logged in Relution User is also available. The credentials of the Relution user logged in on the device are then used, which makes an additional login to the file share unnecessary when using Relution Shared Device →. When the option is enabled, the Username and Password fields are locked, and any values already entered are discarded when the share is confirmed.

Alternatively, for 1:1 devices, the user assigned to the device can log in with their user data. Placeholders such as ${user.name} can be used in the Username field so that each device is configured with the username of the assigned user. Placeholders are also possible in Name, Path and Password, e.g. for personal directories such as server/home/${user.name}. The available placeholders are described under Advanced placeholders →.

The Extension Type field offers two options: Modern (default) and Classic. This setting defines the internally used extension type by Relution Files to integrate the shares into the Files app of iOS/iPadOS. The Classic type should be used in rare cases where the default Modern type does not work as expected (e.g. iOS 18+ has a bug for Shared iPads where the Modern extension type does not display files). For Shared iPads, the dialog explicitly recommends Classic.

SMB and DFS shares can also be provided as a WebDAV share via the Relution Files Bridge →.

Top