> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/bulk-import-web-store-inventory-skus-from-google-play/1.-google-play-integration/step-3-invite-the-copied-service-account-into-your-google-play-console.md).

# Step 3: Invite the Copied Service Account into your Google Play Console

Go to [Google Play Console](https://play.google.com/console/developers) > Users and permissions section to invite the service account email address copied from Coda Portal. You may need admin access to your Google Play Console.

<figure><img src="https://files.readme.io/af5753b-Step_2c_Invite_the_service_account_created_to_your_Google_Play_app.png" alt=""><figcaption></figcaption></figure>

Paste the service account email address copied from Coda Portal into your Google Play Console and choose the app(s) for which you want to grant permission

<figure><img src="https://files.readme.io/cd26c4d-Step_2d_Grant_read-only_access_to_the_service_account.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coda.co/coda-webstore/bulk-import-web-store-inventory-skus-from-google-play/1.-google-play-integration/step-3-invite-the-copied-service-account-into-your-google-play-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.