Structure of the UpReach Cloud
Chronologically, the Cloud structure can be separated into “before the deployment” and “during/after the deployment”.
Contents
Client & event data (before deployment)
This data is especially relevant while setting up the Cloud for your deployment.
Client
This is your company account in the UpReach Cloud. It contains the basic data of your organization and all of your data in the UpReach Cloud is connected to it to make sure only you can access it (and nobody else!). Data which is not connected to your Client account will not be accessible for you. One Client account can have multiple Deployments and Devices assigned all of which can be used only by you.
Deployment
A Deployment is basically an event/project with one UpReach Device (e.g. Photo System). It is not your booking with UpReach though - if you have 1 booking including multiple events/projects/devices, you will have multiple Deployments, too: 1 Deployment for every event/project/device. All data generated during a Deployment will be associated with it, based on the Deployment dates. It is important to set up your Deployment with the correct start & end dates & times to make sure all data captured during your event will be connected to the right Deployment. One Deployment can have multiple Configurations assigned, but just one Device (e.g. Photo System).
Configuration
A Configuration (abbr. “Config”) is the entire set of settings, information & designs creating a photo experience on the UpReach devices. It contains all information for the user flow in the UpReach App such as capture mode settings, layouts and sharing texts, among others. It can be changed at any time online in the UpReach Cloud, even during usage on a live Deployment. Changes are automatically synced live to the App. One Configuration can be assigned to multiple Deployments at once, but just one Client.
Device
Capture Devices are UpReach’s hardware products such as Photo Systems, Camera Arrays or Hashtag Printers (among others). 1 Device can be assigned to 1 client. Also, it can be assigned to multiple Deployments - but only one Deployment at a time, i.e. the Deployment time frames cannot overlap each other if they use the same Device!