Interactive Use

People use Files.com to find and exchange files, work on documents, and follow the activity that matters to their job. The files can be stored on Files.com or accessed through a connected system. Your account and permissions determine what you can reach; the app or interface you choose determines how you work with it.

A finance team might receive supplier invoices, check their contents in the browser, edit a supporting spreadsheet together, and send a response to the supplier. An Automation can handle onward delivery after a person decides the files are ready. Interactive and automated work can therefore form different stages of one process.

Access Through The Right Interface

The web interface combines file browsing, previews, supported online editing, sharing, and activity review. The Desktop App makes files available to local applications through File Explorer or Finder and provides a dedicated mode for large transfers. Mobile access supports work away from a computer, including capturing and uploading photos or videos.

A person can also use the CLI or a protocol client for a particular transfer. File Access & App Choices explains these choices, including the difference between a mounted drive for everyday file work and a transfer tool for moving a large batch.

The storage connection is shared infrastructure. A Remote Server Mount or On-Premise Agent can make an existing file server available through these interfaces. Choosing an app does not require choosing a new storage location.

Shared Work On Files

For ongoing internal work, users and Groups receive folder permissions appropriate to their responsibilities. Some people need to read or review files; others need to edit, upload, or administer them. A shared location keeps the team's working material accessible without emailing a new copy after every change.

Shared Files & Document Collaboration explains previews, local editing, online co-authoring, and locking. The distinction matters when several people edit the same document: sharing access to a file does not by itself make unrelated editors participate in one co-authoring session.

Exchanges With Other People

A Share Link gives visitors a browser-based way to access selected content under the link's controls. An Inbox provides a place to submit files without browsing the destination folder. An ongoing account supports recurring access through apps and protocols, and a Partner can organize the accounts belonging to an external business.

In the invoice example, an occasional sender might use an Inbox. A supplier whose staff and billing system exchange files regularly can have a Partner with individual accounts. Your finance team can use either arrangement without changing its own internal access model.

Sharing & Collecting Files helps choose the exchange method and decide whether recipients should see a fixed copy or the current contents of shared files.

Activity And Follow-Up

File history, Share Link activity, and notifications answer different questions. History can show a file action; sharing records provide context about the visitor's interaction; a notification brings selected activity to someone's attention. A preview can produce a Read event, so an activity record does not always mean that someone saved a separate download or completed a business review.

File Activity & Notifications explains how to follow the work and investigate a missing message. When a delivery is expected even if nobody sends anything, an Expectation supplies the separate monitoring described in Activity, Delivery & Recovery.

For a complete arrangement combining membership, storage, collaboration, and external sharing, use the Team Collaboration example.