Skip to main content
Solved

Can clients see each other's folders if they share content with the same external user?

  • October 16, 2026
  • 1 reply
  • 17 views
  • Translate All

  • New Participant

Hi everyone,

I have a question about Box permissions.

I am an external user who receives access to Box content from multiple clients. I do not manage the Box environments or permission settings myself. I am simply the recipient of access that has been granted by different clients.

Because multiple clients have shared content with the account I use, I can see folders and files from several different clients when I log in.

My understanding is that I can see these folders only because they have been explicitly shared with my account.

What I would like to confirm is whether those clients can see each other's content. For example, if both Client A and Client B share folders with the same external user account, can Client A see Client B's folders or files in any way without being explicitly granted access?

Or are all folders and files isolated by permissions so that each client can only see the content shared directly with them?

Thank you in advance for your help.

Best answer by DuaerTeam


Short answer: **no** — Client A does not get visibility into Client B’s folders just because both of them invited the same external account. Access is granted **to** a person (or group) on a specific folder/file; it is not shared “sideways” between unrelated owners.

A few practical checks:

1. **Per-item collaborators**  
   On each folder that was shared with you, open the collaborator / share settings. You should see your account listed on that item. Client A’s folder collaborator list should *not* automatically include Client B (or Client B’s folders), and the reverse is also true.

2. **What you see vs what they see**  
   Your login can show a **union** of everything that was explicitly shared *with you*. That does not mean the sharers can see each other’s items. Each client only sees the folders and files in *their* own Box account (plus anything that was shared *with them*).

3. **Shared links are the common exception**  
   If someone used an open “anyone with the link” shared link (instead of inviting you as a collaborator on a specific folder), then anyone who gets that URL can open that item — including people at another client, if the link was forwarded. Collaborator invites with a defined role are the safer default when you want isolation.

4. **Same parent / same enterprise caveats**  
   Isolation breaks only if the content actually lives under a common parent that both clients can already access, or if invites went to a shared group/enterprise that both sides belong to. From your description (separate clients granting you access independently), that usually is not the case.

5. **Quick sanity test**  
   Ask Client A whether they can browse to Client B’s folder path from their own account without an invite. If permissions are set normally, they should not be able to. If they somehow can, someone likely shared a parent folder, a group, or an open link — worth cleaning up on that side.

You do not need to change anything on your side for the default case: keep using one external login; each client keeps managing collaborators only on their own folders.
 

View original

1 reply

  • New Member
  • Answer
  • October 16, 2026


Short answer: **no** — Client A does not get visibility into Client B’s folders just because both of them invited the same external account. Access is granted **to** a person (or group) on a specific folder/file; it is not shared “sideways” between unrelated owners.

A few practical checks:

1. **Per-item collaborators**  
   On each folder that was shared with you, open the collaborator / share settings. You should see your account listed on that item. Client A’s folder collaborator list should *not* automatically include Client B (or Client B’s folders), and the reverse is also true.

2. **What you see vs what they see**  
   Your login can show a **union** of everything that was explicitly shared *with you*. That does not mean the sharers can see each other’s items. Each client only sees the folders and files in *their* own Box account (plus anything that was shared *with them*).

3. **Shared links are the common exception**  
   If someone used an open “anyone with the link” shared link (instead of inviting you as a collaborator on a specific folder), then anyone who gets that URL can open that item — including people at another client, if the link was forwarded. Collaborator invites with a defined role are the safer default when you want isolation.

4. **Same parent / same enterprise caveats**  
   Isolation breaks only if the content actually lives under a common parent that both clients can already access, or if invites went to a shared group/enterprise that both sides belong to. From your description (separate clients granting you access independently), that usually is not the case.

5. **Quick sanity test**  
   Ask Client A whether they can browse to Client B’s folder path from their own account without an invite. If permissions are set normally, they should not be able to. If they somehow can, someone likely shared a parent folder, a group, or an open link — worth cleaning up on that side.

You do not need to change anything on your side for the default case: keep using one external login; each client keeps managing collaborators only on their own folders.
 

Translate