AI tools are great at producing output that sounds right. But without product context, they often get the details wrong—especially when your product uses terms that overlap with everyday language, or when internal shorthand doesn’t match customer-facing terminology.

Product knowledge is where you define that context in Atono. It allows you to generate and manage structured product concepts that can be used with AI tools across your workflows.

---

Glossary

The Glossary builds a structured list of your product’s key concepts from documentation URLs you provide. It extracts high-confidence terms—such as feature names, workflows, screens, roles, and domain-specific language—and organizes them into a reusable reference.

There is one shared glossary per workspace. Rebuilding it updates the glossary for everyone in the workspace.

Each glossary entry includes:

• Name — The fully spelled-out concept name. Each name is unique.
• Description — A concise, plain-English definition written to be efficient for AI usage.
• Synonyms — Alternate names or abbreviations found in your documentation.
• Related concepts — Links to other glossary entries that are closely related.

The glossary gives AI tools consistent terminology and clearer context about how concepts in your product relate to one another.

👍

Want early access?

Product knowledge is currently in limited release. If you’d like to try it out, contact us in #support in the Atono community and we’ll get you set up.

Build the glossary

Building a new glossary replaces any existing glossary entries.

1. Open the Product knowledge page.
2. Click Build glossary.
3. Optionally, enter your Product name.
   • If your product name overlaps with a common word, adding it here helps reduce ambiguity during glossary generation.
4. Paste one more more Documentation URLs.
   • We suggest help documentation, API references, or knowledge bases.
   • You can add multiple URLs if your documentation spans sections.

📘

Atono crawls your documentation starting from the URLs you provide. For best results, enter a section-level URL (parent path), not a single article page.

For example:

• https://docs.example.com/docs/welcome-to-product may crawl only that page.
• https://docs.example.com/docs is more likely to crawl that section and the pages beneath it.

Recommendation: Use the highest-level URL that represents the section you want included in your glossary.

5. Click Build glossary to begin processing.

Building the glossary may take several minutes. Atono shows progress while the glossary is building.

You can navigate away while the build is running. When the build completes (or fails), Atono displays a toast message with the result.

View sources and status

The Sources tab shows which documentation was used to generate your glossary, when the crawl started, and whether each source was successfully retrieved.

1. Open the Product knowledge page.
2. Click the Sources tab.
3. Review the list of source URLs.
4. Click a source row to expand it and view the URLs that were crawled.

Each source displays:

• Source — The URL you entered.
• Status — Whether the crawl succeeded or failed, and how many URLs were crawled.
• Created — When the glossary build started.

If a source fails, it shows a Failed status. Glossary generation can still succeed as long as most sources are retrieved successfully.

Export the glossary

When glossary entries exist, an Export option is available.

Exports are in TSV (tab-separated values) format and include a header row with the following columns:

• Name
• Description
• Synonyms
• Related concepts

You can use this export as structured context in AI workflows such as story drafting, documentation generation, or code planning.

Use the glossary with AI tools

Use the glossary as shared context when working with AI assistants.

For example:

• Provide the exported glossary to an AI tool before refining stories or drafting documentation.
• Use it when generating acceptance criteria or reviewing edge cases.
• Include it in prompts for AI coding assistants so terminology and feature relationships are interpreted correctly.

Giving AI a structured glossary reduces ambiguity and helps keep terminology consistent across stories, documentation, and code.

Delete the glossary

Deleting the glossary permanently removes all glossary concepts from your workspace. Delete it when you want to rebuild from updated documentation or different sources.

1. Open the Product knowledge page.
2. Click the Sources tab.
3. Click Delete glossary.
4. In the Delete glossary dialog, confirm deletion or click X to cancel.

After deleting the glossary, click Build glossary to generate a new one.

When to rebuild the glossary

The glossary reflects the documentation it was generated from. If your product or docs change, rebuilding helps keep AI output aligned with your current terminology.

Rebuild the glossary when:

• Major features are added or renamed.
• Core workflows change.
• Terminology shifts between internal and customer-facing language.
• Help documentation is significantly updated.

Keeping the glossary aligned with your documentation helps ensure AI output stays aligned with your product.