Team approvals: review store creative without losing the conversation

A screenshot can be ready to upload while its feedback is still scattered across chat messages. A useful review workflow keeps the preview, the conversation, and the decision attached to the same file. Team review brings those details into your app’s Store assets page.

Start with the file that needs review

Open an app, go to Store assets, and find Team review. The panel shows the current screenshots, icons, and other creative, with a preview, version number, review status, and recent feedback. Use the status filters or search to find the file you need.

Open a review to see the creative beside its discussion and activity. This gives reviewers the file’s context before they leave a comment or record a decision.

Who can approve, request changes, or comment?

• Owners and admins: approve a current file, with an optional note, or request changes with feedback explaining what needs work.
• Every organization member: add a comment without changing the formal review status.
• Each organization has its own permissions: being an admin in one workspace does not grant approval authority in another where you are a member.

No special designer or product-manager role is required. The workflow follows the organization’s existing Owner and Admin permissions, and it also works when an owner reviews their own creative.

A comment and an approval do different jobs

Use Send comment to discuss an idea, ask a question, or explain a change. A comment saying “looks approved” is still a comment. Use Approve file to record a formal approval, or write feedback and select Request changes when the current version needs another pass.

These actions make the next step visible without interpreting casual messages as decisions. Members can request another review of a decided current file when it needs to be reconsidered.

New file, fresh review

Approval belongs to the exact version that was reviewed. Uploading a replacement starts that new version as Awaiting review. The old approval does not carry across to different creative.

Use the version selector to read earlier discussions and decisions. Previous versions can still receive comments, while approval and change-request actions apply to the current file. A practical loop looks like this:

1. Upload the creative and open its review.
2. Collect comments and have an owner or admin record a decision.
3. When changes are requested, upload the revised file as a new version.
4. Review that version and keep its sign-off with its own conversation.

Bring sign-off into the wider release workflow

Team sign-off is an internal record of feedback on creative. It does not submit content to Apple or Google or introduce a publishing approval gate. Use it alongside pre-release copy, configuration, and readiness checks, then follow the relevant store’s submission process.

You can also compare public competitor listings as you plan your next update. Competitor research helps you observe changes; your team review records the decisions about your own creative.

Choose the capacity your workflow needs

Basic includes owner sign-off and comment history in its owner-only workspace. Team supports up to 10 members for shared feedback and review. Compare plan allowances, or follow the complete team review workflow before starting your next release.