How to Configure Submission Review¶
Choose whether organizations must run or pass a Quality Check before submitting to your Inbox site. This setting belongs to your newsroom; submitters cannot change it.
Before You Begin¶
You must be an owner or manager of the organization that runs the Inbox site. See How to Set Up Your Inbox Site if it is not yet configured.
For AI checks, you need your own OpenAI or compatible provider account and API key. Your provider bills that account for AI usage. Inbox submissions remain free during beta.
Choose a Policy¶
- In your Inbox app, go to Settings and choose Review policy under Review.
- Choose Inbox Quality Check policy:
| Policy | Submission behavior |
|---|---|
| Off — send submissions to manual review | No AI check is offered. Submitted releases wait for a person. |
| Optional — submitters may skip the Quality Check | A current pass can proceed to distribution after final submission; skipped or unsuccessful checks go to manual review. |
| Required to run, not required to pass | The default. A current check is required while attempts remain. A current unsuccessful check, provider failure, or exhausted allowance can lead to manual review. |
| Required to pass before submitting | Only a passing result for the current saved content qualifies. Edits require another check; exhausted checks without a current pass block submission. |
These policies govern the new Inbox flow for all submission types, including Calendar Events, and supported requested revisions. Sites that have not enabled the new flow retain their existing review screens. With no configured provider, every policy falls back to manual review. A check already in progress must settle before the submitter continues.
Configure the Provider¶
| Field | What to enter |
|---|---|
| API base URL | Leave blank for OpenAI or enter your compatible endpoint. |
| Model | Leave blank for the standard model or enter your provider's model name. |
| API key | Enter your provider key. It is stored encrypted and not displayed again. |
| Review instructions | Optional local guidance. The required response format and decision rules still apply. |
Select Save submission review settings. The provider configuration is checked on save. To keep the current key, leave its field blank. To remove it, select Remove the stored API key (submissions will wait for manual review) and save. You can also choose Off to use manual review without deleting the key.
Changes to the policy or provider settings can make a draft's earlier result outdated. Submitters must review the new status; saving settings does not replenish their allowance or approve items already waiting for your team.
Explain the Allowance to Submitters¶
Each submission review round allows three accepted checks. Passing checks and provider failures count. A pass uses one, editing and checking again uses a second, and one remains. Edits, save, reload, and reopening the same draft never reset the count.
An accepted editor return or authorized receiving-outlet revision request starts one new round with three fresh checks. Old results remain in the history. Reopening the same request does not renew it again, and a voluntary correction does not grant a reset. There is no administrative counter-clearing step.
With the default required-to-run policy, submitters who exhaust their checks may finish editing and submit for manual review. With required-to-pass, a current pass remains necessary.
Review Incoming Submissions¶
Open your Inbox site's Review Queue for releases that need a person. Approval starts distribution to the saved destinations in the new beta flow; a Quality Check alone never distributes a draft. See How to Review Submissions.
Troubleshooting¶
- The Review policy page is missing: It appears in your Inbox app settings for owners and managers of the organization that runs the site. Ask an owner on your team to change your role under Team members.
- Provider validation fails: Check the key, endpoint, and model. The saved configuration is not replaced by an invalid one.
- A submitter is blocked after an edit: Check the policy and remaining allowance. A previous pass does not qualify new content.
- Checks repeatedly fail: Check your provider configuration and availability. A failed accepted check still counts; do not promise a reset from refreshing.
- Still stuck? Email support@pluckyworks.org.