# Review data access before sharing an ASO report

URL: https://storelift.net/guide/aso-report-access-review/
Language: en
Updated: 2026-10-02

An ASO report can combine public store observations with private tracking choices and connected account data. Those have different sharing implications. Before sending a report or using an integration, establish which data the recipient needs and what access the chosen route provides.

## Investigation steps

1. List the report's sources and mark account-specific fields such as revenue, campaign activity or internal keyword selections. A public app identifier does not make every associated field public.
2. Check the current workspace role, export contents and integration permissions. Reading a report and allowing an integration to change tracked data are separate capabilities.
3. Preview the exact shared artifact or requested action. Keep credentials and unrelated account data out of exported notes, and confirm the destination and intended audience.

## Worked interpretation

Illustrative case: a client needs a country-specific rank summary, while the working export also includes another app and account revenue. Prepare the intended subset rather than assuming that the recipient's request authorizes the whole working file.

## Decision and next check

Use the product's supported role and permission controls and review access when responsibilities change. For an assistant integration, inspect the proposed action and its scope before approving writes. Keep the analysis useful while sharing only the data needed for that task.

## Related Storelift feature

Read App Store MCP server for the available product data and its scope. Keep the app, storefront, period and measurement status with the observations used in your report.