Manage customer installs

Manage a customer install by checking the installed Solution, agent, version, and connections in the organization where they run.

ArchAgents does not currently provide one action that rolls out every change across all customers. Treat each customer install as its own deployed setup.

Check one customer

For the customer you are supporting:

1. Confirm the organization and installed Solution.
2. Open the installed agent and review its tools, routines, and recent work.
3. Check each required connection under the agent's installations.
4. Record the installed Solution version before making a change.

If you do not belong to the customer organization, work through the shared network or ask a customer admin to inspect organization-private settings.

Review an available update

When a publisher releases a newer Solution version, the imported Solution can show an upgrade in the Solutions catalog. Preview the change before applying it:

archagent upgrade solution <solution_id> --dry-run
archagent upgrade solution <solution_id>

The preview reports configs the upgrade would add, change, or remove. Updating the imported Solution does not automatically rewrite agents that were already created from its older templates. Review the diff and decide whether that customer should reinstall from the new template.

Check the result

After any update:

1. run the customer's agreed test task;
2. confirm required connections are still active;
3. check that customer-specific changes were not overwritten; and
4. record which version is now in use.

Use the right operating surface

• Use the Solutions catalog for imported versions and available templates.
• Use the agent page for its tools, routines, and recent work.
• Use Installations for connection state and required setup.
• Use publisher analytics only for the activity they actually report; they are not a general fleet rollout control.

Next steps

• Solutions reference
• Installations
• Activity feed