To help you keep track of the users that have access to your developer account, you can export a list of all users with access and their assigned permissions as a CSV file. This can be helpful if you want to audit which of your team members have a specific permission, for example.
Export a full user list
If you're the account owner, here's how you can export a full list of users with access to your developer account:
- Open the Users and permissions page in Play Console.
- Click Export user list to download your CSV.
Configure your user list
You can use the search box and filter at the top of the page to configure which users are displayed in the table and included in the CSV you want to export. This helps you to easily export user lists based on specific permissions, the apps they have access to, invitation status, or other search terms such as email domain or name.
If you’re an account owner or administrator, the CSV will contain information about all apps in your account. If you’re an admin but not an account owner or administrator, you’ll only see information about the apps that you’re an admin for. This ensures continued account privacy and security.
CSV format
Your downloaded CSV contains the following columns and fields:
Column/field | Description |
---|---|
|
The user’s email address |
Status |
The status of the user’s invitation. This can be:
|
Expiration time |
The date when access will expire for users who only have access for a limited time. |
Invitation time |
The date that the user was last invited to join your developer account. This field is not populated after an invitation is accepted. |
App permissions |
A list of each app that the user has access to, and which app-specific permissions they have. This is in the following format: {com.exampleApp1:PERMISSION_1;PERMISSION2};{com.exampleApp2:PERMISSION_1;PERMISSION3} |
Account permissions |
A list of every account-level permission that the user has. These apply to your whole developer account, account-level features such as Play Games Services, or every app within your account. |
App permissions
App permissions are limited to the specified app only. For example, a user with "CAN_MANAGE_ORDERS" for com.exampleApp1 cannot see or refund orders from com.exampleApp2
The table below lists the names app permissions are given the CSV export, what they’re called in Play Console interface, and a description of what they do.
Name in CSV |
Name in Play Console |
Description |
---|---|---|
CAN_MANAGE_PERMISSIONS | Admin (all permissions) |
Users with this permission get all other permissions for this app. They can also invite new users to your developer account, and add and remove permissions for other users who have access to the same apps. |
CAN_ACCESS_APP | View app information (read-only) |
View all information for this app, including any associated Play Games services projects–but not financial data. This permission does not allow users to edit information or make any changes in Play Console. To grant access to financial data, give users the "View financial data" permission. |
CAN_MANAGE_DRAFT_APPS | Edit and delete draft apps |
Can edit or delete draft versions of the app. This permission does not allow users to publish apps on Google Play. |
CAN_VIEW_FINANCIAL_DATA | View financial data |
View financial and sales reports; view buyer metrics on the user acquisition page; access the purchases API; and view revenue information for any associated Play Games services projects |
CAN_MANAGE_ORDERS | Manage orders and subscriptions |
View orders, refund orders and cancel subscriptions. Users also need the "View financial data" permission to view aggregate financial reports. |
CAN_MANAGE_PUBLIC_APKS | Release to production, exclude devices, and use Play App Signing |
Create, edit, and roll out releases to production, unpublish and republish apps, exclude devices in the device catalogue, and use Play App Signing to sign APKs. Users with this permission can publish apps to users on Google Play. |
CAN_MANAGE_PUBLIC_LISTING | Manage store presence |
Edit your store listing and run store listing experiments; edit pricing; manage in-app products; edit distribution information and content ratings; create and edit promotions; manage your public developer page on Google Play; and create and save filters to sort the device catalogue. This permission does not allow users to exclude devices in the device catalogue. |
CAN_MANAGE_TRACK_APKS | Release apps to testing tracks |
Upload draft apps; create, edit, and roll out releases to testing tracks; unpublish and republish apps that have already been published to a testing track; upload and modify .obb files; edit release notes for apps which are not active in production; and upload APKs for internal sharing. This permission does not allow users to publish apps to production on Google Play. |
CAN_MANAGE_TRACK_USERS | Manage testing tracks and edit tester lists |
Manage users, groups and domains on tester lists, disable testing tracks, update country targeting for testing tracks, and set up uploaders and testers for internal app sharing. This permission does not allow users to publish apps to production on Google Play. |
CAN_REPLY_TO_REVIEWS | Reply to reviews |
Reply to reviews on Google Play, report inappropriate reviews and change the contact information used in suggested replies. Users without this permission can still view ratings and reviews, but can’t reply to them. |
Account permissions
These apply across your developer account and to every app. For example, a user with the account permission "CAN_REPLY_TO_REVIEWS_GLOBAL" can see and reply to any review you get for any of your apps.
The table below lists the names account-level permissions are given the CSV export, what they’re called in Play Console interface, and a description of what they do.
Name in CSV |
Name in Play Console |
Description |
---|---|---|
CAN_MANAGE_PERMISSIONS_GLOBAL |
Admin (all permissions) |
Users with this permission get all other permissions for your developer account. They can also invite new users to your developer account, remove users, manage all other user's permissions, change access expiry dates, and view changes made in Play Console using the activity log. Some additional actions can only be done by the account owner, like agreeing to Terms of Service agreements. |
CAN_SEE_ALL_APPS |
View app information and download bulk reports (read-only) |
View all app information, including any associated Play Games services projects–but not financial data. Users with this permission can also download bulk reports, and will be able to view any new apps that you add to Play Console in the future. This permission does not allow users to edit information or make any changes. To grant access to financial data, give users the "View financial data" permission. |
CAN_CREATE_MANAGED_PLAY_APPS_GLOBAL |
Create and publish private apps to your organization |
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 does not allow users to manage internal testing tracks or publish public apps on Google Play. |
CAN_PUBLISH_GAMES_GLOBAL |
Publish Play Games Services projects |
Publish new Play Games services projects for all apps, and unpublish and re-publish existing projects. |
CAN_EDIT_GAMES_GLOBAL |
Edit Play Games Services projects |
Edit Play Games services projects for all apps. Users with this permission and "View app information (read only)" for all apps can also create new projects, and link apps to existing projects. |
CAN_MANAGE_DRAFT_APPS_GLOBAL |
Create, edit, and delete draft apps |
This permission does not allow users to publish apps on Google Play |
CAN_MANAGE_ORDERS_GLOBAL |
Manage orders and subscriptions |
View orders, refund orders and cancel subscriptions. Users also need the "View financial data" permission to view aggregate financial reports. |
CAN_MANAGE_PUBLIC_APKS_GLOBAL |
Release to production, exclude devices, and use Play App Signing |
Create, edit, and roll out releases to production, unpublish and republish apps, exclude devices in the device catalogue, and use Play App Signing to sign APKs. Users with this permission can publish apps to users on Google Play. |
CAN_MANAGE_PUBLIC_LISTING_GLOBAL |
Manage store presence |
Edit your store listing and run store listing experiments; edit pricing; manage in-app products; edit distribution information and content ratings; create and edit promotions; manage your public developer page on Google Play; and create and save filters to sort the device catalogue. This permission does not allow users to exclude devices in the device catalogue. |
CAN_MANAGE_TRACK_APKS_GLOBAL |
Release apps to testing tracks |
Upload draft apps; create, edit, and roll out releases to testing tracks; unpublish and republish apps that have already been published to a testing track; upload and modify .obb files; edit release notes for apps which are not active in production; and upload APKs for internal sharing. This permission does not allow users to publish apps to production on Google Play. |
CAN_MANAGE_TRACK_USERS_GLOBAL |
Manage testing tracks and edit tester lists |
Manage users, groups and domains on tester lists, disable testing tracks, update country targeting for testing tracks, and set up uploaders and testers for internal app sharing. This permission does not allow users to publish apps to production on Google Play. |
CAN_REPLY_TO_REVIEWS_GLOBAL |
Reply to reviews |
Reply to reviews on Google Play, report inappropriate reviews and change the contact information used in suggested replies. Users without this permission can still view ratings and reviews, but can’t reply to them. |
CAN_VIEW_FINANCIAL_DATA_GLOBAL |
View financial data, orders, and cancellation survey responses |
View financial reports, sales reports and orders; view buyer metrics on the user acquisition page; access the purchases API; view revenue information for any associated Play Games services projects; and download written responses to the cancellation survey. |