Deploy a Solution to a customer
Give a customer an install path, keep their setup separate, and verify the first result.
Deploy a Solution to a customer when you want them to run a packaged agent setup in their own ArchAgents organization.
Choose the install path
Use one of these paths:
- Public marketplace: send the customer the public Solution page. Public listing is curated; build and submit the Solution first.
- Existing customer organization: ask an admin in that organization to import the approved Solution and install its templates.
Do not send a private organization archive to a customer unless you intend to give them that artifact and its contents.
1. Define the customer setup
Before sending the link, write down:
- who in the customer organization will administer the install;
- which agent template they should install;
- which connections and credentials they must provide; and
- one real task that proves the setup works.
The customer supplies credentials inside their own organization. Do not put customer credentials into the Solution bundle.
2. Send the install path
Send the marketplace or invite-backed link to the customer admin. They sign in with the invited work email, review the Solution, and install it into their organization.
The exact follow-up depends on the Solution. Some installs only create the packaged resources. Some public Agent Solutions may also offer to create a shared Network. Treat that Network as optional and verify it separately.
3. Complete customer-specific setup
Have the customer finish each pending connection and add only the people who need access. Keep names and credentials specific to that customer rather than putting customer details into the shared package.
4. Verify together
Run the agreed task and confirm:
- the agent is owned by the intended customer organization;
- its connections use the intended customer accounts;
- the expected people can use it; and
- the result is visible to a human reviewer.
If the install created a shared network, also confirm its organizations, members, agents, and thread access before using it for customer work.
Optional shared Network
Network creation is best effort and is not required for the Solution install to succeed. If the install offers one, follow Work with a customer in a Network and confirm the customer owns the intended organization and Network.
Next steps
Have feedback?
Help us make this page even more useful.
Tell us what you'd like to see expanded, which examples would help, or what workflow you want covered next. Every message gets read.