Relution Files Android

Relution provides the ability to integrate local file shares, also known as network drives, on Android devices using SMB and WebDAV. By connecting to school or enterprise server environments, users can access relevant documents and content and securely store data and work results on a central server.


Advantages of Relution Files

Data should not be stored in unsecured cloud services with servers outside the EU when GDPR compliance is required. It is also advisable not to store data directly on devices, especially when devices are used by multiple users. Storing documents on on-premise servers via Relution Files ensures data security and 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

Using a managed configuration set by an administrator in the Relution Portal removes almost all setup steps for end users. This enables seamless access to the file share.

With the Relution File Shares configuration inside a policy, a WebDAV or SMB connection can be prepared for use. On Android, the configuration is only available in Android Enterprise policies and can be added once per policy. If a policy contains the configuration, Relution automatically installs the Relution Files app as a mandatory app and transfers the required managed configuration to it. A separate distribution of the app is not required. If Relution Files is also listed in Manage apps →, the settings made there apply (e.g. installation type).

In the configuration form, the General section lists all shares under Shares with the columns Name, Protocol, Path, Username and SSO; a check mark in the SSO column marks shares for which the option Use logged in Relution User is enabled. In the context menu of a share, Edit changes the share and Delete removes it; several selected shares are removed together via Delete in the context menu of the list. In a policy version that has already been published, the list is read-only.

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). WebDAV connections always use HTTPS (the prefix https:// is predefined). For a new share, no protocol is selected yet; the corresponding prefix appears in the Path field as soon as SMB or WEBDAV is selected. Placeholders such as ${user.name} can be used in name, path, username and password and simplify the login process.

In addition, the option Use logged in Relution User can be enabled for the share. The credentials of the Relution user logged in on the device are then used, and the Username and Password fields are locked. If the option is disabled, a fixed Username and Password can be stored. As of Relution 26.5.5, the Password field shows a stored password only in masked form (*****); if the field is left unchanged, the stored password is kept. If an existing share is switched to Use logged in Relution User, Relution deletes the previously stored password when saving. When switching back to fixed credentials later, the password therefore has to be entered again. With the option enabled, a value in the Username field is also discarded when the share is confirmed.

In the dialog, Add adds the share to the list; the button becomes active as soon as the Path field is filled in. When a share is edited, the dialog shows its path as the title and the button is labelled Confirm. Cancel closes the dialog without changes. The shares are only saved to the policy with Save.

Below the form, the collapsible Available placeholders area lists the user placeholders of this configuration: ${user.email}, ${user.fullname}, ${user.givenName}, ${user.name}, ${user.organizationUuid}, ${user.phone}, ${user.salutation}, ${user.surname} and ${user.custom1} to ${user.custom10}. Clicking an entry copies it to the clipboard. Relution replaces the placeholders for each device with the data of the assigned user. More information: Advanced placeholders →

Relution File Shares Configuration

Example: Personal directory on the file server

Each user is to find their personal directory on the SMB file server fileserver.example.com in Relution Files. The file server uses the same user accounts as Relution, for example via a shared Active Directory. For this, the configuration contains a share with the following values:

  • Name: My files
  • Protocol: SMB
  • Path: fileserver.example.com/home/${user.name}
  • Use logged in Relution User: enabled

On each device, Relution Files shows the share My files with the directory smb://fileserver.example.com/home/<username> of the assigned user; the login uses the credentials of the Relution user logged in on the device.

How helpful was this article?