Model Publishing Approval

This scenario guides operators through reviewing a model publishing request and verifying the decision, publication scope, and resulting visibility.

Applicable Roles

• Platform Operator processing model reviews
• Model Provider tracking the review result

Target Outcome

• The reviewer identifies the model, provider, publication area, and version.
• Model information, protocol connectivity, billing, rate limits, and visibility are checked.
• Approval or rejection includes a clear, traceable reason.
• An approved model is visible, testable, or callable within the intended scope.

Before You Start

1. The account has Model Services model review permission.
2. Publication, billing, rate-limit, and content governance rules are clear.
3. Connectivity testing is complete and review material contains no real credentials.

Procedure

Step	Action	Manual	Completion Signal
1	Open Approvals > Model Reviews and filter pending requests	Model Reviews	The target request is pending
2	Check model, provider, source, and publication area	Model Reviews	Basic information matches the request
3	Check protocol test, modalities, tokens, billing, and rate limits	Model Reviews	Critical configuration is complete and compliant
4	Approve or reject with a specific reason	Model Reviews	Status and review comment are saved
5	Check status with the Provider Account	My Models	The provider sees the result and reason
6	Verify visibility for an approved public model	Model Marketplace	Intended users can find the model

At the start of review, use the Model Reviews list to locate the request by provider, version, scope, submission time, and status.

Completion Checklist

Purpose: These are the exit criteria for the current feature task. Use them to decide whether the result is observable and reviewable and whether you can continue to the next step in the scenario. They do not repeat the procedure; if any item fails, follow the troubleshooting section below.

Check	Pass Criteria
1	Request, version, provider, and publication scope are correct.
2	Protocol, billing, and rate-limit settings have verification evidence.
3	Status, comment, reviewer, and time are traceable.
4	A rejection tells the provider exactly what to change and retest.
5	An approved model is visible only in the intended scope.

Troubleshooting

Symptom	Check First
Request is missing	Status filter, provider, submission time, and permission
Approval cannot be submitted	Required settings, protocol test, publication area, and review permission
Approved model is not visible	Publication time, model state, publication area, and user visibility
Provider cannot act on rejection	Whether the review comment names the field, rule, and validation method