Connected accounts are connected to each user, not the workspace nor the base.
So, if you are creating a brand new automation from scratch, Airtable will only let you see your own connected accounts.
However, if you are editing a pre-existing automation that has already been setup by someone else with one of their connected accounts, you are allowed to edit their automation and it will allow you to leave their connected account intact.
So, one workaround for your issue is to simply have them start creating the new automation for you by connecting it to their account, and then you can finish it from them.
The other solution for this would be to build your automations with Make’s advanced automations & integrations for Airtable, which creates connections at the organization level, so anybody can create automations using any connection.
Make natively supports over 1,600 apps that can connect with Airtable, and you can also connect unsupported apps as well by using Make’s HTTP module.
There is a small learning curve with Make, which is why I created this thread of training resources to help.
