App Store Access Requirements for Publishing Apps on Apple and Google Play Store
Table of Contents
Scope
Intended Audience: White Label Partners
The following article will cover the App Store access requirements for publishing apps on Apple and Google Play Store for Branded Cloudie Connect.
Requirements
- Access to Apple and Google Play developer accounts
To publish your branded mobile app on the Apple App Store and Google Play Store, Tragofone requires appropriate access to your respective developer accounts. This ensures we can manage app uploads, updates, certificates, and listing configurations on your behalf. This guide outlines the access levels and roles you need to assign, so our team can efficiently handle app deployment while keeping your store ownership and control intact.
Apple Developer Account Access Requirements
To enable Tragofone to submit and manage your iOS app on the Apple App Store, please ensure the following requirements are met:
Account Type Requirement
Note: It is strongly recommended to use an Organization Account (rather than an Individual or personal account) for both Apple and Google developer platforms.
- You must have an Apple Developer Program with an Organization/Individual Account.
- This is necessary to add team members and assign roles.
App Store Connect: Inviting Tragofone to Your Team
- Go to Apple App Store Connect.
- Log in using your Apple ID linked to the developer account.
- From the home dashboard, click on “Users and Access.”
-
Click the “+” (Add User) button.
- Enter the first name, last name, and email provided by Tragofone.
-
Under Roles, select:
-
App Manager or Admin (if you need to provide broader access).
Note: If you assign the Admin role to Tragofone, all necessary permissions including app creation, certificate access, and distribution rights will be granted by default. This is the simplest way to ensure complete access for app setup and publishing without needing to manage individual permissions manually.
-
App Manager or Admin (if you need to provide broader access).
- If you assign the App Manager role to Tragofone, please ensure you enable the checkbox for Access to Certificates, Identifiers & Profiles, especially if we’ll be managing app signing and provisioning.
-
Additionally, make sure the following permissions are granted mandatorily to support a smooth publishing workflow:
- Access to Cloud Managed Distribution Certificate
- Create Apps
-
Click Next to send the access request.
Required Role and Permissions
- Invite Tragofone using the email address shared with you.
- Assign the "Admin" or "App Manager" role under Users and Access.
-
This role will allow us to:
- Create and manage App Store Connect entries
- Submit builds for review
- Manage certificates and provisioning profiles if needed
(Optional) Provide App-Specific Permissions
If you don’t want to give account-wide access, you can assign app-level permissions.
Follow the steps below:
- In Users and Access, select the invited user.
- Under Apps, choose the specific app(s) you want the developer to manage.
-
Toggle permissions as needed:
- View Only – Read-only access.
- Access to TestFlight – Upload & manage test builds.
- App Manager – Full control for that app only.
- (Optional) Create & Download iOS Certificates
Step 1: Login
- Go to: https://developer.apple.com/account.
- Navigate to Certificates, Identifiers & Profiles.
Step 2: Create Certificate
- From the sidebar, go to Certificates → All.
- Click the “+” button.
-
Select certificate type:
- Apple Development – For testing on devices.
- Apple Distribution – For submitting to the App Store.
- Click Continue.
Step 3: Generate CSR
-
On your Mac:
- Open Keychain Access.
- Go to Certificate Assistant → Request a Certificate from a Certificate Authority.
- Save the .csr file.
Step 4: Upload CSR & Download Certificate
- Upload the .csr file on the Apple Developer portal.
- Download the generated certificate (.cer) and install it on your Mac.
Step 5: Export as .p12 (if needed)
- Open Keychain Access, find the installed certificate.
- Right-click → Export → Save as .p12 file.
- Set a password for secure sharing with developers.
These permissions and steps allow Tragofone to manage app signing, create app records, and upload builds directly to App Store Connect.
Google Play Console Access Requirements
To publish and manage your branded Android app on the Google Play Store, Tragofone will need access to your Google Play Console. Below are the account type recommendations, required roles, and step-by-step instructions for granting access.
Account Type Requirement
- We strongly recommend using a Google Play Console Organization account (associated with a business domain).
- Although apps can be published using an individual account, but due to stricter review processes like manual app reviews, identity verification, and extended app testing timelines that can delay approvals by 3–4 weeks or more.
- An Organization account helps ensure faster approvals and better long-term manageability.
How to Grant Access – Step-by-Step
- Go to Google Play Console.
- Log in with your developer account.
- From the left menu, click Users and Permissions.
-
Click the Invite New User button.
- Enter the email address (must be a Google account).
-
Choose from predefined roles:
- Admin → Full access to everything.
- Non Admin user → limited access.
-
Click Invite to send the invitation.
Permissions and Role to Assign
- Invite Tragofone using the email address provided to you.
-
Assign the role of Admin (as tragofone would require almost all permissions)
Providing the appropriate access ensures Tragofone can efficiently manage your app's listing, updates, and release process, while you retain full control of your Google Play Console account.
What Will Be Managed by Tragofone
Once access is granted, Tragofone will handle the complete app deployment process on your behalf, including:
- Uploading app builds and submitting updates to both the Apple App Store and Google Play Store.
- Managing store listings, including app descriptions, metadata, keywords, and localised content.
- Adding and updating app screenshots, feature graphics, and promotional assets as required.
- Coordinating app release timelines, including phased rollouts or staged publishing.
- Handling signing certificates and provisioning profiles, if access is provided (Apple) or if Play App Signing is enabled (Google).
- Generating and integrating the FCM configuration file from Firebase Console, which is essential for enabling push notifications.
Security and Confidentiality
Tragofone takes your data and account privacy seriously. We will only access what is necessary to manage your app’s publishing, updates, and store presence.
- We do not access or modify any other apps, settings, or configurations.
- Permissions will be used solely for the scope of work agreed upon, such as uploading builds, managing metadata, and handling certificates.
- You will retain full ownership and control of your Apple and Google developer accounts at all times.
- Access can be reviewed or revoked by you at any point as needed. Frequently Asked Questions (FAQ)
Q: Can I limit Tragofone’s access after the app is published?
Yes, once the app is successfully published and no further updates or changes are planned, you can downgrade or remove Tragofone’s access from your developer account. However, continued access is recommended if you expect future updates, version rollouts, or store listing changes.
Q: How long is access needed?
Access is typically needed for as long as Tragofone is responsible for managing app updates, metadata, or store presence. If your team takes over future updates, Tragofone access can be safely removed once the handover is complete.