Developer account setup
The Play Console account should outlive the agency, freelancer, and first release.
A clean developer account setup protects app ownership. Before the first app is created, decide who owns the account, who can publish, who can manage policy declarations, and what gets handed over after launch.
Play Console developer account setup is where many Android launches quietly become risky. The app may be built well, but the developer account may be created under a freelancer email, agency workspace, employee Gmail account, or temporary login. Months later, the business needs an update, policy response, app signing detail, or payment profile change and nobody knows who owns what.
This checklist is for founders, agencies, and product teams setting up a Google Play developer account before launch.
Official source note: Google Play Console Help has current setup guidance for registering a developer account, choosing account type, account verification, users, permissions, and account information. Start from Google's current setup page: Get started with Play Console.
Account setup standard
Quick answer
A good Play Console setup separates ownership from implementation access.
Before publishing an app, confirm:
- The business owns or controls the developer account.
- The account type is appropriate for the app owner.
- Verification requirements are understood early.
- Recovery email and phone belong to the business owner or authorized admin.
- Developers, QA, marketers, and agencies have scoped permissions.
- Payment profile, contact details, and support email are controlled by the owner.
- App signing and release responsibilities are documented.
- Handover includes users, permissions, app records, policy declarations, and support contacts.
Play Console account setup checklist
| Area | Decision | Why it matters |
|---|---|---|
| Account owner | Founder, company, or authorized admin | Determines who controls future updates and policy responses. |
| Account type | Personal or organization | Affects verification and business identity requirements. |
| Recovery | Owner-controlled recovery email and phone | Prevents lockout after staff or vendor changes. |
| Users | Developer, QA, marketing, finance, agency | Keeps access scoped to role instead of sharing passwords. |
| Contact details | Support email, phone, website, address | Used across store listing, trust, and account communication. |
| Handover | Written account and app launch runbook | Makes future releases maintainable. |
Personal versus organization account
Account type should match the long-term owner. If a company owns the app, an organization setup often fits better than a personal account under a contractor's Gmail. Organization accounts may require business identity details such as a D-U-N-S number according to Google's account type guidance. Confirm the current rules before starting setup.
Users, permissions, and agency access
Google Play Console supports adding users and managing permissions. Use that instead of sharing the owner password.
Release and technical access
Developers may need app setup, release, signing, testing, or API-related permissions. Avoid granting financial or owner permissions unless needed.
Testing access
QA may need tester links, internal track access, or release visibility without policy or production management rights.
Store listing access
Marketing may help with descriptions, screenshots, graphics, experiments, and translations without changing app signing or releases.
Temporary implementation access
Agency access should be time-bound, documented, and reviewed after launch or handover.
Verification, payments, and contact details
Do not leave verification until production release day. Prepare account details early:
Account details checklist
- Developer name and public profile details.
- Business legal name and address where applicable.
- Contact phone and email.
- Payment profile if paid app, in-app products, or financial setup is needed.
- Tax or banking responsibilities where applicable.
- Developer account verification requirements.
- App support email and website.
- Privacy policy URL for apps that require it.
Handover record
Every Play Console setup should end with a handover note:
- Account owner and recovery route.
- Account type and verification status.
- Users and permissions matrix.
- App package name and app record details.
- App signing owner and upload key responsibilities.
- Store listing owner and asset locations.
- Policy declarations owner.
- Support contact for Google Play communications.
- Release track and rollout process.
FAQ
Should an agency create the Play Console account for the client?
Agencies can help, but the business should usually own the account. The agency can be added as a user with appropriate permissions.
Can multiple people access Play Console?
Yes. Use Play Console users and permissions. Avoid shared passwords.
When should verification be handled?
As early as possible. Verification, account details, and payment setup should not wait until the app is ready for production release.
Can Shinka help with account setup and permissions?
Yes. Shinka can guide the setup, document permissions, prepare launch roles, and hand over a clean runbook while ownership remains with the client.
