Review & publication
Bito reviews the marketplace card and widget release separately. This prevents a reviewed listing from silently shipping unreviewed JavaScript, and prevents a code-only approval from publishing an incomplete store card.
Release decision
Once a moderator takes a release into testing, they walk it through three stages in order — Code check, Listing check, Usability test. Approval is possible only after all three pass; rejection is possible at any stage. The stages, the static code scan's blocking rules and the decision log are described in Submit for review.
| Decision | Result |
|---|---|
| Approve | The exact version becomes moderator-approved, is extracted to the production asset origin and may become the app's current runnable version |
| Reject | The release becomes rejected with a reason; fix the same release and resubmit |
| Developer withdraws | The release becomes withdrawn and editable again |
An approved status alone is not always proof of moderation: a private app can locally activate its own release. Marketplace publication requires a moderator-reviewed approval.
Card decision
| Decision | Result |
|---|---|
| Approve | The card becomes approved; the app's catalogue type becomes public |
| Reject | The card becomes changed with the moderator's reason; its previous visibility is preserved |
| Developer withdraws | The card becomes changed and editable again |
If the app has a current widget version, card approval verifies that the release was moderator-approved. An API-only app can be published without a widget release.
When the app is public
Publication makes the app discoverable; it does not install it automatically. Each tenant still:
- opens the marketplace card;
- reviews permissions, developer, privacy and support information;
- presses Install;
- completes the install callback/OAuth flow;
- accepts consent for the exact widget release before its code mounts.
This is the Bito equivalent of the private-to-public transition in amoCRM's upload documentation, with one important difference: Bito exposes card and release approval separately.
After publication
- Card edits do not replace the live card until the changed card is approved.
- New widget code ships as a new semantic version and goes through release review.
- A newly approved release asks installed tenants for consent again.
- Rejecting an update does not automatically remove the last approved public card or already installed app.
- Test the published version from a separate tenant after release, just as amoCRM recommends checking the final published build after pressing Publish.