> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.aurasos.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.aurasos.com/_mcp/server.

# Google Play Account

Google Play doesn't require a separate account per entity the way Apple does, so
the **fastest path is to publish your app on one of AURA's existing Google Play
stores**. If you specifically need your own Google Play account, this guide
covers setting one up and giving AURA the access to publish on your behalf.

> **Warning**
>
> Register the Play Console as an **Organisation** from the start, not an
> Individual — switching later causes complications and delays.

## Base requirements

* A standard **Google account** linked to your organisation. This becomes the
  root account owner and **cannot be changed** — choose the email carefully.
* A **D-U-N-S number** for your organisation.
* A **Google Play Console** account registered as an **Organisation**.
* An **AURA admin user** on the account, so AURA can list the app and push updates.

## Set up the account

Google's [enrolment guide](https://support.google.com/googleplay/android-developer/answer/6112435)
is the definitive reference; the steps below get you started.

#### Create a Google account

If you don't already have a Google account for the email you want to use, create one.

#### Register the Play Console as an Organisation

Sign up for a Google Play Console account, choose the **Organisation** option,
and select your organisation type. Complete your organisation details.

#### Provide your D-U-N-S number

You may be prompted for a D-U-N-S number so Google can verify your legal entity.

#### Accept the agreement and pay the fee

Accept the **Google Play Developer Distribution Agreement** and pay the
**one-time \$25** registration fee.

#### Verify identity and website

Submit the required personal and organisation documents, and complete **Google
site verification** for your organisation website (this often needs minor DNS
or website changes, so have technical staff available).

## Invite AURA

Open the Play Console → **Users and permissions** → **Invite new users**, and add:

| Field      | Value                      |
| ---------- | -------------------------- |
| First name | AURA                       |
| Last name  | Developers                 |
| Email      | `developers@aura.services` |

Under **Account Permissions**, select **Admin (all permissions)**, then **Invite user**.

## Enable the Google Play API

To let AURA publish updates automatically, set up Google Play API access. This
must be done by the **Account Holder**. If you'd like help, schedule a call with
the AURA developer team.

#### Create a service account

In the Google Cloud Console (signed in with your root Google account), go to
**IAM & Admin** → **Create Service Account**. Give it a recognisable name
(e.g. "AURA service account").

#### Grant the role

When prompted to grant access, choose the **Service Account User** role.

#### Copy the service account email

Open the created service account and copy its generated email address — you'll
add it to the Play Console shortly.

#### Create a JSON key

Under the service account's **Actions** → **Manage Keys** → **Add Key** →
**Create new key**, choose **JSON**, and create it. Save the key file securely;
it will be shared with AURA.

#### Invite the service account in the Play Console

Back in the Play Console → **Users and permissions** → **Invite new users**,
enter the service account's email, grant **Admin** access, and invite.

## Keep in mind

* Google's **terms & conditions** change several times a year and must be accepted
  by the account owner. AURA updates the app to stay compliant.
* Keep the account's **email address valid and monitored** — Google sends all
  notifications there.