Integrations
SKH mirrors content from external sources into your workspaces, so you don't have to maintain files in two places. Configure under Settings → Integrations.
Available integrations
| Integration | Type | Available by default? |
|---|---|---|
| Microsoft OneDrive / SharePoint | OAuth | Yes, every plan |
| Google Drive | OAuth | Yes, every plan |
| Dalux | API token | Only if enabled for your organisation |
| Zipro | API token | Only if enabled for your organisation |
Dalux and Zipro are toggled per organisation by the platform operator. Contact support if you need these vertical solutions.
Microsoft OneDrive & SharePoint
A single Microsoft connection covers both OneDrive for Business and SharePoint Online.
Connect
- Settings → Integrations → Connect Microsoft.
- You're redirected to Microsoft Login.
- Approve the requested permissions.
- After redirect the account appears in the integrations list.
Bind a folder as a page
- Inside a workspace: New page → Connect OneDrive (or Connect SharePoint).
- A folder picker opens. Pick from your OneDrive folders or SharePoint sites + drives + folders.
- Confirm.
SKH automatically starts a sync that indexes the folder and its sub-tree.
Synchronisation
- Initial sync runs immediately after connecting. Watch progress on the page itself and in the Workspace Explorer.
- Incremental sync runs in the background on a schedule.
- Manual trigger via the sync icon on the page.
SharePoint permission mirroring
For SharePoint, SKH additionally synchronises access rights. Anyone without access to a folder in SharePoint also can't see the corresponding page in SKH. Changes in SharePoint (member removed, new permissions) are picked up on the next check. Manual page-member maintenance becomes unnecessary.
Google Drive
Connect
- Settings → Integrations → Connect Google.
- Walk through the Google login, approve Drive access.
- Account appears in the list.
Bind a folder as a page
- New page → Connect Google Drive.
- Pick a folder.
- Confirm.
The sync follows the same model as OneDrive: initial sync, regular incremental sync, manual sync.
Google Drive permissions are not automatically mirrored. You may have to maintain page members yourself.
Dalux (construction plan sync)
Dalux is a software suite for construction projects. When the integration is enabled for your organisation you'll see a Dalux card under integrations.
Configuration
- Settings → Integrations → Configure Dalux.
- Provide:
- Project ID (UUID from Dalux).
- API token (stored encrypted).
- Folder ID (root folder for sync, optional).
Synchronisation
- A nightly sync pulls new plan versions every day.
- Manual sync via the sync button on the page.
- Per plan, a file lands in SKH; versions are tracked.
Use cases
- Construction firms that want to query plans from chat ("which updates landed for the ground-floor plan in 2025?").
- Compliance audits over Dalux-integrated estate.
Zipro (student records)
Zipro is an external student management system. When enabled you see a Zipro card.
Configuration
- Settings → Integrations → Configure Zipro.
- Enter the Zipro tenant ID and API token.
What gets synced?
- Students as their own records (name, unit number, e-mail, phone, ID).
- Per student, pages are mirrored into dedicated workspaces.
- Documents per student land as files in SKH.
Management
Under Students in the sidebar (when Zipro is enabled) you see all synced records with a detail view per person.
Tracking sync status
While a sync runs, you'll see:
- A loading indicator next to pages currently syncing in the Workspace Explorer sidebar.
- A progress display on the page itself (processed vs total files).
- Per-file status (Pending, Processing, Indexed, Failed) in the file list.
Disconnecting an integration
- Settings → Integrations → Disconnect.
- SKH revokes access at the external provider and removes the integration from the list.
- Important: previously synced pages remain in SKH at their last state. They are not auto-deleted. Delete the pages explicitly if you want them gone.
Limits & best practices
- Initial sync on large folders can take several hours depending on volume. Consider running outside business hours.
- Tokens expire – Microsoft and Google tokens must be re-authorised periodically when invalidated, e.g. through a password reset.
- One source per page – A page binds to exactly one external folder. If you need two sources, create two pages.
- Mind the sync cadence – With very high-frequency changes the latency can be several minutes.