File Syncs (Blueprints 2.0 Beta)

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
• Understanding Android Storage Permissions 
• File Sync Scenarios
  • Common Scenarios 
  • Uncommon Scenarios 
  • Scenarios for Files Not Present in the Blueprint

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: 

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. 
• From a Local, 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 

Uncommon Scenarios 

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. 

Esper doesn’t keep track of local files that aren’t added to a blueprint.