Review and publish changes

When you make changes to your chatbot, whether it's changing the content of a passage, updating a script, or changing your chatbot's settings (with some exceptions), those changes need to be reviewed before they can go live.

To ensure changes are reviewed thoroughly and efficiently, content has a review state. This keeps track of whether something is a brand new change, or something that has been vetted and is ready to go live. There are four review stages in the inGenious AI platform that changes progress through:

  • Draft: All new content and new changes start in draft. This content is still being developed, is likely to change, and should not be reviewed yet.
  • Ready to review: When you've finished developing your content, move it to ready to review. Your Publisher or Admin will review the content and either send it back to draft for further work or progress it to ready to publish. 
  • Ready to publish: Once content has been reviewed and approved, it is ready to publish. This content is waiting to be included in the next published version of your chatbot.
    Some changes, such as changes to your chatbot's experience settings or data sources, go directly to ready to publish. 
    Changes to your chatbot's experience settings must be published with the next version of your chatbot.
  • Published: This content is currently live in your chatbot.

Changes may move back and forth between draft, ready to review and ready to publish as needed. You can add comments to changes to indicate what work still needs to be done. The number of changes your chatbot has in each review state is displayed at the top of the platform.

Unversioned changes

Not all changes to your chatbot go through versions. Some changes, such as those to test pages or the platform improvement features like automated tests and insight reports, don't affect your live chatbot and so aren't included in versions. Changes you make to those features take effect immediately.

Some changes only appear in versions under certain circumstances. For example, changes to platform usages or to non-primary chatbot usages take effect immediately and don't appear in versions. You can check the usage page to see if changes will appear in versions.

Some changes are always immediate and do not appear in versions:

  • Changes to your chatbot's general settings
  • Changes to integrations.
  • Changes to data stores.
  • Deleting knowledge bases or data sources within knowledge bases.
  • Test pages
  • LLM Connectors
  • Platform usages and non-primary chatbot usages.
  • Platform improvement features such as automated tests and insight reports.
Was this article helpful?
0 out of 0 found this helpful