Explorer

Explorer is the center of the product.

It is not just a folder browser. It is the shell that owns most working views and most context-preserving collaboration flows.

What Explorer owns

• the folder tree and direct item browsing
• uploads, drag/drop, move, restore, and item creation
• focused repo views such as Files, Notes, Tasks, and Chats
• connected-account views such as Emails and Calendars
• relationship views such as Companies and Contacts
• Cases, shared mounts, pinned shortcuts, trash, sync, and recent-folder shortcuts

How to think about Explorer

Explorer has two layers:

1. the real folder tree
2. virtual working views that help you reach common content faster

Examples of virtual Explorer views:

• Files: recent files
• Notes: recent markdown notes
• Tasks: task lists
• Chats: chat threads
• Emails: unified inbox plus per-account inbox shortcuts
• Calendars: connected calendar accounts
• Companies and Contacts: company workspaces and contact records presented as structured lists
• Cases: case views over folder-backed case records

These views are useful shortcuts, but they do not replace folder ownership. When you need the durable collaboration boundary, return to the actual folder location.

Side sections users should understand

• Shared with me: federated or shared repo content and guest-visible repos
• Pinned: workspace shortcuts, including inbox or mailbox shortcuts
• Recents: recent files and recent folders
• Quick access: manually pinned items
• My folders: folders you changed directly
• Trash: recoverable deleted items
• Sync: desktop checkout and sync-session workflows

Recommended workflow

1. Use Explorer to reach the relevant folder or working view.
2. Open the real folder before creating long-lived work.
3. Use focused views for triage and discovery, not as an excuse to forget where work belongs.
4. Use Search when the location is unknown.

Guardrails

• Avoid doing all work from the recent-content views alone.
• Avoid treating focused views as separate data silos.
• Keep folder names and top-level structure stable after team rollout.