Install and choose clients
Most users should start with the web app. Add SynckHub Desktop or mobile only when the workflow needs it.
Client options
| Client | Best for |
|---|---|
| Web app | Everyday repository work, Explorer, Search, sharing, admin workflows, and broad feature coverage |
| SynckHub Desktop | Local file editing, desktop-assisted file flows, sync sessions, Save As ingestion, and heavy document work |
| Mobile app | Reading updates, responding quickly, and lightweight work away from a desktop |
Do not treat each client as a separate workspace. They should open the same tenant, repository, and folder context.
Use the web app first
Use a supported browser such as Chrome or Microsoft Edge.
The web app is the baseline client for:
- signing in
- opening repositories
- using Explorer and Search
- creating folders, files, notes, tasks, and chats
- sharing and permission checks
- most admin workflows
If your browser supports installing progressive web apps, you can install SynckHub as a desktop-like app from the browser menu. This is optional; it does not replace SynckHub Desktop.
Add SynckHub Desktop for local file work
Install SynckHub Desktop when users need operating-system workflows such as:
- opening files in native desktop applications
- syncing a folder or file checkout
- saving desktop-created files into SynckHub
- using Save As ingestion from local tools
- handling larger or longer-running file workflows
After installing Desktop, verify one real file workflow:
- Open SynckHub in the web app.
- Open a repository folder.
- Start a supported desktop edit or sync action.
- Save or finish the file workflow.
- Confirm the updated file state appears back in SynckHub.
If Desktop cannot connect to the web app, check sign-in state and any organization desktop policy.
Use mobile as a companion
Use mobile for:
- quick reading
- chat or task response
- lightweight updates
- field access
Do not use mobile as the primary admin or migration client unless your organization explicitly supports that workflow.
Microsoft Office and coauthoring
Office coauthoring is deployment-dependent. Some environments support Office web, WOPI, or SharePoint-backed coauthoring; others use normal file edit and version history.
If Office coauthoring is available:
- open Office files from SynckHub using the provided action
- avoid parallel non-coauthor editing on the same file
- confirm final content is saved back to SynckHub
If the action is missing, assume the integration is not enabled for your deployment or account.
Client rollout checklist
- All users can sign in through the web app.
- Heavy document users have SynckHub Desktop installed.
- Desktop users can complete one file edit or sync flow.
- Mobile users can open the same repository and respond without creating shadow workflows.
- Users know which client to use for each job.
Next step
Continue to Create Your First Repository.