# Approve a public listing

> Configure operator credentials for a self-hosted public catalog, claim pending reviews and record decisions independently of organization roles.

Source: https://skaas.io/docs/public-listing-review
Last updated: 2026-11-15

## Give the deployment an operator

Set `SKAAS_OPERATOR_CREDENTIALS` on the API host to comma-separated `operator-label:credential` pairs. Each credential needs at least 32 printable, nonspace ASCII characters. Labels use letters, digits, dots, underscores, colons or hyphens and are at most 64 characters. Secret-file loading is also supported by the API configuration. Generate credentials privately and give each operator their own credential.

Open `/operator` on the web host and enter your own operator credential. The web never substitutes a deployment credential or an organization API key. A normal owner session grants no operator power. Credentials are submitted in a password field, sent to this deployment's API and not retained in HTML, a URL or a cookie. Re-enter the credential for each action.

A deployment without operator configuration returns not found for operator routes. A missing or wrong credential, including an ordinary owner's key, is refused. Configure public listing review before expecting new public skills to appear in the catalog.

## Review and decide

**Load queue** lists reviews by state. For another page, submit the returned cursor verbatim. **Claim next item** claims the oldest available review for 15 minutes. An empty claim means no item is available; a pending row may still be claimed by another operator. The screen shows the claim holder and deadline, including expired claims.

Review the organization, repository, skill, release and reason. A row without a skill identifies a publisher or repository review. Use the row's organization ID and item ID in **Record a decision**. Choose approve, reject or escalate, with an optional note of at most 500 characters. The queue refreshes after a decision. An item already decided, a live claim held by another operator or a concurrent decision returns a conflict. Reload before trying again.

A `first_public_publish` decision atomically changes listing approval and the corpus revision. Approval permits the listing subject to the other catalog rules. A pending publisher may have an approved listing without a verified badge; a suspended publisher remains hidden. A rejection of another review kind does not take down the artifact. Takedowns and holds use their separate operator procedures. Organization administrators cannot lift an operator hold.

The screen calls the existing `GET /v1/operator/moderation`, `POST /v1/operator/moderation/claim` and `POST /v1/operator/orgs/{org_id}/moderation/{item_id}/resolve` routes with the explicit bearer credential. Queue rows and notes are not a substitute for reviewing the release and its audit.
