Add developer account users and manage permissions

There are three different access levels in Play Console: account owner, admins, and users. Your access level determines what actions you can perform and what information you can access in Play Console. As an admin (administrator), user management allows you to safely control which parts of Play Console your wider team can see based on their roles, what data they have access to, and the settings they can change.

Account access levels

Type	Description
Account owner	First registered account in Play Console Has full access to Play Console Can invite and remove users, and manage individual permissions Is the only person who can have a linked payments profile to sell paid apps Is the only person who can edit information on the Payments settings page in Play Console Is the only person who can edit developer profile information in Play Console Is the only person who can edit API access details in Play Console
Admin	Has the "Admin (all permissions)" permission Can be given access to all or specific apps Can invite and remove users, and manage individual permissions Doesn't need to pay the $25 registration fee
User	Can have different levels of access to Play Console Can be given access to all or specific apps Can't invite users or edit permissions Doesn't need to pay the $25 registration fee

Give users access

Step 1: Decide whether your user needs account or app access

Before you set up permissions, you need to decide if your user needs access at account level or at app level:

• Account: Account permissions apply to all apps in your developer account.
• App: App permissions only apply to the selected app.

Some permissions are exclusively available to app or account level users only. For details on how account and app access might impact a specific permission differently, you can check the permission definitions and uses section.

Step 2: Add users and turn permissions on or off

If you're an account owner or admin, you can add users to your Play Console account and manage permissions across all apps or for specific apps. Before adding users and turning permissions on or off, review the permission definitions and uses section to ensure that you understand them.

1. Open Play Console(Users and permissions > Invite new users).
2. To manage permissions for an existing user, click anywhere on the user’s row in the user table.
3. To add a new user, type the user’s email address and set an access expiry date if necessary. Make sure you have the Admin (all permissions) permission at account level.
   Note: Invited users can only sign in to Play Console using the same email address that you provided. Also, if you don't choose an access expiry date, the user will have ongoing access to your Play Console account or app indefinitely.
4. Select the permissions you want to apply to specific apps using the App permissions tab. To select permissions to apply to all apps in your developer account, use the Account permissions tab.
   • To add an app to the permissions table, select Add app under the App permissions tab and then click Apply.
5. Select Invite user.

Collapse all Expand all

Permission definitions and uses

General permissions

Admin (all permissions)

Rights

Usage notes

Invite users. Manage permissions of other users. Remove users.

This permission gives a user admin access. With this permission, an admin also gets all other permissions. If this permission is set per app, the admin can see all users with permission to access the same apps. App-level admins can't remove users with global access. If this permission is set to global, the admin can also change access expiration dates and review changes made in Play Console using the Activity log.

View app information (read-only)

Rights	Usage notes
Read-only access to all app information, including any associated Google Play games services projects but not financial data.	To grant access to financial data, give users the View financial data permission. This permission is available to users with "App" access only. The "Account" equivalent is View app information and download bulk reports (read-only). For example, provide read-only access to promotional content submissions and reporting data.

View app quality information (read-only)

Rights	Usage notes
Read-only access to app-level Android vitals and pre-launch reports, as well as basic information about artifacts, tracks, and releases.	Users with this permission are not able to edit information or make any changes. To provide access to any other app data, or to allow these users to make changes, select the View app information and download bulk reports (read-only) permission before granting access to other account permissions.

View app information and download bulk reports (read-only)

Rights	Usage notes
Read-only access to all app information for all apps, including all Google Play games services projects but not financial data. Download bulk reports.	The user can access any new app or game you add to Play Console afterwards. The user can view all games, including ones not linked to any app. To grant access to financial data, give users the View financial data permission. This permission is available to users with "Account" access only. The "App" equivalent is View app information (read-only).

Edit and delete draft apps

Rights	Usage notes
Edit and delete existing draft apps.	This permission doesn't allow users to start the roll-out of a release. This permission is available to users with "App" access only. The "Account" equivalent is Create, edit, and delete draft apps.

Create, edit, and delete draft apps

Rights	Usage notes
Create new draft apps. Edit and delete existing draft apps.	This permission doesn't allow users to publish apps on Google Play. To create new apps, users also need to have the View app information and download bulk reports (read-only) permission. This permission is available to users with "Account" access only. The "App" equivalent is Edit and delete draft apps.

Manage policy declarations

Rights	Usage notes
Edit and submit policy declarations, for example, the Data safety section and permission declarations.	This permission can be used in conjunction with the View app information (read-only) permission. To grant access to financial data, give users the View financial data permission. The user can view policy-related messages in Inbox.

View financial data

Rights	Usage notes
View financial and sales reports. Access to the Purchases API View revenue information for any associated Google Play games services projects.	This permission is available to users with "App" access only. The "Account" equivalent is View financial data, orders, and cancellation survey responses.

View financial data, orders, and cancellation data survey responses

Rights	Usage notes
View financial reports, sales reports, and orders. Access to the Purchases API View revenue information for any associated Google Play games services projects. Download written responses to the cancellation survey.	This permission is available to users with "Account" access only. The "App" equivalent is View financial data.

Manage orders and subscriptions

Rights	Usage notes
View orders. Refund orders. Cancel subscriptions.	This permission doesn't allow users to view aggregate financial reports. This requires the View financial data permission.

Release to production, exclude devices, and use Play App Signing

Rights	Usage notes
Create, edit, and roll out releases to production. Unpublish and republish apps. Exclude devices in the device catalog. Use Play App Signing to sign APKs.	This permission allows users to publish apps to production on Google Play.

Release apps to testing tracks

Rights	Usage notes
Upload draft apps. Create, edit, and roll out releases to testing tracks. Unpublish and republish apps that were previously published to a testing track. Upload and modify .obb files. Edit release notes for apps which are not active in production. Upload APKs for internal sharing.	This permission doesn't allow users to publish apps to production on Google Play.

Manage testing tracks and edit tester lists

Rights	Usage notes
Change testing configuration for internal, open, and closed tracks. Manage tester lists and associated users.	This permission doesn't allow users to publish apps to production on Google Play.

Manage store presence

Rights	Usage notes
Edit store listing information (including text and images) and perform store listing experiments. Edit pricing, in-app products, and pricing templates. Edit distribution information, including content rating. Create and edit promotions or sales. Manage saved device filters in the device catalog. Create and edit promotional content.	This permission doesn't allow users to exclude devices in the device catalog.

Reply to reviews

Rights	Usage notes
Reply to reviews on Google Play. Change the contact information used in suggested replies.	Users without this permission can still view ratings and reviews but can’t reply to them.

Managed Google Play permissions

Create and publish private apps to your organization

Rights	Usage notes
Create, edit, and publish private apps which are only available to users within your organization.	This permission applies to private apps using Managed Google Play, and doesn't allow users to manage internal testing tracks, or publish public apps on Google Play.

Google Play games services permissions

Edit Google Play games services projects

Rights	Usage notes
Edit Google Play games services projects for all apps.	This permission is only available to users with "Account" level access. Users with this permission and the View app information and download bulk reports (read-only) permission can create new projects and link apps to existing projects. Users also need permission to access the game in the Google Developers Console.

Publish Google Play games services projects

Rights	Usage notes
Publish new Google Play games services projects for all apps. Unpublish and republish existing projects.	This permission is only available to users with "Account" level access. Users also need permission to access the game in the Google Developers Console.

Manage user access

Account requirements for invited users

When users are invited to access Play Console, they must sign in with a Google account using the same email address that the admin or Play Console account owner invited. Users can create a Google account using a new Gmail address (@gmail.com) or with an existing email address, such as a company email address.

If an invited user needs to access Play Console with a different email address, they need to contact the admin and ask them to resend an invitation to their preferred email address.

If a user doesn't accept an invitation and sign in within 30 days, the invitation will expire and the admin will need to resend an invitation.

View sent invitations

After you send an invitation, the user's email address will be listed with the status "Invite sent." If the user's access has an access expiration date, it will be included in their invitation. When the user accepts the invitation, the account owner will get a confirmation email and the user’s status will change to "Active."

Update account expiration dates

If you're the account owner, take the following steps to update users’ access expiration dates:

1. Open Play Console (Users and permissions > Manage users).
2. Select users to extend access expiry from the drop-down menu.
3. In the table, select the users whose access you want to extend and click Extend access.
4. Choose how long you want to extend access for and click Extend access.
5. Select Confirm to save your changes.

To individually update a user’s access expiration date, take the following steps:

1. Open Play Console (Users and permissions > User details).
2. Click anywhere on the user’s row in the user table.
3. On the User details page, check the box next to "Set access expiry."
4. Enter an access expiry date or choose one using the calendar.
5. Click Save changes.

Remove users

If you're the account owner, take the following steps to remove users’ access:

1. Open Play Console Users and permissions > Manage users).
2. Select users to remove from the drop-down menu.
3. In the table, select the users who you want to remove and select Remove.
4. Click Save changes.

To individually remove a user’s access, take the following steps:

1. Open Play Console (Users and permissions > User details).
2. Click anywhere on the user’s row in the user table.
3. On the User details page, select Remove user.

Error 403

If you get "Error 403" within Play Console, ask your account owner to grant you permissions for that app.

Permissions for integrated features

User permissions for Google Play game services

For a Play Console user to access Google Play game services information, the following requirements must be met:

Access	Requirements
View a Google Play game services project.	User must be able to view a linked Android app. To view Google Play game services projects that are not linked to an Android app, the user must have the View app information and download bulk reports (read-only) permission.
Create Google Play game services project, edit games, or link new apps.	User must have the View app information and download bulk reports (read-only) permission. User must have the Edit Google Play games services projects permission. User must have permission to access the Google Developers Console project for this game. For details, refer to the following section.
Access to Google Play game services financial data	User must have both the View financial data, orders, and cancellation survey responses and View financial data permissions. If the game is linked to multiple Android apps, a user only needs the View financial data permission for one linked app.

If you want to add a user to your project after a Google Play games services project has been created, you need to extend an existing user's Play Console rights and add the user to your Google Developers Console so they can edit and publish Google Play games services projects.

Here are the steps to add a user to your project on the Google Developers Console:

1. Sign in to the Google Developers Console.
2. Select a project.
3. On the left menu, select Permissions.
4. Near the top of your screen, select Add Member.
5. Type the email address of the user you added to Play Console.
6. Choose a permission level.
7. Select Add.

User permissions for the Google payments center

For another user to have access to reports on your Google payments center, you need to add the user on your Google payments center settings. Play Console permissions are separate from any permissions managed within the Google payments center.

Here are the steps to add a user to your Google payments center:

1. Sign in to the Google payments center.
2. On the left menu, select Settings .
3. Under "Payments users," select Manage Payments Users > Add a new user.
4. Follow the onscreen instructions to add the requested information.
5. Select Invite.

Related content

• Learn more about adding users and managing user permissions in Play Academy.