Your store accounts, step by step

Applies to the Managed Launch service · Questions: publishing@posra.app

Your app, your accounts. Posra publishes your app to your Apple Developer and your Google Play Console account — never ours. You are the developer of record on both stores. You own the app, the listings, the signing key and the reviews. We work inside your accounts with access you grant and can revoke at any time, and if you ever leave, everything stays with you.

This page covers the five things only you can do: create the two developer accounts, get verified, invite us with the smallest role that lets us work, give us a push key for iOS, and remove us when we're done. Budget about an hour of your own time, spread across a few days while Apple and Google verify you. Every step below can be done on a call with us if you'd like company.

Before you start

An email address you control for each account. Use a role address such as apps@yourstore.com rather than an employee's personal address, so the account outlives staff changes.
A phone that can receive two-factor codes, again ideally not one person's personal phone.
A payment card for the store fees: about $99/year for Apple and a one-time $25 for Google. These are paid to Apple and Google, not to Posra.
Your legal business details. Registered name, address, and for companies enrolling with Apple, a D-U-N-S number. Apple can look yours up or request one for free; allow up to two weeks if you don't have one.
A privacy policy page on your own domain. Both stores require a URL. Your WooCommerce site's existing privacy page usually qualifies.

1. Apple Developer Program

Apple verifies the identity behind every developer account, so this step has to be done by you. Enrollment as an organisation puts your business name on the App Store and lets you add team members, which is what we need. Enrollment as an individual shows your personal name and cannot add team members, so for a Managed Launch please enrol as an organisation.

Create or sign in with an Apple ID at developer.apple.com/programs/enroll. Turn on two-factor authentication if it isn't already.
Choose Organization, enter your legal entity name, D-U-N-S number and website. The person enrolling must have legal authority to bind the organisation.
Apple may phone or email to confirm. This is the slow part; anything from two days to two weeks.
Pay the annual membership fee.
Sign in to App Store Connect once and accept the latest agreements under Business → Agreements. Apple blocks submissions while an agreement is pending, and only the Account Holder can accept them.

Invite Posra to App Store Connect

In App Store Connect, open Users and Access and click +.
Email: publishing@posra.app. First name: Posra. Last name: Publishing.
Role: App Manager. Do not grant Admin, and never Account Holder.
Leave "Access to Certificates, Identifiers & Profiles" enabled. We need it to create your app's signing certificate and provisioning profile inside your account.
Send the invitation. We'll accept it and confirm by email.

We then create an App Store Connect API key of our own under your team. It is tied to our user, so removing the user (below) revokes it too. We never ask for your Apple ID password.

2. Google Play Console

Google also verifies identity and, for organisations, business details. A Play account created after late 2023 as a personal account must run a closed test with about 20 testers for 14 days before it can publish to production. An organisation account does not have this requirement, so if you are a registered business, choose that.

Go to play.google.com/console/signup with a Google account you control (a Google Workspace address on your domain is ideal).
Choose Organization where you can. Enter the legal name, address and a contact phone number.
Pay the one-time registration fee.
Complete identity verification when prompted. Google may ask for a business registration document or D-U-N-S number and can take a few days.
Accept the Developer Distribution Agreement.

Invite Posra to Play Console

We'll create the app entry first so the invitation can be scoped to that app alone. Once we've asked you to:

In Play Console, open Users and permissions and click Invite new users.
Email: publishing@posra.app.
Under App permissions, add your app and choose the Release manager preset. Leave account-level permissions off.
Send the invitation.

Google's closed-testing requirement means we may also ask you for a list of tester email addresses from your staff and regular customers. They install the app, open it, and that's all.

3. A push-notification key for iOS

Push notifications on iPhone are delivered by Apple, and Apple only accepts them when they're signed with a key from the account that published the app: yours. So we need one APNs authentication key from your Apple Developer account. It can only sign push messages; it can't publish, change or read anything else.

In the Apple Developer portal open Certificates, Identifiers & Profiles → Keys and click +. This needs the Account Holder or an Admin, so it's usually you rather than us.
Name it Posra push, tick Apple Push Notifications service (APNs), continue and register.
Download the .p8 file once (Apple won't offer it again) and note the Key ID shown next to it.
Paste both into the publish wizard in the builder, or send them to us with your intake.

We register your app for push in a Firebase project that Posra owns and operates, and attach your key to it. Your Google account is never involved. Android needs nothing from you: the same registration covers it.

4. Signing keys

On Android, your app is signed with a key that must stay the same for every future update. We create it for you, enrol the app in Play App Signing so Google holds the master copy, and export the upload key to you at handover. On iOS, certificates live inside your Apple account and expire yearly; renewing them is part of the Care Plan.

5. Removing our access

Do this any time you like. We'll remind you when the launch is handed over, and again if you cancel the Care Plan.

App Store Connect: Users and Access → select Posra Publishing → Remove. This also revokes any API key we created.
Play Console: Users and permissions → select publishing@posra.app → Remove user.

Nothing else changes. Your app stays on both stores, your listings and reviews stay where they are, and the Android upload key we exported to you keeps working.

If you'd rather not invite us

You can instead generate credentials and paste them into the publish wizard in the builder dashboard: an App Store Connect API key with App Manager access for iOS, and a Play service-account JSON with release permissions for Android. They are encrypted at rest, every read is logged, and we delete them when your launch is handed over. We recommend the invitation route above because it leaves nothing with us that could outlive your consent.

Never share these

Your Apple ID or Google account password.
Two-factor codes, unless you're on a call with us and are reading a code Apple sent for our invitation.
Passport or ID scans, tax documents, or bank details. The platforms ask for these directly from you, on their own pages.

If anyone claiming to be Posra asks for any of these, stop and write to support@posra.app.