JUDLEX can use your firm's own cloud account (Google Drive, Dropbox or a server of your own) for two things: a backup that runs by itself, encrypted if you choose, and sharing a matter or a case file with a colleague without exporting and importing it by hand.
What leaves the computer, and what does not
What you share with a colleague is always encrypted on this computer before it leaves: the cloud service stores envelopes it cannot open, with names that give nothing away.
The backup is encrypted or not depending on what you choose when you turn it on, and by default it is unencrypted. Unencrypted, its files can be seen and downloaded from your cloud's website; encrypted, nobody else can read it, but if you lose the password and the code nothing can be restored. Both sides are explained in The cloud backup.
What it uploads goes straight from your computer to your account. It does not go through JUDLEX's servers, encrypted or unencrypted. The only thing our server passes between the computers on the same licence is the public part of each computer's key, which is used to encrypt for that computer and cannot open anything.
Where to find it
In Settings, on the Data tab, under The firm's cloud, below On this computer. In the Professional section it starts with this computer's security fingerprint (see Sharing); then come four parts:
Connections: the accounts or servers you have connected.
Cloud backup: whether it is on, where it goes, when the last one ran and how often it runs. See The cloud backup.
Restore from the cloud: for a new computer, or to go back. See Restore the firm from the cloud.
What you have shared: what this computer has sent to a colleague and is still in the cloud. Professional section only.
At the top you also see This computer's security fingerprint: five groups of five digits that a colleague compares with the one on their screen before trusting this computer.
Adding a connection
Click Add a connection, choose the service and follow the matching guide:
S3-compatible storage (Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO…)
If an IT person runs the server, what to ask them for, and for them, the technical guide.
When you save a connection, JUDLEX tests it straight away: it uploads an envelope, downloads it, checks that it is the same and deletes it. That way you know today that it works, rather than on the day you need the backup.
If something is missing for the Connect and test button, the line above it says what ("Missing: the user · the password").
If the test fails, the connection has already been saved and the window stays open, with your details and the reason in red. Correct whatever is needed and click Connect and test again: that same connection is changed, no new one is created. If you would rather fix it later (for example, because your IT person still has to install the key), click Save as is and close: the connection shows in the list as Failing (or Sign in again, if what failed was the password or the key), with the reason, and once it is fixed Test is all you need.
What you can do with each connection
Each row has a three-dot menu:
Test: runs the upload, download and delete test again.
Reconnect: when the connection asks you to sign in again (it shows in amber, Sign in again) or when the password has changed. The new password is tested before it is saved: if it does not work, the connection stays as it was. For an SFTP connection with a key, see Reconnecting with a key.
Change the details… (WebDAV, S3 and SFTP): the address, the user, the password or the folder; the new fingerprint of a reinstalled server; the renewed certificate of a NAS. Any secret you leave empty stays as it was. JUDLEX tests with the new details before saving them: if the test fails, nothing changes and you are told in the same window, and Save anyway saves them all the same (useful if you know the server is switched off).
Rename: the name is only there to help you recognise it in the list.
Firm folder…: to receive what is shared with you without links. See Share a matter or a case file with a colleague.
Remove the connection: JUDLEX forgets the password or the permission. It does not delete anything from the cloud: it tells you how many backups and packages are left there, in case you want to delete them yourself from the service's website. To delete the backup from JUDLEX, use Delete the backup from the cloud… before removing the connection.
Each connection's status shows in its row: Works in green, Sign in again in amber, or Failing, with the reason underneath; hover over it to read it in full.
With a read-only licence
If the licence expires, you can still view and restore what is already in the cloud, but no new backups are uploaded and nothing can be shared.