Shared Files & Document Collaboration

A shared folder gives people access to common working files. Collaboration adds decisions about how they review and change those files: in a preview, in a local application, or together in an online editor. The right arrangement depends on whether people need to inspect content, make independent changes, or edit the same document at the same time.

Shared Access

For an internal team, Groups and folder permissions provide shared access. Grant the operations each participant needs rather than assuming that everyone who can see a folder should also be able to change its permissions or share it externally.

A Workspace can group the team's files with its connections, workflows, and external relationships. Folder permissions still determine access inside that Workspace. Team Collaboration develops this into a complete arrangement.

Files can remain in native storage or in a connected location. With a mount, an edit affects the remote file, and other applications may also be accessing it directly. The storage model helps identify where the working file actually lives.

Previews And Review

Previews let people inspect supported images, PDFs, documents, text, and media in the browser. List/Preview permission supports the web preview experience while hiding the normal download action. Read permission supports downloads as well.

Preview access still sends content to the browser. It is not a guarantee that the recipient cannot retain or capture that content. The preview reference explains which formats are supported and how original files, derived previews, and watermarks behave.

A preview is useful for checking whether an invoice is legible or whether a document is the one a colleague needs. Recording that a preview occurred does not establish that the person approved the invoice or reviewed every page. Any required business decision needs an explicit handoff in the team's process.

Local Editing And Online Co-Authoring

Mounted Drive Mode in the Desktop App lets a local application open a file and save changes back to Files.com. This fits specialized desktop software and individual editing work.

For simultaneous document editing, co-authoring uses the online editor configured for the site. Participants must use the same supported online editing arrangement. A person editing directly in a remote platform, such as SharePoint, is not joining the Files.com online session merely because both systems expose the same stored document.

Online editing requires Full folder permission for account users. Share Link visitors have separately configured allowed actions. Supported file formats, conversion behavior, and editor prerequisites belong to the editor reference.

Online editors work with a temporary copy and save changes back periodically and when the session closes. Allow those saves to complete before treating the stored file as the final version for a transfer or review.

Locks And Attribution

Files.com locks coordinate supported desktop and online editing. The Desktop App and online editors participate in this locking behavior; other clients may not. A lock therefore needs to be understood together with every editing path in use, especially when a remote application can modify the file outside Files.com.

File history records saves from a co-authoring session under the user who started the session. It does not identify each collaborator's individual edit. Where that attribution matters, the editor's Track Changes feature records named changes for review and acceptance. Co-authoring logging explains the distinction.

Once a document is ready to distribute, Sharing & Collecting Files helps choose between a live view of the working files and a fixed snapshot for recipients.