> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/upload/android/grant-google-developer-access.md).

# Grant Google developer access

### How to grant access of your Google developer account?

You can invite your team members and colleagues to your Google Play Console account. The following steps explain the process:

{% embed url="<https://scribehow.com/shared/Grant_Google_developer_access__mTgoui9BRHS6mGIzR67oRA>" %}

* Login to your Google Play Console account.&#x20;
* Select **Users and permissions** from the side menu.&#x20;
* Click on Invite new users to add new team members to your app.&#x20;
* Enter the email address of the user you wish to invite and an access expiration date. If you do not set an expiration date, the invited user will have ongoing access to your Play Console account or app.&#x20;
* Choose the permissions granted to the invited user for each app in the App Permissions tab. Additionally, choose the permissions granted for all apps in your developer account in the Account Permissions tab.&#x20;
* Click on **Invite user** after selecting the permissions granted.


---

# 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.appmysite.com/app/upload/android/grant-google-developer-access.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.