Metadata access
Timeline reads every version and localization of your metadata. Rankings uses the same access to know which apps and keywords to track, then checks public App Store search.
StoreGit works through an App Store Connect API key. The role you give that key decides which parts of StoreGit can load, so give it the smallest role that covers what you use.
Choose what you'll use. StoreGit asks for the lowest roles that cover it.
Developer covers Timeline and Rankings, and shows App Info read-only.
App Manager, Marketing or Admin also work, with more access than StoreGit needs.
Each StoreGit tab needs one of these App Store Connect roles. Rows that match your setup above are marked.
| Role | Timeline and RankingsView history and ranks | App InfoEdit and commit | AnalyticsReports |
|---|---|---|---|
| Admin | |||
| App Manager | – | ||
| Marketing | – | ||
| Developer | – | – | |
| Sales and Reports | – | – | |
| Finance | – | – | |
| Customer Support | – | – | – |
App Info shows your current metadata with any role that can open Timeline. Editing and committing need App Manager, Marketing or Admin.
Timeline reads every version and localization of your metadata. Rankings uses the same access to know which apps and keywords to track, then checks public App Store search.
Viewing App Info uses the metadata Timeline already loaded. Committing changes, adding languages and changing screenshots need a role that can edit your App Store metadata.
Analytics reads App Store Connect's analytics reports. The first time, StoreGit asks App Store Connect to start generating them, which can take a day or two.
One key with the Developer role covers your setup.
You can't change a team key's role after you generate it. Revoke it in App Store Connect, generate a new key with the role you need, then connect the new key in StoreGit.
Apple's guides: Creating API keys for App Store Connect API and Role permissions.