Docs › Desktop app
Share a library on your network
A library can live in a shared folder on your network instead of on one computer, so your team works in it together from the desktop app: the same datasets, reports, Calculated Fields and Summary Calculations, with no cloud in between. Everyone's changes appear in the others' apps as they're saved, as they do on the website. This guide covers choosing and setting up the folder, moving your library there, and connecting your colleagues.
Plan availability Shared libraries are for Plus and Ultimate workspaces. Everyone who opens one must be a member of the workspace and signed in to the desktop app. A library has no dataset or report limits; publishing from it counts toward the workspace's plan as usual.
What the folder needs#
- A network share that supports SMB 3 or NFS v4. A Windows file server share, a NAS share using SMB 3, or an NFS v4 export. The app checks this when you choose the folder and refuses an NFS v3 mount or an old NAS that can't create files exclusively, which shared writing depends on.
- Not a synced folder. OneDrive, Dropbox, Google Drive, iCloud Drive and Box copy files behind the app's back and would damage the library. The app refuses folders inside them. A SharePoint library synced through OneDrive counts as one of these.
- An empty folder, one per library. One workspace's library per folder. The app refuses a folder that already holds other files, or another workspace's library.
- Read and write access for every member who will use it. Each person's own network account must be able to create, change, rename and delete files in the folder.
- Clocks that agree. The computers that share a library should have their clocks within a minute of each other. Computers joined to a company domain or set to the internet time already do.
Set up the folder#
On a Windows file server:
- Create a folder for the library, for example
D:\Shares\Insight\Sales. - Share it (Properties, Sharing, Advanced Sharing), and under Permissions give your team's group Change.
- Under Security, give the same group Modify. Take away access for everyone else.
- Note its network path, for example
\\fileserver\Insight\Sales.
On a NAS, create a share with SMB 3 turned on (often under the SMB settings as the minimum protocol), and give your team's group read and write access.
On macOS and Linux, connect to the share first (Finder, Go, Connect to Server… with smb://fileserver/Insight, or mount it in Linux) and use the mounted folder.
Move your library to the folder#
One person does this, usually the one whose library has the work so far.
- In the desktop app, open Settings.
- Under Libraries, find the workspace and choose Move….
- Pick the shared folder. The app copies the library there, checks the copy, and from then on works from the folder. The list shows Shared folder: with its path.
- The old folder on your computer stays until you choose Delete it in the banner.
If nobody has a library with work in it yet, moving an empty one is fine: the app makes the library in the folder when it's first opened.
Connect your colleagues#
Each colleague, in their own desktop app, signed in as themselves:
- Open Settings.
- Under Libraries, find the workspace and choose Use a shared library….
- Pick the shared folder (the one that already holds the library).
The app then opens the workspace's library from that folder: "Workspace is opened from folder. Everyone working there sees each other's changes."
In the workspace's pages the shared library is listed as This computer, beside what's online (Live): the Reports folder tree has a root for each, and Datasets marks each dataset and can show one or both. Sharing a report with people and public links are for reports in the live workspace; a shared library is shared through its folder.
Working together#
- Changes appear live. When someone saves a report, imports or edits a dataset, the others see it within a few seconds, with the same notices as the website.
- One editor per report at a time. Editing a report takes its edit lock, as on the website. The others see who has it and can open the report read-only meanwhile.
- Dataset edits from several people are kept, row by row. Two people changing the same row are handled as on the website: the later save is told the row changed.
- Database connections are shared, passwords aren't. A connection added on the library's Connections page is there for everyone. Each person enters their own password once, kept on their own computer, or uses their own Windows sign-in.
- Refreshes can be run by anyone who can sign in to the database.
Scheduled refreshes on a shared library#
A dataset's Schedule (on the library's Connections page) belongs to the library, so every app that has the library open sees it. Only one computer runs each scheduled refresh:
- The first one ready takes it. When a refresh is due, each app that can run it tries to claim it in the library's folder; one wins and runs it, and the others skip it. The claim goes when the refresh finishes, or after 70 minutes if that computer stopped mid-way, so another can take over.
- Only a computer with the password runs it. An app claims a refresh only when its user has entered the connection's password on that computer (or the connection uses their own Windows sign-in). Make sure at least one person who keeps the app running, ideally on a computer that stays on, has entered it.
- Nobody able to run it? The run log notes it once a day: "Not refreshed on its schedule: no credential on this computer". The Data pane of a report on that dataset shows it as behind, with Refresh now for anyone who can run it.
- The app stays in the tray after its last window closes while a library has a schedule, and Start when I sign in (in Settings) starts it after a restart, so the computer that runs the schedules doesn't need a window open. A refresh missed while every app was closed runs once when the next one starts.
- Schedules are in each computer's own time zone. "Daily at 06:00" runs at six on the computer that claims it, so a team across time zones should agree on one computer, or a time that suits everyone.
- Refresh by hand works the same way: if another computer is running that dataset's refresh at that moment, the app says so and you try again when it has finished.
Working offline and when the share is unreachable#
- The library is only as available as the share. When the folder can't be reached (no network, VPN off), the library doesn't open. Reports saved as
.ifprfiles and other libraries still do. - Each person's sign-in counts on its own: after 30 days without signing in, that person's app stops opening the library until they sign in again. Nothing in the folder changes.
Backups#
The library is a folder of ordinary files, so back up the share as you would any other. Restore a whole library folder at once rather than single files, with nobody working in it while you do.
Stop sharing, or move it again#
- To move the library to another folder, any member can choose Move… again. Tell the others, who then choose Use a shared library… with the new folder.
- To stop using the shared library on one computer, that person chooses Move… to an empty folder on their own computer. They take a copy, and the shared folder carries on for everyone else. The app doesn't offer to delete a shared folder; when the team is done with it, whoever runs the share removes it.
If something goes wrong#
| Message | What to do |
|---|---|
| "… is inside a cloud-synced folder (OneDrive, Dropbox, Google Drive or iCloud) …" | Choose a network share or a folder on your computer that isn't synced |
| "… does not support exclusive file creation (an NFS v3 mount or an old NAS?) …" | Use SMB 3 or NFS v4. On a NAS, raise the minimum SMB version to 3 |
| "… cannot be written …" | Your network account can't create files there. Ask whoever runs the share for Modify access |
| "… already holds other files; choose an empty folder for the library" | Make a new, empty folder for the library |
| "… is the library of another workspace …" | That folder is another workspace's library. Pick that workspace's own folder, or an empty one |
| "… is not empty; choose an empty folder to move the library to" | Move… needs an empty folder. To open a library already there, use Use a shared library… |
Plan limits summary#
| Feature | Free | Mini | Plus | Ultimate |
|---|---|---|---|---|
| Library on a shared network folder | No | No | Yes | Yes |
| Datasets and reports in a library | No limit | No limit | ||
| Snapshot datasets and saved versions in a library | No | No | No | Yes |
| Row access in a library | No | No | Yes | Yes |