Record folders

Each record can be bound to its own folder in your connected storage. Once bound, the files in that folder appear on the record, and anything uploaded to the record lands in the folder: the same files, reachable from either side.

Binding. A customer's folder is chosen on the customer. Where folders already exist and are named after your customers, DealJourney can match them up rather than making you pick each one by hand. Matching by name is a suggestion and not a guarantee, so it is worth checking a few before trusting the rest.

Keeping up with the folder. Changes made on the storage side are picked up on their own, roughly every hour, so a file a colleague drops straight into the folder turns up on the record without anyone opening it. A file renamed in storage keeps its place and shows its new name. A file deleted or moved out of the folder stops being listed here, and if it is put back it returns to the same place rather than arriving as a second copy. Sync also runs the moment you open the record, so there is nothing to wait for when you are looking at it.

If the wrong folder is attached, change the binding on the record. The folder itself is untouched: binding is a pointer, so re-pointing it moves nothing and deletes nothing.

Two folders for one customer happens where somebody created a second one in the drive with a slightly different name. Fix it in the storage system by merging the folders, then bind the record to the survivor. Doing it the other way round leaves files stranded in a folder nothing points at.

When documents do not appear, work through it in this order: is storage connected at all, is a folder bound to this record, and can *you* open that folder in the storage system? The last one catches most of it: access is still governed by the drive's own permissions, so a folder you cannot reach there will look empty here.

Uploads are checked before they are accepted, and a refused upload will say so rather than failing quietly.