Integrations
Integrations connects your document systems to Judicio and keeps chosen folders mirrored between them. The page is headed Integrations, subtitled Connect your document systems to sync folders with Judicio.
Open integrations (opens in a new tab)Who can use it
Integrations works on any plan, wherever document-system sync is turned on for your workspace. What you see depends on your account.
| Account | What you get |
|---|---|
| Personal account (trial, Starter or Professional, or an Organisation plan whose team isn't set up yet) | The full page. You connect and manage your own document-system accounts |
| Organisation admin | The full page. You manage your own accounts, and also your organisation's Microsoft connections that use organisation-wide admin approval. Only an admin can reconnect one of those |
| Team member on an Organisation plan | A screen saying Only your organization's admin can manage these settings, with Back to settings |
The page appears in the settings rail for personal accounts and organisation admins wherever document-system sync is turned on for your deployment. If sync isn't turned on for your own workspace yet, the page shows no cards, only the line Cloud folder sync isn't available for your workspace yet.
A connection is private to the person who connected it. Only that person can browse its folders, reconnect it, change its cap or disconnect it. An organisation admin can't manage another person's connection either.
Once a folder is synced, anyone who can edit its project can work in it. Their saved changes reach the cloud through the account that set up the sync.
Anyone who can edit a project can also connect an account and sync a folder without this page, team members included. Open the project in the File Library and press Import. Choose a provider and account, then its sync action. Setup stays inside the explorer: choose the account, select one or more folders, and review their names at Project root before pressing Import and sync. Sync is available only when the selected connection supports it. An existing folder can be turned into a synced one with Convert to synced folder… on its menu.
The connection cards
The page has a card for each system: SharePoint, OneDrive, Google Drive and DocuSign. Each card carries the system's logo, its name and a status badge. If you have connected more than one account for the same system, each account gets its own card.
| Badge | What it means |
|---|---|
| Not connected | No connection for this system yet |
| Connected | The connection is live |
| Needs reconnect | The connection has lost its authorisation and has stopped working until you renew it |
| Disabled | The connection has been turned off |
Connecting one
An unconnected card carries one line and one button. SharePoint, OneDrive and Google Drive read Mirror the system's folders into Judicio projects and push work products back, with Connect. DocuSign reads Pull completed DocuSign envelopes into a Judicio folder on a schedule, with its own Connect.
Connect opens that provider's sign-in in a separate window. When it finishes, the card fills in. The new connection belongs to you.
A connected document system
| Control | What it does |
|---|---|
| Summary line | Names who connected it, the account it uses, and how many folders are synced |
| Set up synced folder… | Opens the Sync folder wizard described below |
| Sync all | Runs every synced folder on this connection now. Disabled while there are none |
| Reconnect | Appears only on Needs reconnect. Renews the authorisation |
| Disconnect | Ends the connection, after a confirmation |
| Credit cap (total credits) | A number field with Save beside it, shown on connections you manage. Syncing on the account pauses once it has used this many credits in total. The count covers the connection's whole life and never resets with your billing period; the line under the field shows how many it has used so far. Leave the field empty for no cap, or clear it and save to remove a cap. Save stays disabled until you change the value. Confirms with Credit cap updated, or Credit cap removed when you clear it |
Disconnect opens a modal titled after the system, for example Disconnect SharePoint?, which states what happens: every synced folder on the connection stops syncing, files already in Judicio stay, and nothing in the source system is touched. Cancel backs out, Disconnect goes ahead.
When a synced folder pauses
A synced folder pauses when the connection reaches its credit cap. A folder that was given a cap of its own when it was set up also pauses at that cap; the wizard no longer offers one. The person who connected the account and your organisation's admins get a Sync Paused notification that opens the folder in the File Library.
Raising the cap doesn't restart the folder by itself. To start it again:
- Raise or clear the connection's credit cap on this page. Raise credit cap… on the paused folder's menu brings you here.
- In the File Library, open the synced folder's menu and choose Resume sync. You need edit access to the project.
If the connection or the folder is still over its cap, the folder pauses again on its next run. Buying more credits doesn't resume a folder that hit its cap.
A folder can also pause when your account moves between workspaces, for example when you upgrade to or leave the Organization plan, and the folder's connection stays in the other workspace. Resume sync can't restart that folder. It shows This folder's cloud connection is not in this workspace. Stop syncing the folder and set it up again. Do exactly that: stop syncing the folder, then set it up again with a connection in your current workspace.
DocuSign
DocuSign pulls completed envelopes in. It is one-way, and it does not use the folder wizard, because envelopes are not a folder tree.
Each DocuSign connection pulls into its own destination folder, and only the person who connected it can change its settings. To choose a destination, you need edit access to that project.
| Control | What it does |
|---|---|
| Enable envelope polling | Turns the scheduled pull on and off, and saves straight away. Nothing is pulled until a destination project and folder are also saved |
| Destination project | The project completed envelopes land in |
| Destination folder | The folder inside that project. Stays disabled until a project is chosen, and resets when you change project |
| Sender filter (optional) | Restricts the pull to one sender. Placeholder: name@example.com |
| Save | Writes the filter, and the destination if you changed it. Confirms with DocuSign settings saved. With polling on, the first pull starts shortly after the destination is saved |
| Disconnect | Stops polling, after a confirmation. Files already in Judicio stay |
The Sync folder wizard
Set up synced folder… opens a modal titled Sync folder. It runs four steps, and the footer shows dots and the name of the step you are on. Back moves you one step back, and the primary button carries the step's own label.
Opened from a card, the wizard already knows which account to use, so it starts at the second step. The first step appears when you start from the File Library without a connected account.
Provider
Headed Choose a document system, with the line Choose your connected account. Project editors will sync through this account. Each account you have connected is its own selectable row, showing the system's logo, its name, the account's email and a badge:
- Connected - the account is ready to sync.
- Needs reconnect - the account can't be selected until you renew it.
- Sync coming soon - the account is connected, but two-way sync isn't switched on for this system yet, so it can't be selected.
Below each system's accounts is a Connect button. Once you have an account for that system, it reads Connect another account.
Continue moves on.
Remote folders
Headed Select remote folders.
Lists above the tree choose where to browse. SharePoint has two: Site, placeholder Choose a site, and Document library, which stays disabled until a site is chosen. OneDrive and Google Drive have one, Drive. Judicio picks the first site and the first drive for you, so the tree loads straight away. Changing either clears the folders you had ticked, because a synced folder belongs to one drive.
The tree lists what the drive holds and opens a folder in place when you expand it. Only folders can be ticked; the line above the tree reads Sync includes every file inside a selected folder. Files cannot be selected as sync roots. A folder inside one you have ticked is marked Included, and a folder that is already synced is marked Already synced. Neither can be ticked on its own. A counter shows how many folders are selected, Clear all unticks them and Refresh reads the tree again. A long folder ends with Load more.
Tick every folder you want mirrored, then Continue.
Review and confirm
Headed Review & confirm, with a line counting how many remote folders will be mirrored at the project root.
Opened from this page, the step first asks where the folders go: Sync into project, placeholder Select a project. It lists your active projects by name, and you can type to search them. Start sync stays unavailable until you pick one, and you need edit access to that project. If you have no active projects, the step asks you to create one first. If you have more projects than the list can hold, a note says so; to sync into a project that isn't listed, start from that project's File Library.
The step names the account the folders come from, as Source account, and gives each folder a field for the name it will have in Judicio: Folder at project root, followed by the folder's cloud path. The names apply in Judicio only; the cloud folders keep theirs. A name takes 1 to 255 characters, none of \ / : * ? " < > |, and cannot repeat another folder at the project root. If a name breaks a rule, a warning says so and Start sync stays unavailable until it is fixed.
A checkbox asks you to confirm what the sync does, and the wizard will not proceed until it is ticked. For a two-way sync it reads I understand that project editors can update the cloud through my account and normal usage charges apply. Stopping sync keeps both copies. For a one-way sync it reads I understand that this copies cloud changes into Judicio and normal usage charges apply. Judicio changes are not sent to the cloud.
Judicio checks that the sync can start while you wait, showing Checking sync readiness…. If the check fails, a warning says why and Retry readiness check runs it again; Start sync stays unavailable until the check passes.
Start sync commits.
Initial sync
Headed Initial sync, with the line You can keep working. Sync and file processing continue in the background.
Each synced folder has a card showing its status. Once the run is recorded, the card names the account and the destination, counts the files received and sent and, separately, how many are ready, still processing or need attention, and lists the files. Checking status means the saved outcome has not yet been confirmed; it does not mean the run succeeded, and Check status reads it again. When a run has finished, Show in File Library closes the wizard and opens what it brought in. A file that needs attention offers its own way to recover; see Uploading files.
While the first pull is running the modal cannot be closed with the close control or the Escape key, and the button reads Run in background, which lets you leave it running and get on with something else. When no transfer run is live, Done closes the modal. Check each card, and View uploads in the File Library, for its actual result: closing the modal does not establish that every file has completed processing.
Next steps
- Organisation settings - team administration, for Organisation plan admins.
- File Library - where the mirrored files land.
- Credits explained - what a large first pull costs.