A city clerk built an agent and wants it available to all staff. What must happen first?

A city clerk who wants an agent available to all staff must follow the municipal agent approval process before releasing the agent to all staff. Approval is the governance gate between a built agent and broad internal availability. Completing approval first protects the city from unreviewed agents that may mishandle data, misstate policy, or speak with an unofficial voice across every department.

Sharing the agent with a pilot department team for early review before full release fails by concept: a pilot is still a release to staff before the governance gate, and early review is not a substitute for the municipal approval process. Publishing the agent to the municipal app catalog for broad staff discovery and use fails as the first step: app catalog publication is a post-approval release action, not the approval gate itself, and it cannot substitute for the municipal approval process. Assigning agent access permissions to all staff through the municipal admin center fails as a substitute for governance: granting access enables use but does not constitute the municipal approval process or authorize release.

Exam caveat: AB-900 Domain 3 includes the agent approval process before wide release. Remember the sequence: build and configure, approve, then release to the intended audience. App catalog publication is not an approval substitute.

Operational check: Submit the clerk’s agent through the city’s defined approval workflow, attach evidence of grounding sources and access settings, remediate any reviewer findings, obtain recorded approval, then release to all staff and communicate support channels—retaining the approval record for audit.