Push a file to every device provisioned under a blueprint for a consistent content management experience. Esper’s file management system allows you to keep track of the files deployed to all of your devices.
In this article:
Adding Files to a blueprint
In a blueprint, go to Files and press Add File. Use one of the following methods to upload the file:
- Drag and drop the file into the upload area
- Press Select to upload the file from your computer
- Press Browse Esper Cloud to select files already uploaded to the Esper Console
Files are stored in the default path /storage/emulated/0/Documents in the device. See Understanding Android Storage Permissions and Saving to the Correct File Path for more information.
To edit file information, click on the ellipsis (...). You’ll be able to add tags and descriptions.
Any tags will also appear in the Content Management section.
Understanding Android Storage Permissions
The version your device runs on will determine your Android device's storage permissions. Here is a breakdown of the version and their storage permissions:
Storage Type | Android Version Compatibility |
Internal Storage |
Android 9 and below: Available Android 10: AvailableAndroid 11 and above: The root folder and Downloads directory can’t be accessed. |
Removable Storage |
Learn more about Android Storage Permissions.
File Sync Scenarios
Esper-provisioned devices accept files from three sources:
- From Esper Cloud, when you add a file to the device through a blueprint or the console’s Content Management section.
- From a Local source, such as a USB drive. Files uploaded this way are not treated as part of the blueprint, nor do they appear in Content Management. Esper does not keep track of this file.
- From Esper Cloud (Locally added). A file that is added to the device locally and then uploaded to Esper. Once this file is part of a blueprint, you can keep track of it through Esper.
- From Any of the previously listed file sources.
Common Scenarios
Before Updating a Device’s Blueprint (or Blueprint Version) | During Update | After Updating a Device’s Blueprint (or Blueprint Version) | |||
Present in the Previous Blueprint or Blueprint Version? | Present on Device According to Esper? | Previous File Source | Do the files match? | Result | New File Source (according to Esper) |
Yes | No | Esper Cloud | Yes | Transfers a file to the device. | Esper Cloud |
Yes | No | Esper Cloud | No | Transfers a file to the device. | Esper Cloud |
Yes | No | Esper Cloud (Locally added) | Yes | Transfers a file to the device. | Esper Cloud |
Yes | No | Esper Cloud (Locally added) | No | Transfers a file to the device. | Esper Cloud. |
Yes | No | Local | Yes | Transfers a file to the device. | Esper Cloud |
Yes | No | Local | No | Transfers a file to the device. | Esper Cloud |
Uncommon Scenarios
Before Updating a Device’s Blueprint (or Blueprint Version) | During Update | After Updating a Device’s Blueprint (or Blueprint Version) | |||
Present in the Previous Blueprint or Blueprint Version? | Present on Device According to Esper? | Previous File Source | Do the files match? | Result | New File Source (according to Esper) |
Yes | Yes | Esper Cloud | Yes | Do nothing. | Esper Cloud |
Yes | Yes | Esper Cloud | No | Overwrite the file. | Esper Cloud |
Yes | Yes | Esper Cloud (Locally added) | Yes | Do nothing. | Esper Cloud - Local |
Yes | Yes | Esper Cloud (Locally added) | No | Overwrite the file. | Esper Cloud - Local |
Yes | Yes | Local | Yes | Keeps a copy of the local file to replace if needed. | Esper Cloud - Local |
Yes | Yes | Local | No | Overwrites the file and keeps a copy of the local file to replace if needed. | Esper Cloud - Local |
Scenarios for Files Not Present in the Blueprint
Once a file is removed from a blueprint and restored as a local file, Esper no longer keeps track of it.
Before Updating a Device’s Blueprint (or Blueprint Version) | During Update | After Updating a Device’s Blueprint (or Blueprint Version) | |||
Present in the Previous Blueprint or Blueprint Version? | Present on Device According to Esper? | Previous File Source | Do the files match? | Result | New File Source (according to Esper) |
No | Yes | Esper Cloud | Yes | Delete the file. | None |
No | Yes | Esper Cloud | No | Delete the file. | None |
No | Yes | Esper Cloud (Locally added) | Yes | Restores the local file. | None |
No | Yes | Esper Cloud (Locally added) | No | Restores the local file. | None |
No | Yes | Local | Yes | No change. | None |
Esper doesn’t keep track of local files that aren’t added to a blueprint.