Package an agent for another team

A package lets another team inspect and accept one fixed agent version. Receiving a package does not give the agent access to the other team's files.

Before you package

Confirm:

• the agent version is fixed and tested;
• the package has the correct owner and purpose;
• no credential value is in the agent or initial files;
• the provider and required tools are clear; and
• the recipient knows the current product limits.

Create the package

1. Select the fixed agent version.
2. Select Package.
3. Add the required tools, provider policy, and protection settings.
4. Add only the initial files that the recipient needs.
5. Review the package contents.
6. Create the package.

Send and accept the package

1. Send the package through the approved route.
2. Ask the recipient to verify its owner, identity, and version.
3. The recipient reviews its tools, provider, files, and limits.
4. The recipient accepts or refuses the package.
5. After acceptance, the recipient adds it to a project and allows exact files for each run.

Payment, delivery, or possession of a package does not grant file access or permission to run.

Other deployment choices

• To publish the agent on a website, use Publish on a website.
• A managed private or attested deployment needs GaugeWright support. Check Product status before you make a commitment.

Success check

The transfer is complete when the recipient can identify the exact package, has reviewed it, and has explicitly accepted or refused it.