Sharing and Browser Controls

Sharing files with recipients and publishing web content establish different relationships. A Share Link gives visitors access to a selected delivery without requiring Files.com user accounts. Public Hosting lets a publisher maintain files or a website for visitors. Administrators approving either arrangement need to consider who can distribute or change the content, how recipients obtain access, and what their browsers may do with it.

A shared password, an invitation URL, and a code sent to a mailbox establish different access requirements. They do not all identify an individual person. Published content also has its own access controls, separate from the folder permissions used by the people maintaining it. Choose the arrangement for the relationship you need with recipients and publishers.

Access and Browser Behavior

Browser controls govern how pages load, embed, and read content. They complement authentication and permissions, rather than replacing the checks that determine whether a request can receive protected information. A response designed for embedding can have different controls from the main web interface or an API response.

For hosted content, the browser origin is a consequential boundary. Two folders served under one hostname can share browser capabilities even when their URLs and passwords differ. Someone who may publish scripts needs to be trusted with the other hosted content those scripts can reach, or the content needs a separate origin and appropriate controls.

Recipient access has its own lifetime as well. Changing an employee's folder permissions does not automatically end a Share Link they created, and revocation cannot retrieve a completed download. Review access removal alongside the controls governing the delivery or published content.