Automation
Rule scopes and precedence
How organization, account, and app rules resolve when more than one could apply to the same review
A rule is attached to one of three scopes. This is what lets an agency run relaxed automation across most clients while keeping one sensitive app on drafts only.
The three scopes
| Scope | Covers | Typical use |
|---|---|---|
| Organization | Every app you have connected | Your baseline policy |
| Account | Every app under one account | One client, or one App Store Connect team |
| App | A single app | An exception — stricter or looser than the baseline |
Most specific wins
When a review arrives, ReviewDesk looks for an app-level rule first, then an account-level rule, then the organization rule. The first one it finds is the one that runs.
A worked example
Suppose you configure:
- An organization rule: auto-send some, positive only, professional tone
- An account rule on "Beta Client": draft only, all reviews
- An app rule on "Beta Fitness" (inside Beta Client): auto-send all, positive only, enthusiastic tone
| Review arrives for | Rule used | Result |
|---|---|---|
| Beta Fitness | The app rule | Positive reviews auto-sent, enthusiastically |
| Any other Beta Client app | The account rule | Everything drafted, nothing sent |
| Any app outside Beta Client | The organization rule | Positive reviews auto-sent, professional tone |
When no rule matches
If no rule covers an app at any scope, nothing happens for its reviews — no drafts, no sends. This is the state every new organization is in, and it is why the Quickstart treats creating a first rule as a required step rather than an optional one.