Skip to main content
Use Team setups to give employees a consistent starting point for AI work. A setup combines approved clients, required tools, authored workflow instructions, and reusable team guidance.

Create and publish

  1. Choose New setup, give it a clear name, and assign teams.
  2. Select the AI clients and tools the team should use.
  3. Add a workflow with a concrete outcome, useful instructions, supported clients, and its dependencies. Add reusable skills for conventions shared across workflows.
  4. Save the draft and preview the employee experience.
  5. Publish the reviewed version. Employees receive the published setup; later draft edits remain private until published.
Start with one useful task, such as investigating an issue or preparing a change for review. Instructions should explain how to use existing approved tools and when an employee should review the result.

Access and readiness

Publishing a setup does not grant app access, provision vendor licenses, or override Safety rules. Employees connect their accounts and request access through Passport’s existing flows. Readiness reflects available server observations, including app access and connection state. Desktop separately checks workflow files on the employee’s Mac. A successful tool connection is not proof that a workflow is installed everywhere.

Maintain a setup

Save and publish a new version when tools or instructions change. Employees review local skill updates before installation. If two admins edit the same draft, Passport rejects the stale change so one cannot silently overwrite the other. Rollback restores the previous published revision for the assigned audience. Employees can then apply that revision locally. Archiving removes the setup from assigned discovery. Existing local instructions remain until the employee removes them, while gateway access continues to follow current permissions. Managed local workflow skills support Claude Code and Codex. Other approved clients retain their existing Passport setup instructions.