There is no Your Company toggle. You reach the state by sharing a file so that all internal users gain access, then confirming the platform reports the org-wide privacy state. The steps below use the most durable path, a library open to everyone, with a per-file group share as the alternative.
- Pick or build the org-wide audience
Decide how all internal users will be covered. The cleanest option is a public group whose membership includes every employee. Confirm who owns that group and how members are added, because that rule governs every file you share with it.
- Create a library for the content
In the Files app, create a library to hold the org-wide reference material. Add folders if the collection is large. A library lets one membership grant cover many files at once instead of sharing each file separately.
- Share the library with everyone internal
Add the all-employees public group to the library as a member with at least view access. Every file you add to the library now inherits org-wide reach, which is what places those files in the Your Company state.
- Add files and confirm the state
Upload or move files into the library. Open a file and check that it shows the "your company" icon, meaning anyone in the company can find and view it. To verify programmatically, query ContentDocumentLink and confirm the rows reach all internal users.
Grant the all-employees group access to the library so every file inside reaches all internal users. The most maintainable route to Your Company for reference content.
Share a single file directly with an all-employees public group. Faster for one file, but each file needs its own share, which does not scale across a collection.
On a sharing row, AllUsers exposes the file to all users, InternalUsers holds it to internal users only, and SharedUsers limits it to explicit recipients. Your Company needs all internal users covered.
V grants view-only, C grants collaborator (view, edit, re-share), and I infers access from a linked record. Reference content is usually shared as view-only so the whole company cannot edit it.
- Your Company is computed from sharing rows, not a stored flag. Remove the org-wide grant and the file silently drops back to Privately Shared or Private.
- The state covers internal users only. Sharing with an all-employees internal group does not make a file visible to Experience Cloud community or partner users.
- Do not confuse Your Company with a public link. Your Company keeps the login requirement; a public link removes it and lets anyone with the URL view and download the file.
- Files shared org-wide accumulate. Audit ContentDocumentLink periodically so a sensitive file does not stay company-visible long after it should have been scoped down.