Shared drives don't show when picking a Google Drive folder

You connected Google Drive, the connection says it worked, but the folder picker only shows your own My Drive folders. The shared drive where your team actually keeps client work is nowhere.

Why it happens

Agency OS requests the narrowest Google Drive permission available: access to files it creates, plus files you explicitly open for it. It deliberately does not request permission to read your entire Drive, because that would mean handing a third party every document in your organisation, including ones that have nothing to do with client work.

A shared drive folder that Agency OS did not create and that you have not explicitly picked falls outside that permission. It is not a bug, and reconnecting will not change it.

What to do

• Let Agency OS create the folder. The smoothest path. Set up the client's Drive folder from inside the app and it lands in a folder the app can see and manage. Move it into your shared drive afterwards if you like; access is granted per file, so it keeps working.
• Pick the folder through the Google picker. Where the app offers a picker rather than a list, choosing a shared drive folder there grants access to that specific folder. Typing or pasting a folder ID will not, because the grant comes from the act of picking.
• Check you can open it in Drive yourself. Agency OS inherits your access exactly. A shared drive you are only a commenter on will not accept files.

If the folder still does not appear

Shared drives can be locked down at the Google Workspace level so that external apps cannot be granted access at all, regardless of your own permissions. Your Workspace admin can confirm this under Drive sharing settings. If that is the restriction, create the client folder in My Drive instead and share it with the team.

Still stuck?

Contact support with a screenshot of the picker and the name of the shared drive.