Workspace Views

The current SynckHub product is not organized as a row of unrelated apps.

For most users, the workspace has two main entry points:

• Search for retrieval
• Explorer for nearly everything else

Inside Explorer, the left sidebar exposes the real working surfaces users move between every day:

• Files
• Chats
• Emails
• Calendars
• Notes
• Tasks
• Companies
• Contacts
• Cases
• Invites
• Shared with me
• Pinned shortcuts
• Recents, quick access, my folders, trash, and sync

That is the model the rest of this section follows.

The real view model

In the current product, users typically work like this:

1. open Explorer for context-first work
2. jump to Search when they know what they want but not where it lives
3. move between Explorer-owned views such as Files, Chats, Emails, Calendars, Notes, Tasks, Companies, Contacts, and Cases
4. use repo-admin tables only when they are doing governance work such as users, groups, or public links

Surface selection map

• Search: exact retrieval, full-text discovery, and finding saved content by text, type, or folder scope
• Explorer: folder tree, item creation, uploads, drag/drop, and day-to-day work in context
• Files / Notes / Tasks / Chats: focused Explorer views over the repository’s operational content
• Emails / Calendars: connected-account workflows surfaced inside Explorer
• Companies / Contacts: company workspaces and contact records for relationship work
• Cases: workflow-oriented case views over folder-backed case records
• Directory pages: repo admin and governance tables such as users, groups, agents, and public links

In this section

• explorer.md
• search.md
• directory.md
• email.md
• calendar.md
• collections.md

Reading rule

If a page in this section talks about a standalone “app”, verify whether it is actually:

• a top-level route
• an Explorer-owned view
• a repo-admin table
• or a legacy route that now redirects

That distinction matters for onboarding, permissions, and user expectations.

Practical selection rules

Start with the question:

• “Where does this work live?” -> Explorer
• “What did we already save?” -> Search
• “Which files or markdown notes changed recently?” -> Files or Notes
• “Which conversations need attention?” -> Chats or Emails
• “Which commitments or deadlines matter now?” -> Tasks or Calendars
• “Which company, contact, or case is this about?” -> Companies, Contacts, or Cases
• “Who has access or what links exist?” -> Directory or admin pages, not ordinary work views

Common mistakes

• documenting Email, Calendar, and Cases as if they are unrelated top-level apps
• sending new users to directory governance pages when they really need Explorer
• treating Companies and Contacts as free-form notes instead of structured relationship views
• pretending /collections is still the everyday entry point for case work