To publish and maintain your mobile app, our team requires access to your developer accounts (Apple App Store Connect and Google Play Console). Adding our team email as an Admin ensures:
Seamless App Publishing: We can submit builds, update app versions, and manage releases on your behalf.
Faster Approvals: Direct access avoids back-and-forth with credentials, reducing delays in review and publishing.
App Maintenance: We can quickly respond to compliance changes, fix rejected builds, and update certificates/keys.
Ongoing Support: We can manage permissions, troubleshoot errors, and ensure your app remains live and compliant.
Security Best Practice: Instead of sharing your personal login, Admin access keeps accounts secure and auditable.
How to add the provided email as an Admin
? For Apple App Store Connect
Log in to App Store Connect.
Navigate to Users and Access from the main dashboard.
Click the “+” (Add) button.
Enter the team email:
>> [Insert the email - appletestkb@gmail.com]Assign the role Admin (full permissions required to manage apps).
Click Invite.
The team will receive an email invitation — once accepted, we’ll have access to manage your app.
? For Google Play Console
Log in to Google Play Console.
From the left-hand menu, go to Users and Permissions.
Click Invite New User.
Enter the team email:
>> [Insert the email - appletestkb@gmail.com]Under Role, select Admin (to allow app publishing & management).
Check App Permissions → All Apps so we can manage every app in your account.
Click Invite User.
The team will accept the invite and gain access.
✅ Best Practices
Always grant Admin access (not just Developer) to ensure we can handle publishing, certificates, billing, and compliance tasks.
Do not share your personal login credentials — invites are the secure method.
If you ever need to revoke access, you can remove the team email from your console.
? Adding us as Admin early helps prevent launch delays and ensures smooth app operations.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article