Share analytics with another studio
In Settings, Team, the receiving studio owner creates an invitation code. Give it privately to the source studio owner, who opens Settings, Team or /share/accept, reviews the destination and explicitly selects games. The code expires after seven days and works once.
Recipients can read game analytics and digests, including cross-game comparisons and the breakdowns by country and device. They cannot change games, read ingest keys or configuration, ask the analyst, read feedback, or manage exports. Either studio owner can revoke access immediately. Sharing never transfers ownership.
API and MCP reads use the receiving token's studio allowance and balance. Project-restricted tokens cannot read shared games. Use a studio-scoped token with only the tools you need. Shared games are marked read only in the game list.