Understand Save, Sync, Publish, and Deploy
Learn what each delivery action changes so you know when work is drafted, synchronized, published, or live on a customer channel.
Use this guide to choose the correct final action after changing an Agent, Knowledge source, catalog, or Helpdesk. The four words describe different transitions and are not interchangeable.
Humind separates preparation from customer-facing delivery. Work in the B2B workspace can change an Agent, Knowledge, catalog, Inbox, or Helpdesk without immediately changing every live surface. Understanding that separation helps you test deliberately, involve the right teammate, and avoid treating a saved draft as a completed launch.
Before you begin
Access: Use a role with write access to the area you are changing. Publication and deployment may require broader company permissions.
- Know which workspace and Agent you are editing.
- Identify the customer-facing surface that should change.
- Keep one realistic test question or product scenario ready.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Save the workspace change
Save records the current form or editor state in Humind. Treat this as the minimum checkpoint, not as proof that a public surface has changed.
- Confirm the save completes without an error.
- Reopen the setting and verify the value persisted.
Sync external source data
Use synchronization when Humind must import updated data from a connected source such as Shopify. Sync affects source data and does not replace Agent or Helpdesk publication.
- Start or review the relevant catalog synchronization.
- Wait for its final status before testing affected products.
Publish versioned content
Publish when the area creates a customer-facing version, such as a Helpdesk snapshot. A later edit remains pending until you republish a new coherent version.
- Review the complete publication candidate.
- Publish once and note the resulting version.
Deploy and verify the channel
Deploy or install the Agent on the intended website or sales channel. Then test the real domain because a correct workspace preview does not prove the embed is present and allowed.
- Open the deployed channel in a private browser window.
- Run the prepared scenario and confirm the expected source is used.
Important limits and operating notes
- A saved draft can be newer than a published Helpdesk.
- A successful catalog sync can still require indexing before products are usable.
- Publishing a Helpdesk does not install the Agent on a storefront.
- Use the action shown in the owning area instead of assuming one global publish button updates everything.
Verify the result
- The saved value survives a page reload.
- Any sync has completed rather than remaining queued or failed.
- The public version or deployment reports the expected state.
- A customer-facing test reflects the intended change and no unrelated change.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
The editor shows the change but customers do not
Check whether the owning surface needs synchronization, indexing, publication, or deployment after save. Verify each state in that order instead of repeatedly saving the same value.
A live result changed before the expected action
Confirm which setting you edited. Some runtime configuration is read directly, while versioned Helpdesk content changes only through publication. Record the exact surface and ask an administrator if ownership is unclear.