Memory contains controls about context and learning. Knowledge contains documents you can review and manage in Aptly. Keep those two ideas separate when you ask Hiro to remember something or prepare a document.
Before you begin
- Decide whether the information is a personal response preference, shared business guidance, or document content.
- Use Soul for personal response preferences.
- Review the audience before entering information in a field labeled Whole team or choosing Organization sharing for a document.
Review the Memory screen
- Open Hiro and select Identity.
- Open Memory.
- Review Learn from conversations and What Hiro remembers.
- Read the Knowledge base scope shown for your organization.
- Review Always remember. It is labeled Whole team and allows up to 2,000 characters.
Memory shows a learning switch, a remembered-information area, Knowledge scope, and a team-wide field.
The Knowledge base section describes searching every Knowledge article and including new articles automatically. Treat this as the scope described by the screen, not as a reason to change document permissions or assume a particular answer has read every article.
Include important context in the current request and do not rely on cross-chat recall when details matter.
Prepare and review a new Knowledge document
- In Chats, ask Hiro to prepare a new Knowledge document. Include a title and the text or outline you want.
- Review the returned card’s title and Knowledge base location.
- Check Private or Organization sharing before proceeding.
- Read the rendered draft.
- Choose Edit before saving to open the editable preview.
- Review any edits before selecting Save document. Choose Cancel if you do not want to continue.
- After saving, open the destination document to confirm its content, location, and sharing. If the outcome is unclear, check for the document before submitting the same request again.
A two-frame screenshot walkthrough shows a new Knowledge draft and Edit before saving.
What to expect
The new-document workflow provides a review card and an editable preview. Memory provides a separate settings screen. A document draft, a stored chat, and a learned preference are different kinds of state; one does not prove that the others exist.
Important limits
- Confirm a saved document by reopening it in the destination. An editable preview is not proof of a successful save.
- This article covers a new document. Existing-document changes, diff review, and moves or deletions require their own review.
- A chat remaining visible after reload does not establish learned memory, cross-chat recall, or any retention period.
- Do not infer Memory retention, privacy, or deletion behavior from this article. Check the applicable policy and the controls available in your account.
- Do not assume every organization has a Knowledge document picker. Follow the controls actually shown in your account.