Academy
Technical · Course T6

Lesson 2 of 4

WeBox: files out, files back in

8 min read
In this lesson you'll learn to
  • Distribute files to devices via recursive policy assignment
  • Configure per-policy WeBox behavior — downloads, storage, passcode
  • Set up device-upload folders for field data collection

WeBox is the fleet's file system: a Drive-style console where admins organize content and push it to devices — and, in the other direction, where devices upload field data back. Two tabs, two flows.

Files out: the WeBox Files tab

The explorer works like any cloud drive — folder tree on the left, list or grid on the right, breadcrumbs, search, upload. The constraints worth quoting: documents, images, audio, video, and zip archives are accepted (PDF, Office formats, PNG/JPEG, MP3, MP4 and friends), with a 500 MB default per-file limit that plans can override.

Delivery is policy assignment. From any file or folder's menu, Assign Policies opens a drag-and-drop dialog — available policies on one side, assigned on the other, with search and select-all. Two behaviors matter:

  • Folder assignment is recursive — everything inside ships. Files added later may need a re-assign, which explains most "devices only see some files" tickets.
  • Delivery rides a push notification: device online + WeBox app present + right policy = files appear. That's also the troubleshooting checklist, in order.

The Policies view flips the lens: pick a policy card and see only its content, upload straight into it, and open its settings.

Controlling the device experience

The per-policy settings sheet (gear icon in the policy-filtered view) decides what device users can do with delivered content:

  • Allow Download / File View / Open With — export, preview, and hand-off to other apps, each separately toggleable.
  • Download network restrictionWi-Fi Only or any network; the lever for sensitive or heavy content.
  • Storage services — besides WeBox itself, a policy can surface SD Card, Google Drive, Amazon S3, or Dropbox as backends.
  • Passcode protection — a 6-character code gating the WeBox app, with an expiry window from 1 minute to an hour.

Files in: the Device Uploads tab

The reverse flow is field data collection — photos, signed forms, inspection reports. Two folder kinds:

  • Shared folders — every enrolled device can upload. Fleet-wide dropboxes.
  • Group folders — scoped to selected policies; only those devices can upload.

Each folder configures an upload size limit and an optional signature requirement — the digital-signature-with-every-upload option that compliance-heavy customers ask about unprompted. Browsing uploads supports date-range filters, search, view/download, and per-file deletion.

The plan-gate map

WeBox surfaces plan gating in three places: the Upload button (greys out with a "not available in your current plan" tooltip), file deletion, and the upload size ceiling. When something is missing here, check the plan before filing a bug — it's the platform→type→plan triage from Policy Mastery, applied to a suite product.

Knowledge check
1. How do files actually reach devices after you upload them to WeBox?
2. A customer wants field technicians to send inspection photos back to HQ, visible only for their region's policy. What do you build?
3. Sensitive documents must not leave WeBox on cellular connections. Which setting?