Connect Google Play Console

AppBoard connects to Google Play through a service account that you invite into your Play Console. The service account's JSON key is the credential AppBoard uses to read and update your listings.

Create and invite the service account

1. In the Google Cloud project linked to your Play Console, create a service account and generate a JSON key for it.
2. In the Play Console, under Users and permissions, invite the service account's email and grant it access to view app information and edit store listings.
3. Start a new Google Play connection in AppBoard and upload the JSON key. It is encrypted in the vault before it is stored.

Register draft apps manually

Google's Play Developer API only returns apps that have at least one published or in-review release. Apps that are still in draft are invisible to the API, so they won't import automatically.

For those, AppBoard supports manual package registration: add the app's package name yourself and AppBoard tracks it alongside the discovered apps. Once the app has a release Google exposes, it behaves like any other connected app.

Full re-import

If your local apps have drifted from what's on the account — stale entries, a reorganized console, or a fresh start — run a full re-import. AppBoard wipes the locally stored apps for that store and fetches everything fresh from the account.

Heads up: a full re-import removes the local apps for that store before re-fetching. Any local-only entries, including manually registered draft packages, need to be re-added afterward.

Publishing to Play

When you publish, AppBoard can push your changes as a draft or send them for review. Managed publishing modes — manual, automatic, or scheduled — are controlled in the Play Console itself, so AppBoard respects whatever you have configured there.