Product Guide

This guide is for daily SynckHub users: individual contributors, project leads, operations teams, and cross-functional collaborators.

It is product-first on purpose. Start from the workflow, not from the backend shape.

What you will learn

  • how the current workspace is organized across Search, Explorer-owned views, and repo-admin surfaces
  • how to choose the right item type for each job
  • how sharing, permissions, history, and links behave across the repository
  • how desktop and web workflows fit together
  • how to run common workflows without over-sharing or duplicating context
  1. start-here/what-is-synckhub.md
  2. start-here/first-repository.md
  3. tabs-and-views/index.md
  4. items/index.md
  5. core-concepts/permissions-and-roles.md
  6. common-tasks/share-folder-or-file.md
  7. common-tasks/find-anything-fast.md
  8. common-tasks/coauthor-office-files.md
  1. core-concepts/unified-folder-structure.md
  2. core-concepts/sharing-and-access.md
  3. core-concepts/version-history-and-activity.md
  4. common-tasks/create-public-shared-link.md
  5. common-tasks/restore-previous-version.md
  6. tabs-and-views/collections.md
  7. tabs-and-views/email.md
  8. tabs-and-views/calendar.md

Current platform shape

The current product is centered on one repository with:

  • Search as the main retrieval surface
  • Explorer as the main working shell
  • Explorer-owned views for files, notes, tasks, chats, emails, calendars, companies, contacts, cases, and sync
  • separate repo-admin or governance pages for users, groups, public links, and similar management workflows

If your team understands only the folder tree, it will miss half the product. If it jumps between specialized views without respecting folder context, it will create duplicate work. Both failures are common.

Scope

This section covers user workflows. For admin operations and deployment concerns, use:

  • ../admin-guide/index.md
  • ../self-host/index.md
Previous
Getting Started
Next
Admin Guide