Which App Store Connect roles can edit your listing
Four roles can open your app information page and save a change. Account Holder, Admin, App Manager, and Marketing see the same fields: app name, subtitle, keyword field, description, screenshots, and custom product pages. Apple states the requirement with identical wording across app information, localization, tags, and product pages. Required role: Account Holder, Admin, App Manager, or Marketing. Memorize that list. Nobody else on your team can save a metadata edit, no matter how senior they look on paper. Our App Store Connect setup guide walks through the rest of that page, so this guide stays on access and handoffs.
The surprise is the Developer role. It sounds like the most powerful seat in the account because it builds and ships the binary, yet on the metadata side it can only read. A developer can push builds to TestFlight and keep the release train moving while remaining unable to fix a typo in the subtitle. Apple drew this line on purpose. Code access and storefront access are different risks, so they live in different roles. Marketing sits on the storefront side of that line. It edits the name, subtitle, keyword field, description, promotional text, screenshots, and custom product pages, which is the full surface a translator touches. It cannot submit versions for review, upload builds, change pricing and availability, or run TestFlight, which is why it fits outside help. Scope it to one app and the contractor never sees the rest of your catalog. That single property, edit rights without ship rights, is what makes the Marketing role the translator seat.
One more distinction saves confusion later. Roles decide who may edit, not when edits reach shoppers. Keyword and subtitle changes still ship with a version release, the same as always. Access only decides who gets to type them in. So plan the handoff while the version is still editable. A translator who arrives after the version locks will deliver perfect strings that sit unread until the next cycle.
Give your translator the Marketing role, step by step
The invite takes five minutes once you know the path. You'll need Account Holder, Admin, or App Manager rights yourself to invite anyone, so borrow the account owner for a quarter hour if that isn't you.
- Open App Store Connect and go to Users and Access, then the People tab.
- Click the plus button and enter the translator's name plus the email tied to their Apple ID.
- Assign the Marketing role and nothing else. Skip Admin even when it feels faster.
- Restrict the invite to the one app the translator will work on (details in the next section).
- Leave analytics reports access off unless the translator truly needs download numbers. Most don't.
- Tell the translator which version is editable right now, so edits land where they can ship.
- Confirm one saved edit together, a promo text tweak works well, before the real work starts.
That last step sounds fussy and it prevents the classic failure. Access problems surface as silent save refusals, not error banners. A two-minute live check beats a week of finished translations that nobody can paste into place.
Scope the invite to one app
Five roles support per-app restriction: App Manager, Developer, Marketing, Sales, and Customer Support. Pick one of those and Apple lets you pin the person to chosen apps. Admin and Finance cannot be fenced this way. They always see every app on the team, so never hand those to outside help for a text job.
Then mind the reports trap. Granting a Marketing user access to analytics reports unlocks visibility into every app, even when their role was scoped to one. Apple treats reports access as its own grant with its own reach. If you want a contractor locked to a single app, leave reports off. Translators need your words and your limits, not your download charts.
Decide the ending at the start. For a one-locale job, remove the invite when you approve delivery. For ongoing help across a release calendar, keep the scoped seat and revisit it each quarter. Either way, write the plan in the invite note or your own task list. Orphaned seats pile up fast as your locale count grows, and each one's a door you forgot.
What to hand your translator besides access
Access lets translators save. A brief lets them save the right words. Send both in the same message and the first draft usually fits. Pack these five items:
- Source text with context. Export the current English fields and add one line on what the app does and who pays for it. Translators guess less when they know the buyer.
- Field limits in writing. Name 30, subtitle 30, keyword field 100, promotional text 170, description 4000. Flag that German and Finnish swell past English length, so captions drafted tight survive layout. Our German market guide shows the packing problem up close.
- Screenshot context. Share the caption text or the exported shots so translators see where each string lands. A headline that fits a description box can still break a screenshot caption.
- Keyword rules, not keyword translations. Each locale needs its own researched terms, never a translated English list. Point translators at your researched list per market and forbid inventing extras. Our keywords-field guide and our cross-localization guide set the method.
- Review timing. Name the version the strings must land in and the date it locks. Translators who know the window deliver early. Translators who don't learn about the lock from you.
Match the method to the budget. Machine translation plus native review covers most indie listings at a fair price, and our machine-translation workflow shows the handoff order. Full human translation earns its keep on the name and subtitle, the two fields that rank. Our services-versus-DIY comparison helps you pick the split before you hire.
Mistakes that cost indie teams a submission cycle
- Granting Admin for a text job. Admin sees every app and can touch pricing, builds, and banking. Marketing edits the same words with none of that reach.
- Assuming the Developer role covers metadata. It reads the listing and ships the binary. It saves nothing on the storefront side.
- Sharing your own login instead of inviting. Shared logins leave no trail of who changed what, and a password reset can lock the whole team out on submission day.
- Granting reports access by habit. One checkbox undoes your per-app scoping and opens the full catalog.
- Inviting after the version locks. Perfect strings with nowhere to land wait a full cycle. Invite while the version is editable.
- Skipping the glossary. The same feature translated three ways across name, subtitle, and screenshots reads sloppy in every one of them. One term list, shared with every translator.
Run our QA pass before the version submits. Every string inside its limit, screenshots rendered in the storefront tongue, no English leftovers. Access gets translators into the room. The QA pass makes sure what they wrote can ship.
How App Store Localizer fits
Most translator handoffs stall on preparation, not permission. Somebody must export the current fields, draft each locale, render the screenshots, and pack it all into a brief. App Store Localizer does that first half in one pass. Paste your public App Store URL and the tool pulls your title, description, icon, and screenshots through Apple's public lookup. It translates the screenshots plus the title, subtitle, description, and the 100-character keyword field into 20 or more target locales, using free heuristics drawn from your live listing. Output covers iPhone 14 Plus and iPad Pro sizes, ready to hand over or upload.
Pair it with the access setup above. Generate the translator-ready package first, then invite the translator under the scoped Marketing role to review and refine inside App Store Connect. You get machine speed with a native eye on the final words, and the contractor edits real fields instead of spreadsheets. Pricing is one-time per listing: Starter at $19.99 covers 3 languages with all screenshots, and Global at $99.99 covers all supported languages. One honest limit: the tool handles the store listing, screenshots plus metadata, not interface strings or code, so keep your normal string workflow for the binary itself.
Frequently asked questions
- Which App Store Connect role should I give a translator? The Marketing role, restricted to their one app, with reports access off. It edits every field a translator touches: name, subtitle, keyword field, description, screenshots, and custom product pages. It cannot submit versions, upload builds, or change pricing, so it fits outside help exactly.
- Can someone with the Developer role edit my keywords? No. The Developer role reads metadata and ships binaries. It cannot save changes to the keyword field, subtitle, description, or screenshots. If your translator holds Developer access today, add the Marketing role or move them to it before work starts.
- Does the Marketing role let contractors submit my app for review? No. Submitting versions stays with Account Holder, Admin, and App Manager. A Marketing user can prepare everything and stage it, but someone with a higher role presses the submit button. Keep that split. Preparation and submission deserve different hands.
- Will my translator see my other apps? Not if you set the invite up right. Restrict the Marketing role to the one app and leave analytics reports access off. Either half alone leaks: Admin cannot be scoped at all, and reports access opens every app regardless of scoping. Check both boxes, then verify with a test login if your catalog is sensitive.
- When do translated keywords go live? With the next version release that carries them. Role access decides who may type the edit. The release train decides when shoppers see it. Plan translator delivery for while the version is still editable, and confirm the strings made the build before it locks.
Paste your App Store URL into App Store Localizer tonight and hand your translator a finished draft instead of a blank form. Then set up the scoped Marketing invite above, and let the next version carry all of it live.