Google Cloud
The Google Cloud project behind your app's Google APIs — Sign-In, Maps, push notifications, and more — set up the account and grant us access so we can configure them.
Why we need this
Google Cloud is the umbrella project that powers the Google services your app relies on: Google Sign-In / OAuth login, Maps and Places, Firebase Cloud Messaging for push notifications, and any other Google API we wire up. Calda needs access so we can enable those APIs, create the credentials and keys they require, and configure them for your app.
Like all other accounts, this one should be owned by you. Your project, credentials, OAuth consent screen, and billing are tied to the account, so keeping it under your company means everything running on it belongs to you, not us.
Do I need a credit card?
Yes. Most Google Cloud APIs require an active billing account with a payment method — for example, Maps Platform won't serve requests without one. Google provides free trial credits and a monthly free tier, so early development usually costs little to nothing, but the card still needs to be on file.
Billing stays under your account
The payment method and all API usage billing live under your Google Cloud account. We'll keep the APIs scoped to what your app actually needs so you only pay for real usage, and the free tier covers most early development.
Step-by-step setup
Create the Google Cloud project
Go to console.cloud.google.com and sign in with the Google account that will own everything. From the project dropdown in the top bar, click New Project and name it after your company or app.
Set up a billing account
Open Billing from the left menu and add a payment method. Link this billing account to the project you just created so the APIs we enable can serve requests.
Free trial credits
New Google Cloud accounts come with free trial credits, and many APIs have a monthly free tier — so this step is mostly about having a valid card on file, not about immediate charges.
Invite Calda
Open IAM & Admin → IAM, click Grant access, enter the Calda email we share with you, and assign the Editor role — or Owner if we'll be managing the OAuth consent screen and API credentials, which Editor can't fully control.
What we'll do once we're in
After you've granted access, we'll enable the specific APIs your app needs (Sign-In, Maps, push notifications, and so on) and create the credentials and keys ourselves — you don't need to enable anything or share any keys.
Confirm in Slack
Don't forget to notify us in Slack so we can accept the invitation and confirm that we can sign in and see the project.
Conclusion
That is it — with this access we can set up and manage the Google services your app uses on your own account. Once you've granted access and confirmed in Slack, we'll handle the rest of the configuration on our side.
How is this guide?