> For the complete documentation index, see [llms.txt](https://docs.appmachine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmachine.com/share-your-app/google-play/authorise-an-additional-user-to-your-google-play-developer-account.md).

# Authorise an additional user to your Google Play developer account

An additional authorised user can be helpful if:

\- Your main Google Play developer account has access to multiple developer teams.\
\- You don't feel comfortable sharing your main Google Play developer credentials in our system.\
\- You're having trouble validating your Google Play developer credentials in our system.

Authorising a new user to your existing Google Play developer account is free. After completing the steps in this document you will have a new (additional) Google account which can be used to access your existing Google Play developer console.<br>

**How to add an additional user to your Google Play developer account.**

1. Logout of all Google services.
2. Navigate to [https://gmail.com](https://gmail.com/) and register a new Gmail account. (e.g.: <YourAppName-app@gmail.com>)
3. During the account registration, you'll be asked to add login verification to the account. Make sure to only add a recovery phone number here. ***Do not turn on two-step login verification.***
4. After successfully registering a new Gmail account, logout of Google.
5. Navigate to <https://play.google.com/apps/publish/> and login with your existing Google Play developer account.\
   \&#xNAN;***Note: If you're asked to register as a Google Play developer, please restart from step 3.***
6. After logging in to the Google Play developer console, go to Settings -> Users & permissions.
7. Click the "Invite new user" button in the top-right corner of the screen.<br>

   <figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80111275922/original/6LvBNhTz83NvXPr551kOHWWx5lO9Z_BW2w.png?1654689439" alt=""><figcaption></figcaption></figure>
8. When prompted for an email address, enter the email address you've created in step 2, and give the user Administrator rights.<br>

   <figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80111275919/original/7Diw5k12-K_Psl9OY2rM5OJfe4wkkLa06A.png?1654689439" alt=""><figcaption></figcaption></figure>
9. Logout of the Google Play developer console.
10. Navigate to [https://gmail.com](https://gmail.com/) and login with the new account created in step 2.
11. Open and accept the invitation mail you've sent yourself in step 7.

After completing the steps above, you've created a new user in your Google Play developer console. You will be able to use the email address and password of this new user to publish your app in AppMachine.

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appmachine.com/share-your-app/google-play/authorise-an-additional-user-to-your-google-play-developer-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
