Team and roles
Who's in, what they can see, and who's allowed to push things live.
Members and roles
A role decides which pages exist for that person. The menu is filtered by the permission set the API serves, so what a teammate can't see is exactly what the API would refuse them anyway — there's no client-side-only hiding here.
Read access and write access are separate: someone can study the ASO drafts without being able to push them to App Store Connect.
Inviting
Invites go out as a single-use link. The recipient sets their own password on the way in — nobody sends a password to anybody.
Roles at a glance
| Role | What they can do |
|---|---|
| Owner | Everything, plus billing, connector keys and team management. |
| Marketing | Every growth surface, and can push live. No keys or billing. |
| UI/UX Designer | Creative surfaces — drafts screenshots, captions and posts, but can't publish them. |
| Developer | Read-only on apps, competitors, keywords, ASO and performance. |
| Tester | Read-only across everything the team ships. |
On this page in the app
- Members
- Invite someone