Role structure in Console

The Users and permissions page lists everyone who can access the account. The account owner sits at the top and can manage users, view finances, publish apps and handle the payments profile. Other members get account permissions and app permissions separately so only parts of the Console are open to them.

Permission dimensions at a glance

DimensionWhat it allowsHandover note
Account ownerManage users, finances, payments profile, ownershipMust be you, not them
Admin-type permissionsManage users and app settingsAdmin alone does not mean you control the account
Release and versionsCreate releases and submit for reviewGrant to developers as needed
Financial dataView revenue and reportsOnly necessary people
App-level permissionsLimited to one appGood for contractors and partners

The principle is least privilege: each person gets only what their work needs.

Also useful in this topic cluster:

Why 'being admin' is not enough

A common handover problem: the buyer is invited as admin while the other side keeps owner. You can operate the account on the surface, but the owner can remove you, change payments details or transfer the account at any time. After handover you should be owner, or the written terms should say when and how owner is transferred.

If the account type cannot transfer ownership directly, the written terms must spell out the alternative rather than 'admin now, sort it later'.

Acceptance actions

  1. Confirm you are owner or the agreed role
  2. List all users and permissions and save screenshots
  3. Remove the seller and unrelated people; keep necessary partners
  4. Invite your admins and developers with least privilege
  5. Require two-step verification for every member
  6. Record the date of permission changes in handover docs

Refresh after each step to confirm the state and keep screenshots as a record.

Granting access to your team

  • Release permission to the dev lead; financial data only to finance or the owner
  • Contractors and partners use app-level permissions with an end date
  • Remove leavers immediately, not at month end
  • Review the member list regularly, for example quarterly

Writing down who has which permission and why keeps things controlled through staff changes.

The permission structure also affects app signing and upload key reset: only members with the right permissions can manage signing or submit a reset request. If nobody has them after handover, fix permissions first. See the Play App Signing and six-fields guides.

Related reading:

Related

Related desks