Instruction
Difficulty level:
Beheer > Integraties > Google Drive
Setting up the Google Drive integration: steps on the Google and i-Reserve side
The Google Drive integration needs configuration on two sides: first an OAuth client in Google Cloud, then the integration itself in i-Reserve.
1. On the Google Cloud side
- Open the Google Cloud Console and create/select a project.
- APIs & Services → Library: search Google Drive API and click Enable.
- OAuth consent screen: choose the user type (usually Internal within your own Workspace), fill in app name and support e-mail, and add the Drive scope (
.../auth/drive). - Credentials → Create credentials → OAuth client ID, type Web application.
- Under Authorized redirect URIs add the redirect URI i-Reserve shows (e.g.
{base_url}/integrations/redirect/{int_id}). - Note the Client ID and the Client secret.
2. On the i-Reserve side
Go to Administration → Integrations and add a Google Drive integration.
2.1 Authentication screen
| Field | What to enter |
|---|---|
| Client ID | The OAuth client ID from Google Cloud. |
| Client secret | The matching client secret. |
| Return url | The redirect URI; use exactly the value i-Reserve shows and register that same URI in the Google client. |
Then two buttons: Step 1: consent (Google consent screen, sign in with the desired account) and Step 2: connect (exchanges the consent for the tokens and tests the connection).
2.2 Configuration screen
| Field | What to enter |
|---|---|
| Base folder id | The Drive folder everything lives under (root = My Drive, or a specific folder id from the Drive URL). |
| Base folder name | Display name for the base folder (informational, e.g. i-Reserve). |
| Subfolder pattern | The path template for entity folders, with tokens {context}, {itemname} and {itemid} (e.g. {context}/{itemname} (#{itemid})). |
| Auto-create subfolders | Yes/No — create missing entity folders automatically on first use, or only show existing folders. |
2.3 Activate
Save and set the integration to active. The file manager is then available on the entities (provided the CRM module is active and the user has the Drive permissions).
The Drive integration requires the CRM module and grants per-entity access based on permissions (read / create / delete). Without those permissions the user does not see the file manager.
Google-native files (.gdoc/.gsheet/.gslides) cannot be uploaded via the file manager; they are references, not real files. Move Google Docs within Drive itself.
