Shared Drive file sharing

40 views
Skip to first unread message

Ross Scroggs

unread,
Sep 5, 2025, 5:54:54 PM (10 days ago) Sep 5
to google-ap...@googlegroups.com
My understanding is that a file/folder on a Shared Drive can be shared to an external domain.
But it's not working for me; am I missing something?

$ gam user us...@mydomain.com add drivefileacl <FileIDOnSharedDrive> domain otherdomain.com role reader withlink            
User: us...@mydomain.com, Add 1 Drive File/Folder ACL
  User: us...@mydomain.com, Drive File/Folder ID: <FileIDOnSharedDrive>, Permission ID: therdomain.com, Add Failed: Bad Request. User message: "invalidLinkVisibility"

On the Shared Drive of interest, there two items are checked:
Allow people outside of <Domain Name> to access files
Allow people who aren't shared drive members to access files

Thanks,

Ross
--

john smith

unread,
3:43 AM (11 hours ago) 3:43 AM
to GAM for Google Workspace
Hi Ross,

To my knowledge the only way to share with a 'domain' is the default 'Target Audience', however this only applies to the domain in which the user exists. The default target audience {Account Name} contains all users in the account (I suspect in the back-end it is essentially a dynamic group containing all users). Shares to this Target Audience will look like mydomain.com in the logs and have the permission type of 'domain'. In the UI, the default target audience is an option alongside 'anyone with the link'.

I suspect the 'domain' permission type / API option is reserved for the default target audience of the account in which the user exists rather than being a general-purpose sharing mechanism. If it was general purpose I would expect to see a way of sharing to a domain in the UI. 

However, the descriptions of 'domain' in https://developers.google.com/workspace/drive/api/reference/rest/v3/permissions make it sound general purpose, so I'm not sure I'm correct. My best guess is this is undocumented behavior, possibly made murkier due to the transition from sharing to 'domain' to 'target audience' in the front end without changing the back-end / API language.

p.s. Thank you for the updates to Meet in 7.19!
Reply all
Reply to author
Forward
0 new messages