Skip to main content

Integrations

Connects DocuFlow to your organisation's Google Workspace and/or Microsoft 365, so that everyone can open files from, and save results to, Google Drive or OneDrive without linking a personal account. You set each one up once, for the whole organisation. Nothing is stored in Google or Microsoft by DocuFlow itself except the files people choose to save.

To open it: open the admin area and select the Integrations tab. There is one card for Google Drive and one for OneDrive, each with its logo, its Enabled switch and a status: Not connected, Connected · not tested yet, Connected · tested <date>, or Needs attention. A card that is switched off and not set up yet shows only "Switch on to set up Google Drive." (or OneDrive) — switch it on and the setup steps and the form appear. A service that is already set up keeps its form even when it is switched off, so you can still fix or remove it.

Connect Google Drive​

You need to be a Google Workspace administrator, and the account you are signed in with to DocuFlow should be that administrator's.

  1. On the Google Drive card, switch Enabled on. In Google Cloud, turn on the Google Drive API for your Cloud project. Then create a service account (it needs no roles) and download its key as a JSON file. The client ID you will need in step 3 is also inside that file.
  2. In the Google Drive card, paste the whole file into Service account key (JSON), type your Workspace domain (for example org.com) into Workspace domain, and select Save. The card then shows a client ID.
  3. In the Google Admin console, go to Security › Access and data control › API controls › Domain-wide delegation. Add a new entry with that client ID and the scope https://www.googleapis.com/auth/drive, and authorise it.
  4. Back in DocuFlow, select Test connection.

What you'll see when it's done: two lines under the card — one about the shared drives DocuFlow can see, one about acting as you. A green tick on both means it works.

Connect OneDrive​

  1. On the OneDrive card, switch Enabled on. In the Azure portal, register an application. Give it these application permissions (not delegated ones): Files.ReadWrite.All and Sites.ReadWrite.All. Create a client secret.
  2. In the OneDrive card, paste the Tenant ID, the Application (client) ID and the Client secret. If you like, also fill in Work e-mail domain (see below). Select Save.
  3. The card now shows a consent link. Open it and approve the permissions for your organisation. This needs a Microsoft 365 administrator.
  4. Back in DocuFlow, select Test connection.

The switches and the lists​

  • Enabled — turns the service on or off for everyone without losing its settings. When it is off, nobody sees its buttons.
  • People can use their own drive — lets each person open and save in their own My Drive or OneDrive. DocuFlow always acts as the signed-in person, using their work e-mail address. If that address isn't one of your organisation's Google or Microsoft accounts, the person is told to ask you — this is the message "Ask your administrator" in the manual's Files chapter.
  • Shared drives / document libraries people may use — this list appears after a successful test. On a later visit, when the last test passed, select Load shared drives (Google) or Load libraries (OneDrive) to see it again; otherwise the card asks you to test the connection first. If the list can't be read, the card says why. Tick the ones people may use, then Save. It means different things for the two services:
    • Google Drive: if nothing is ticked, people see the shared drives they are already members of. Ticking drives only narrows that down — Google still checks each person's own membership, so ticking a drive never gives someone access they don't already have. The list you pick from is read as you, so you must be a Google Workspace administrator.
    • OneDrive: if nothing is ticked, no shared library is offered at all — people only get their own OneDrive. Everyone in DocuFlow gets full access to a library you tick, to read and to save, whatever its SharePoint permissions say. Tick only libraries that everybody may use.
  • Work e-mail domain (OneDrive, optional) — when filled in, only people whose e-mail ends in this domain (for example org.com) can use OneDrive and the libraries. Leave it empty to allow any address DocuFlow signs in. Google is always limited to your Workspace domain. Keep in mind that this depends on people not being able to change their own e-mail address in your login system.

Credentials are never shown again after saving; each field says "Saved — paste to replace". If you change one, fill in all the credential fields again — leaving them all empty keeps what is saved. Until you select Save, the card says "Not saved yet". The status next to the name says whether the last test found a problem, or whether the connection is switched off.

To remove a connection: select Remove and confirm. People stop seeing the service; nothing already saved in Google Drive or OneDrive is deleted.

Needs attention​

If the card says Needs attention, DocuFlow can no longer use the credentials it holds, and a warning under the status says what to do — usually to paste the credentials again and Save. The one exception is a server that is missing its safekeeping setting (see the message below): pasting again won't help there, it has to be fixed on the server by whoever runs DocuFlow. Until then, people asking for that service are shown a message to contact you.

If something goes wrong
  • "INTEGRATIONS_ENC_KEY is not set on the engine. Set it and restart before configuring integrations." — the server itself is missing the setting it needs to keep these credentials safe. That is for whoever runs your DocuFlow server, not something to fix on this page.
  • A test line in amber means DocuFlow reached the service but the check failed; read the sentence, it says what to change.

Screenshots of this tab will be added once a real Google Workspace and Microsoft 365 organisation has been connected.