App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-03-04

App Store Connect roles: who can submit and touch money

Account Holder, Admin, App Manager, and least privilege for listing agencies. No password sharing. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66

In listing agency work, the worst scene is a consultant who can change banking and tax, delete apps, and download distribution private keys—while the client thought “they just click Submit.” Connect roles separate duties: Account Holder owns legal and financial root, Admin manages users and cert policy, App Manager is closer to daily metadata and build flow—but exact buttons change with console updates, per official pages.

Goee (goee.cc) explains role boundaries, minimal access for agencies, and how to state “no passwords, no Holder takeover” in agency handoff. Not legal advice; verify the Users and Access UI live.

What this guide solves

Real losses from permission chaos:

  • Vendor Admin changed agreements or paid-app contract—client discovers payout broken months later.
  • Apple ID password shared widely—2FA and device list out of control.
  • Listing lead lacks Submit for Review on deadline—can upload build but not send.
  • Marketing deletes TestFlight group—external links dead, blocking TestFlight flow.
  • Collaboration ends without user removal—ex-staff still see sales/finance.
  • “Upload IPA is enough” but signing handoff still needs client-held keys.

Who should read

  • Owner / legal entity: who gets which role; Holder stays tight.
  • In-house listing lead: App Manager + target app access for vendors—not Admin.
  • Agency buyer: acceptance includes “users removed at end.”
  • Finance: who sees payouts—avoid accidental touch by marketing.
  • CI engineer: API upload keys vs human Connect login—two chains.

Read developer account setup first if new.

Core practice

Role map (conceptual)

Stable concept layers; exact matrix per official UI:

Role (common name) Typical scope Do not give vendors
Account Holder Legal entity, contracts, banking/tax root Holder itself
Admin Invite users, cert policy, most app admin Unless internal CIO
App Manager Metadata, builds, submit, some reports —
Developer (if used) Certs, identifiers, technical resources Depends on CI
Finance / Reports Sales, payouts Split from listing ops
Customer Support Review replies, etc. Usually not agency

Multiple roles on one person = union of powers—trial on sandbox app before granting.

Minimal agency access

  1. Dedicated user: @vendor.com, not client personal Apple ID.
  2. App-scoped: target bundle only—not “all apps.”
  3. Close the loop: select build + edit store + submit + read review status; privacy labels if agency fills them.
  4. No money: no tax, bank, contract sign.
  5. No Holder transfer: legal act—out of listing scope.
  6. No passwords: invite only; client keeps Holder device control.
  7. Revoke on exit: remove user or shrink app access; screenshot archive.

With signing handoff: agency often client CI uploads + App Manager submits; distribution private key stays client-side.

Work split table

Task Client Agency Notes
Enroll / contracts Holder —
Create app record Optional Optional Log in handoff
Upload build Eng / CI Optional API key ownership
Metadata / screenshots Product + design Entry Materials
Submit and notes — Common Test account
Agreements / banking Finance —
Appeals Product decision Draft help Appeal

2FA and devices

Holder 2FA on client legal/IT. Few Admins who can reset users. Agency uses Authenticator—no shared SMS SIM.

App Store Connect API

CI upload ≠ web roles. Key permissions map to roles; treat Issuer ID, Key ID, .p8 as secrets—log in handoff, not group chat.

Audit before each release

□ Agency user still scoped to needed apps only
□ No stray Admin
□ Former staff removed
□ No unknown API key names
□ Client can still submit (disaster recovery)

Copy-paste templates

ASC access request (client → vendor)

Please invite user@agency.com:
App: ___ (Bundle ID ___)
Role: App Manager (or current minimal equivalent)
Needs: edit store, select build, submit, read review messages
Must NOT: contracts/banking/tax, delete app, user admin
Until: ___ or project end
Confirm Admin not granted

End-of-collaboration cleanup

End date:
Removed users: ___
Revoked API keys: ___
Client self-test submit: Y/N
Archive screenshots:

Common mistakes

Mistake Outcome Fix
Password sharing Account takeover Invite only
Everyone Admin Finance risk Minimal role
All apps open Wrong-project edits App scope
Ignored API keys Hidden backdoor Key inventory
No DR drill Stuck if agency ghosts Client retains submit
Certs mixed with ASC Upload fails Signing handoff

Permission hygiene as org grows

Shared Admin works at five people; at thirty it is an incident factory. Semiannual Connect user audit: roster, roles, app access, recent logins (as console provides). Offboard same day—not month-end batch.

Multi-subsidiary on one program: app-scoped access per business unit. Agency for product A must not see B sales/metadata. Holder stays a small controlled group—no “anyone can invite Admin.”

Enterprise vs App Store programs differ—do not mix internal distribution with store release permissions. Two handoff sections if both exist.

Legal alignment: who signs Export Compliance, content rights, government questionnaires—often Holder or specific Admin; agency prepares, does not sign for client. See rejection codes and materials.

If agency account is compromised

Disable suspect user, rotate API keys, audit recent metadata/build changes, Holder password + device audit. Do not wait until store page shows gambling copy to open user list. Pair quarterly with signing handoff backup drill—under one hour.

FAQ

Is App Manager enough to submit?
Usually yes—verify live permissions; dry-run before deadline.

Client wants PDF guidance only?
OK—timing is client risk; Goee can remote walkthrough—still no passwords.

Several consultants—how many accounts?
One person one user for audit—no shared agency@.

Review without finance?
Reports read-only or App Manager review view—per console.

Temporary Holder to agency?
No—legal and banking bound. Agency does not need Holder.

Next steps

Telegram @hagee66 · No approval promise · Role matrix per official pages.

Back to guide library