` links can point to synced documents. Keep spaces URL-encoded (`%20`) and preserve the file's exact case. Commit the target document as well as the page linking to it.
Honen resolves these links using the synced repository, branch, and file path. In the Knowledge Base, they open documents the viewer may read. On an academy, they open documents selected for that site's published documentation. Headings can be addressed with a `#fragment`; explicit HTML anchors are preserved too.
Local links resolve to synced pages that the reader can access. For academy cross-links, include and publish the target page, then open the link in the public academy. External web links continue to open their original destinations.
For working examples, open [Documentation file formats](https://honen-academy.honen.com/docs/6ab35ef4da8e0901468ca3c4) or [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd).
## Import HTML
Use semantic HTML: headings, paragraphs, lists, tables, code blocks, and image tags. For example:
```html
Create a course
Open Create and describe your learning goal.
```
Honen imports the document content. Scripts, page styling, and interactive website behavior do not become part of the Knowledge Base page.
## Where images are stored
For referenced repository images, Honen resolves the path, downloads the image through the connected GitHub account, and uploads it to the workspace’s Knowledge Base image storage on Google Cloud Storage (GCS). The saved document points to Honen’s image URL. Readers do not need repository access to view images that are published with an academy page.
Unchanged image bytes are reused. Replacing a screenshot triggers a refresh even when the document text stays the same. Commit supported, accessible image files alongside the documentation and review them on the synced page before publishing.
## Keep docs current
Commit changes to the connected branch. Honen checks linked sources on its sync schedule. Open the linked folder and choose **Refresh** when you need to check a change immediately. Wait for its sync status to settle, then inspect the affected document. **Open in GitHub Documentation** on a folder and **Open original** on a document take you back to the source. This is a one-way connection: edit the repository to make durable source changes.
Source updates can also inform linked course revisions. They do not approve or publish a course update automatically.
## Build training from repository documentation
1. Open **Create → Attach → Add from knowledge base**.
2. Browse the synced repository folder, select the guides for this learning outcome, and choose **Add selected**.
3. Wait for the source attachments to be ready. Explain which product workflow to teach, who will learn it, and whether to reuse the repository screenshots.
4. Answer the setup questions, review the outline, and choose **Approve & Build**.
5. Open **Review & edit**. Verify the product steps, images, and answer keys against the synced documentation, then try the course in **Preview**.
For an existing course, attach documents through **Materials → Add from knowledge base → Attach selected**. After a repository change syncs, use **Refresh from KB** on the material and revise the affected lesson. Follow [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314).
## Tips for a smooth setup
- **Repository missing:** check the GitHub App installation, selected repositories, organization approval, and the connected account’s access.
- **Folder missing:** it must contain supported documentation files. A folder containing only code or images is not a documentation folder.
- **Image missing:** check path spelling and case, commit the image, and verify the account can read it. Prefer repository-hosted assets over external authenticated URLs.
- **Document link is not clickable:** commit and sync the target, check the relative path and branch, and ensure the target is included in the academy or available to the Knowledge Base viewer.
- **Old content:** check the connected branch, refresh status, and most recent source revision. A disconnected account cannot keep syncing.
## Build training from Notion and Confluence
Source: https://honen-academy.honen.com/docs/6ab38b913b82ff9f26dee989
Use the pages your team already maintains as the foundation for onboarding and process training. Select a small, coherent collection so the course teaches one workflow with the right terminology.
## Notion: select pages and databases
1. Open **Knowledge Base** and the destination folder.
2. From the add menu, choose **Add an integration**. In **Content sources**, choose **Connect** for **Notion**.
3. Complete Notion's authorization and select the pages the connection may access. Return to Honen when authorization finishes.
4. Open the destination folder's add menu and choose **Add from Notion**.
5. Browse the available pages and databases. Open a parent to inspect its children, or select its checkbox to bring in the collection. Select individual page checkboxes for a smaller import.
6. Check the selection count and choose **Add selected**.
7. Wait for processing, then inspect the imported pages, lists, tables, and images.
Notion grants access to selected pages in its own connection flow. If a page is absent, check that it is shared with the connection in Notion. The picker's **Search Notion…** filters items that have been loaded; browse the correct parent and use **Load more** where offered.
## Confluence: select a space or page tree
1. Open **Knowledge Base → Add an integration → Content sources**.
2. Find **Confluence**, choose **Connect**, and complete the Atlassian sign-in and consent for the Confluence site you intend to use.
3. Return to your destination folder and choose **Add from Confluence**.
4. Open a space to browse its pages. Open a parent page to inspect the child pages underneath it.
5. Select individual pages for a focused lesson, or select the space or parent collection to include its supported page tree.
6. Choose **Add selected** and follow the import status.
7. Open the imported result. Read the page body and inspect diagrams and images before using it for learning.
Use **Search Confluence…** to filter the loaded items and **Load more** to continue browsing. The connected account must be able to read the pages and their source attachments.
## Create the course from your wiki pages
1. Choose **Create → Attach → Add from knowledge base**.
2. Select the imported pages that belong in this course and choose **Add selected**.
3. Wait for the attachments to become ready, then state the outcome. For example: “Use these escalation pages to teach new support teammates how to recognize an urgent issue, collect the required information, and choose the correct escalation path.”
4. Tell Honen the audience and starting level. Choose the offered structure and size, or type your preferred scope.
5. Review the proposed outline. Ask to remove unrelated topics or add a practice scenario before choosing **Approve & Build**.
6. Open **Review & edit**, compare the reading with the source, check answer keys, and complete the scenario or quiz in **Preview**.
For a procedural wiki, a reading can explain the policy while a Scenario, Form, or Walkthrough checks whether learners can apply it. See [Choose the right activity and project](https://honen-academy.honen.com/docs/6ab35ee2da8e0901468ca367).
## Maintain the original and the course together
Make policy updates in Notion or Confluence, then check the linked Knowledge Base copy with **Refresh**. Imports are one-way: edits in Honen do not update the original wiki.
In the course's **Materials**, use **Refresh from KB** when the source has changed. Ask the editor assistant to revise the affected lesson, check its citations and practice answers, and review the draft before publishing. See [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314).
## Turn Document360 articles into training
Source: https://honen-academy.honen.com/docs/6ab38b943b82ff9f26dee999
Bring a maintained help center into Honen and use its product articles to teach the workflows customers or teammates need to perform.
## Connect Document360
1. Open **Knowledge Base** and choose **Add an integration** from the add menu.
2. In **Content sources**, find **Document360** and choose **Connect**.
3. Create a Document360 API v3 key under **Settings → Knowledge base portal → API keys**, then enter it in **API key**. The dialog's **Where do I find my key?** link opens the provider's setup instructions.
4. Choose **Connect** and confirm the connection is active.
This is a shared workspace connection. A workspace administrator with integration-management permission manages the key, and the Document360 account needs API v3 access. Use the key for the project whose articles belong in your training collection.
## Select articles or categories
1. Return to the Knowledge Base destination folder and choose **Add from Document360**.
2. Browse the available project/workspace collection and its categories.
3. Open a category to inspect its articles. Select individual article checkboxes for a focused course, or select a category to maintain that collection in Honen.
4. Check the selected count and choose **Add selected**.
5. Wait for processing. Open the imported documents and review headings, procedures, and screenshots.
The picker searches loaded items. Browse the relevant category and use **Load more** where available before deciding a particular article is absent.
## Build a product course
1. Open **Create → Attach → Add from knowledge base**.
2. Select the imported articles that support one product outcome, then choose **Add selected**.
3. Wait for the attachments to become ready.
4. Write a brief such as: “Teach new customers to create their first project using these getting-started articles. Preserve the product's control names and use the article screenshots where they clarify a step.”
5. Answer the setup questions and review the outline. Check that the sequence follows the real product workflow before choosing **Approve & Build**.
6. In **Review & edit**, compare every product action and screenshot with the source. Try the learner activities in **Preview**.
For an existing course, attach the articles through **Materials → Add from knowledge base → Attach selected**, then request the specific revision you want. [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd) shows the attachment flow.
## Refresh after a product change
Update the articles in Document360. Linked content refreshes on its supported schedule; Document360's scheduled refresh interval is at least six hours. Use **Refresh** on the Knowledge Base item to check sooner, then inspect the changed article.
Refresh the course material with **Refresh from KB**, update the affected lessons, and review before publishing. [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314) walks through that complete revision cycle.
## Connect Google Drive, OneDrive, and SharePoint
Source: https://honen-academy.honen.com/docs/6ab38b923b82ff9f26dee991
Bring your team's working documents into Honen, then turn selected material into training. Link a focused folder when you want its supported files to stay together as the source changes.
## Choose the connection
| Source | What to select | Useful material |
| --- | --- | --- |
| Google Drive | Individual files or a folder in Google's picker | Google Docs, Slides, Sheets, Drawings, and supported uploaded files. |
| OneDrive | Files or a folder in Honen's picker | Office documents, PDFs, images, videos, Markdown, text, and supported spreadsheets. |
| SharePoint | A site, document library, folder, or individual files | Team procedures and shared document collections. |
The connection uses the account you sign in with. The provider's consent screen describes its read access; the items you subsequently select determine what Honen imports. In Honen, choose the destination folder for the audience that should read those copies.
## Google Drive: link a document or folder
1. Open **Knowledge Base**, open the destination folder, and choose **Add an integration** from its add menu.
2. In **Content sources**, find **Google Drive** and choose **Connect**.
3. Complete Google's sign-in and consent, then return to Honen. Confirm the connection is shown as connected.
4. Return to the destination folder and choose **Add from Google Drive**.
5. In Google's picker, select the files or folder you want and confirm the selection.
6. Wait for the imported items to finish processing. Open a document and inspect its text and images.
Google Docs are read as document text. Slides retain their presentation content for extraction, Sheets are read through a PDF export, and Drawings through an image export. Review sheet print layout, slide diagrams, and drawing labels in the imported result. For a large native document that Google cannot export, download a supported copy and use [Import file](https://honen-academy.honen.com/docs/6ab36192effafe59361d23d7).
## OneDrive: link files or a folder
1. Open **Knowledge Base → Add an integration → Content sources**.
2. Find **OneDrive**, select **Connect**, and complete the Microsoft sign-in and consent.
3. Return to your destination folder and choose **Add from OneDrive**.
4. Open folders to browse. Select a file's checkbox for that file, or a folder's checkbox to include its supported descendants.
5. Check the selected count and choose **Add selected**.
6. Open the resulting Knowledge Base item when processing completes. Check that headings, tables, and images are readable.
Use **Search OneDrive…** to filter the loaded items. Open the relevant folder and use **Load more** when available to see additional results.
## SharePoint: choose the right library
1. In **Content sources**, choose **Connect** for **SharePoint** and complete Microsoft's sign-in and consent.
2. In your Knowledge Base destination folder, choose **Add from SharePoint**.
3. Browse the site, then its document library and folders. The picker breadcrumbs let you return to a parent location.
4. Select individual files for a focused lesson, a folder for a maintained collection, or the broader site/library when you intend to import that collection.
5. Review the selected count, choose **Add selected**, and wait for processing.
6. Open representative documents and check their titles, body text, images, and original-source links.
OneDrive and SharePoint read Markdown, text, and CSV as text. Supported Excel files, OpenDocument files, and RTF are converted to PDF for reading. A linked spreadsheet supplies learning material; it does not become a live editable spreadsheet inside the course.
## Turn the imported files into a course
1. Choose **Create → Attach → Add from knowledge base**.
2. Open your imported folder, select the specific documents, and choose **Add selected**. Wait for the ready attachment indicators.
3. Write a brief that names the source and the desired behavior. For example: “Use the attached onboarding procedure and training deck to teach new support teammates how to prepare and complete a welcome call.”
4. Answer the audience, starting-level, structure, and size questions that Honen asks.
5. Review the outline and choose **Approve & Build** when its topics and activities fit the source.
6. Open **Review & edit**. Check facts and source images, then try each activity in **Preview**.
For an existing course, use **Materials → Add from knowledge base → Attach selected**, then ask the editor assistant for a specific lesson update. See [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd).
## Keep the training current
Update the original document in its source system, then use **Refresh** on its linked Knowledge Base item when you want to check for the latest version. Open the updated copy and review the changed section. In the course, use **Refresh from KB** on the material, revise the affected activities, and preview them before publishing. Follow [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314).
## Turn Granola meetings into training
Source: https://honen-academy.honen.com/docs/6ab38b903b82ff9f26dee984
Capture useful explanations from a meeting and turn them into reusable onboarding or practice. Choose meeting notes for a concise summary, a transcript for the original conversation, or both when you need the summary and detail together.
## Connect Granola
1. Open **Knowledge Base → Add an integration**.
2. In **Content sources**, find **Granola** and choose **Connect**.
3. Enter the Granola API key in **API key**, then choose **Connect**.
4. Confirm that Granola is connected before returning to the Knowledge Base.
Granola uses a shared workspace connection managed by someone with integration-management permission. The source account determines which meeting folders and notes can be read.
## Select the meetings and their content
1. Open the destination folder's add menu and choose **Add from Granola**.
2. Browse a folder or use **Search Granola…** to filter the loaded meetings.
3. Under **Include**, choose **Notes**, **Transcript**, or **Both**.
4. Select meeting checkboxes for specific conversations. Select a folder checkbox when you want its meeting collection to remain linked.
5. Review the selected count and choose **Add selected**.
6. Wait for processing, then read the resulting document. Check decisions, speaker meaning, product terminology, and any action items you intend to teach.
Use **Load more** when the picker offers more meetings. A summary and a transcript serve different purposes: review the transcript when the exact explanation matters, and use the notes to identify the main themes.
## Create a course from the meeting
1. On **Create**, choose **Attach → Add from knowledge base**, select the imported meeting documents, and choose **Add selected**.
2. Wait for the ready indicators, then explain which parts should become learning material. For example: “Use this product handoff to teach new support teammates the three approved troubleshooting steps. Turn the discussion into a concise explanation and a practice scenario.”
3. Answer the setup questions about audience, level, structure, and size.
4. Review the outline. Replace meeting-specific follow-ups with reusable learning goals, then choose **Approve & Build**.
5. Open **Review & edit**. Check the facts against the meeting and approved product documentation, then try the practice activity in **Preview**.
If Granola is already connected, **Create → Attach → Add from Granola** can import selected meetings directly as course materials. Choose the content mode and **Add selected** in that picker. Use the Knowledge Base route when the meetings should also form a shared reference collection.
## Keep useful meeting knowledge current
On a linked Granola item, use the content-mode control to switch between **Notes**, **Transcript**, and **Both** when your teaching needs change. Refresh the linked item and review the new body. Folder changes are reflected as the folder syncs.
If the document is already attached to a course, use **Refresh from KB** in **Materials**, then revise and preview the affected activities. See [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314).
## Use one source for people and AI
Source: https://honen-academy.honen.com/docs/6ab3768478ce9f171827970a
Parallel Training uses the same approved organizational knowledge for human learning and AI assistance. Give people a course built from the source, and give an Agent or connected AI client scoped access to that source.
## 1. Prepare the shared source
1. Create a Knowledge Base folder for the process or product.
2. Import or write the approved documents.
3. Check titles, images, source accuracy, and folder permissions.
4. If the source lives in GitHub, connect the intended repository folder and verify a completed sync.
[Import files and links](https://honen-academy.honen.com/docs/6ab36192effafe59361d23d7) · [GitHub sync](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc)
## 2. Build the human learning path
Attach the document to a course, explain the skill learners should demonstrate, and generate the lessons and practice. Review the draft and deliver it through an assignment, academy, or LMS.
The attachment is a snapshot. Refreshing a changed source updates that material, not the authored lessons or questions. Revise and review the affected course content separately.
[Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd)
## 3. Configure AI access
Create an Agent with read access to the approved folder, or a scoped Connector for an external AI client. Give it clear instructions about which process it supports and ask it to cite its sources. Use a Skill when you need reusable instructions for executing that process.
Test an answer whose source you know. Check that citations open the intended document and that the Agent cannot read unrelated private folders. Add a delivery channel only when that audience is ready to use it.
[Create an Agent](https://honen-academy.honen.com/docs/6ab35edcda8e0901468ca33e) · [Connect an AI client](https://honen-academy.honen.com/docs/6ab360ffeffafe59361d2244) · [Rules and Skills](https://honen-academy.honen.com/docs/6ab35ee8da8e0901468ca386)
## 4. Keep the two uses aligned
After an approved source update, verify its Knowledge Base version, test a fresh AI answer, and review which course lessons need revision. Publish the reviewed course changes through the configured workflow. A recurring drift-check automation can help identify work; it does not by itself publish a new course.
Related reading: [Introducing Knowledge Bases and Parallel Training](https://honen.com/news/introducing-honen-knowledge-bases-parallel-training).
Use [Automations](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331) for a scheduled source-review task, and [Inspect Agent logs](https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a) to review the recorded result. A successful run still needs comparison with the source.
## Create your first course
Source: https://honen-academy.honen.com/docs/6ab35ee5da8e0901468ca374
Start with what people need to learn and the material they should learn from. Honen asks for missing setup details, proposes an outline, and builds the content after you approve that outline. You review the generated lessons afterward.
This walkthrough uses a fictional welcome-call playbook in **Northstar Academy · Demo**.
## 1. Add your source material
1. Open **Create** and select **Course**.
2. Open **Attach → Attach files**. Choose your playbook, slides, notes, or other source document from your computer.
3. Wait for the file chip to finish uploading and processing. A ready attachment displays a checkmark; the create arrow is disabled while files are processing.
4. If the material is already in your workspace, use **Attach → Add from knowledge base**, select the relevant documents, and confirm the attachment instead.
See [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd) for the full upload and Knowledge Base walkthrough. For a source library shared across courses, start with [Import files and links](https://honen-academy.honen.com/docs/6ab36192effafe59361d23d7). A general-topic course can start with a prompt alone; a course about your own process needs your actual process, whether attached or explained in the conversation.
## 2. Describe the learning outcome
In the prompt, explain the subject, audience, and what learners should be able to do afterward. Identify which attached material to use. You do not need to prescribe units, topic counts, or activity counts in this first message; Honen can gather those choices during setup.
For example, with the playbook attached:
> Teach new Northstar customer-success teammates how to run a helpful welcome call. Use the attached playbook. By the end, they should be able to confirm a customer's week-one goal, choose an approved guide, and agree on a clear next step.
Select the **Create course** arrow when your prompt and attachments are ready. Choose [Assessment or Atom](https://honen-academy.honen.com/docs/6ab36138effafe59361d22d9) instead when you want a focused assessment or one piece of content.
## 3. Answer the setup questions
Honen reads the available sources and asks for missing details one at a time. Depending on your brief and template, these can include:
| Setup choice | What to provide |
| --- | --- |
| Audience | Who will take the course: you, your team, or students. |
| Starting level | What learners already know about this subject. |
| Structure | The learning activities or project approach that fits the outcome. |
| Size | How many units and topics you want, using an offered size or a custom answer. |
| Project count | How many projects per unit, when you choose a custom structure with projects. |
In this demo, Honen read the playbook, offered roleplay or lessons and quizzes, then asked for the course size. We chose lessons and quizzes and typed a custom size of one unit with two topics.
Use the offered buttons or type your answer. Details already supplied can be skipped, and a workspace template may supply its own questions. Finish setup and approve the outline to begin generating the lessons.
## 4. Approve the proposed outline
1. Read the proposed title, units, topics, learning goals, activities, tests, and projects.
2. Check that the planned content supports the outcome and uses the right sources.
3. Request changes in the conversation if the plan needs work.
4. Approve the outline when it is ready.
Outline approval starts the build. Honen creates the planned lessons and activities, then brings you into the editor to review the finished content.
## 5. Review after the build
1. Follow the activity status as Honen builds your course.
2. Open **Review & edit** when the completed-course panel offers it.
3. Use **Preview** to read lessons and try activities, then **Edit** or the course assistant to make changes.
4. Check factual claims, answer keys, source references, media, and learner instructions before sharing.
Follow [Edit and review a course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c), [Edit readings and media](https://honen-academy.honen.com/docs/6ab3614eeffafe59361d231a), and [Configure course settings](https://honen-academy.honen.com/docs/6ab3613ceffafe59361d22e7). [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) is a separate workflow from approving the initial outline.
## Tips for a strong first course
Use a clear learning outcome and current source material. Wait for attachment processing before selecting the create arrow, answer the setup questions in your own words, and use the outline conversation to refine scope. During the build, follow each activity's status. Once ready, review the lessons from the learner's perspective before delivery.
## Course creation
Source: https://honen-academy.honen.com/docs/6ab35ee3da8e0901468ca36c
Start with a topic or source material. The creation assistant asks for the missing setup decisions, proposes an outline, and starts generating the content after you approve it. Reviewing the finished lessons is a separate step in the course editor.
For a screenshot walkthrough, follow [Create your first course](https://honen-academy.honen.com/docs/6ab35ee5da8e0901468ca374).
## 1. Start with what you want to teach
Open **Create**, select **Course**, and enter a topic. You do not need to specify the whole course in the first message.
For example:
> Teach new team members how to use our customer onboarding checklist.
Attach the checklist if the course should follow that document. Your source material gives the assistant the context to teach your organization's procedures. See [Attach course materials](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd).
You can also include decisions you have already made, such as the intended audience or a specific number of units. A selected [template](https://honen-academy.honen.com/docs/6ab35ee8da8e0901468ca386) can supply instructions, source folders, structure, and its own setup questions.
## 2. Answer the setup questions
The assistant asks one missing question at a time. There is no fixed number of questions: your brief, sources, selected template, and previous answers determine what remains to be decided.
For a Course, setup covers:
| Decision | What to tell the assistant |
| --- | --- |
| Topic and scope | What the course should teach and what to leave out. |
| Audience | Whether it is for you, your team, or students. |
| Experience | What the learners already know. |
| Learning structure | Whether to emphasize lessons and quizzes, projects, or another combination. |
| Course size | How many units and topics you want, or the offered size that fits. |
Click an offered answer or type your own. For a custom structure, the assistant may also ask how many projects to include per unit. When a source has a detected module structure, it can ask whether to keep that structure instead of starting with a generic size question. Available course sizes depend on your plan.
A detailed brief can answer some of these decisions in advance, helping you move into outline review with your preferences already in place.
## 3. Review and approve the proposed outline
The outline is the plan for the content that will be generated. Check the title, units, topics, learning goals, activity formats, projects, and tests.
Request changes in the conversation while it is still a proposal. For example:
> Use two units. Put the checklist steps in the first unit and a customer handoff scenario in the second.
When the revised plan is right, approve it. Honen generates the activities in the outline and prepares them for your content review.
## 4. Wait for generation
Follow the build as Honen creates your course structure and requested activities. Each activity shows its status, so you can begin exploring ready content while the rest of the course takes shape.
## 5. Review the generated course
Once content is ready, open **Review & edit** and use **Preview** to inspect the actual learner experience. Read the lessons, try the activities, and verify answers and source use. You can now ask the editor assistant for specific changes to existing content or use **Edit** directly.
[Edit and review a course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c) explains the working draft and applying changes. [Edit readings and add images](https://honen-academy.honen.com/docs/6ab3614eeffafe59361d231a) covers direct text and media editing. [Configure course settings](https://honen-academy.honen.com/docs/6ab3613ceffafe59361d22e7) covers learner and tutor options.
## 6. Prepare delivery
Publishing, catalog review, and learner access are separate from creating the course. Follow [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) after you have checked the generated content.
For a smaller deliverable, see [Choose Course, Assessment, or Atom](https://honen-academy.honen.com/docs/6ab36138effafe59361d22d9). Assessment and Atom have different setup questions and do not use the Course length and structure flow.
## Choose Course, Assessment, or Atom
Source: https://honen-academy.honen.com/docs/6ab36138effafe59361d22d9
Select a content type in **Create** before submitting your topic or materials. The choice determines what the assistant will build and which setup decisions it asks you to make.
| Type | Use it for | Setup specific to this type |
| --- | --- | --- |
| **Course** | Connected lessons and practice organized into units. | Learning structure and course size, including unit/topic counts. |
| **Assessment** | A test, a project, or both that check a defined skill. | What to assess and which kind of evidence to collect. |
| **Atom** | One focused topic or one project. | The single thing the learner should learn or do. |
All three need enough context about the subject and learner. The assistant asks for missing information rather than requiring a complete specification in your first message.
## Create a Course
1. Open **Create** and select **Course**.
2. Enter the topic and attach any sources it should follow.
3. Answer the assistant's setup questions about the audience, experience, learning structure, and size. Decisions already supplied in your brief or template need not be repeated.
4. Check the proposed outline and request changes if needed.
5. Approve the outline to start generation.
6. After the content is ready, open the editor to review the generated lessons and activities.
Follow [Create your first course](https://honen-academy.honen.com/docs/6ab35ee5da8e0901468ca374) for screenshots, or [Course creation](https://honen-academy.honen.com/docs/6ab35ee3da8e0901468ca36c) for the setup decisions in detail.
## Create an Assessment
1. Select **Assessment** below the prompt.
2. Describe the skill or knowledge to assess, such as “Check whether a new team member can use the customer onboarding checklist.”
3. Attach the source material if the assessment must follow a particular procedure.
4. Select **Create assessment**.
5. Answer any missing audience, level, and assessment-scope questions. Specify a **test**, a **project**, or **both** when asked.
6. Review and approve the proposed outline. After generation, inspect the questions, instructions, and scoring before delivering it.
Assessment setup does not ask for a course length or academic/project-based course structure. Its purpose is to check performance. A short introduction may provide instructions or necessary context without turning it into a surrounding course.
## Create an Atom
1. Select **Atom**.
2. Describe one focused concept to teach or one task to perform.
3. Select **Create atom**.
4. Answer any missing audience, level, or focus questions.
5. Review the proposal, request changes if needed, and approve it.
6. After generation, review the finished content in the editor.
An Atom contains one topic with one to three activity formats, or one project. It does not add sibling topics or a unit test, and setup does not ask for course length or structure. For example, a short reading and quiz can support one topic; a single roleplay can be a project Atom. Use **Assessment** when the deliverable is a standalone test.
## Tips for your next step
Choose a template that matches your intended content type, or clear the template to select a different type. Check the heading and selected type, add your brief, and submit to begin creation.
If the outline is broader than intended, request a narrower scope before approving. Once it has been built, follow [Edit and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c) to revise the existing content.
## Turn documents and recordings into a course
Source: https://honen-academy.honen.com/docs/6ab38b2d3b82ff9f26dee894
Start with the material that explains your work, then give Honen a clear outcome to teach. A policy document, slide deck, screenshot, recording, or dataset can each support a different kind of lesson.
## Choose the path for your source
| Source | Bring it into Honen | What to check before building |
| --- | --- | --- |
| PDF, including scans | **Create → Attach**, or **Knowledge Base → Import file…** | Extracted text, page order, tables, and diagrams. |
| Word (`.doc`, `.docx`) | Upload the document through Create or the Knowledge Base | Headings, numbered procedures, and any embedded images. |
| PowerPoint (`.ppt`, `.pptx`) | Upload the deck | Slide order and whether you want original pages or a newly written lesson. |
| Markdown (`.md`, `.markdown`) or text (`.txt`) | Import into the Knowledge Base, or attach to Create | Heading structure, lists, terminology, and referenced images. |
| HTML documentation | [Sync a GitHub documentation folder](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc) | Semantic headings, repository image paths, and links between pages. |
| PNG, JPEG, WebP, or GIF | Upload through Create or **Import file…** | Legible labels and what the image should teach. |
| MP4, WebM, or MOV | Upload the recording, or use **Record a product walkthrough or workflow** | The spoken explanation, visible steps, and start/end of the procedure. |
| Google Docs, Slides, Sheets, or Drawings | [Connect Google Drive](https://honen-academy.honen.com/docs/6ab38b923b82ff9f26dee991) and attach the imported Knowledge Base items | The document export; check spreadsheet print layout and diagram labels. |
| OneDrive/SharePoint spreadsheets or OpenDocument files | [Connect the cloud source](https://honen-academy.honen.com/docs/6ab38b923b82ff9f26dee991) | The converted reading view and the specific sheets or sections to teach. |
| Local datasets, spreadsheets, code, or ZIP archives | Attach directly as course materials and ask the assistant to inspect the relevant contents | Name the files, sheets, columns, or code paths that matter. These uploads retain the original file for inspection. |
Knowledge Base PDF, Office, image, and video imports support up to **5 GB per file**; Markdown and plain-text imports support up to **5 MB of text**. Direct course attachments have a **1 GB per-file** limit. For HTML with repository images, use GitHub sync; it resolves relative document and image paths together.
## 1. Attach and inspect the material
1. Open **Create → Attach** and select your file, or choose **Add from knowledge base** for an imported source.
2. For Knowledge Base items, check the intended document checkboxes and choose **Add selected**.
3. Wait for the ready indicator on each attachment.
4. If you imported through the Knowledge Base, open the document first and check the extracted body and images.
A direct upload keeps a copy of the file. Connected Knowledge Base sources can refresh from their original system; attaching them to a course takes a snapshot that you can later update with **Refresh from KB**.
## 2. Tell Honen how to teach from this source
Name the source, the audience, and what learners should be able to do. Add format-specific instructions where they help:
| Starting material | Example brief |
| --- | --- |
| Policy PDF or Word procedure | “Teach new support teammates when to escalate an issue. Use the attached policy's criteria and include practice choosing the next action.” |
| Slide deck | “Turn this deck into a short onboarding course. Use its original pages 2–5 for the lecture, then add a quiz about the decisions they explain.” |
| Markdown or HTML product docs | “Teach the first-project workflow from these docs. Preserve the exact control names and use the supplied screenshots beside the relevant steps.” |
| Screenshots or diagrams | “Use these annotated screenshots to explain the three setup decisions. Add captions describing what learners should notice.” |
| Training video | “Use the recording to explain the process in order. Include a reading with the key steps and a practice activity that checks the result.” |
| Screen recording | “Create an Interactive Walkthrough from this recording. Keep the visible screens and guide the learner through the clicks required to finish.” |
| Spreadsheet or dataset | “Inspect the named sheet and columns, explain how to interpret the results, and add a practical exercise using the same concepts.” |
| Code or repository material | “Use the README and the named code path to teach how this feature works, then add a Code Notebook or Full Sandbox practice task.” |
For original slides and diagrams, say whether to reuse the source pages or create new illustrations. For spreadsheets, say whether the course should explain the data or teach learners to work with it.
## 3. Complete setup and approve the outline
1. Submit the brief with the **Create course** arrow.
2. Answer the audience, starting-level, structure, size, and project questions that apply.
3. Review the proposed topics and learning goals against your source. Ask for changes before starting the build.
4. Choose **Approve & Build** when the plan fits.
Choose a [Course, Assessment, or Atom](https://honen-academy.honen.com/docs/6ab36138effafe59361d22d9) according to how much learning you need. Use [Adapt a course to your audience](https://honen-academy.honen.com/docs/6ab380f882700be81b7d02c1) for language, length, and assessment choices.
## 4. Review the result in the format learners will use
1. Open **Review & edit** after generation.
2. Read the source-based explanation and compare key facts with the original.
3. Inspect each reused image or slide at its learner size.
4. Play generated or uploaded media, review its transcript, and check source citations.
5. Answer the quiz and try the project. Check the answer key, instructions, and evaluation criteria.
6. Apply the reviewed draft, then follow [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381).
For source revisions, use [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314). Updating the source and sharing a revised course are separate steps in that workflow.
## Add documents to an existing course
Open **Materials** and upload your files. Review the staged files, then select **Start Processing**. To add a new unit from them, enable **Create unit from these materials**, choose the topic count and activities, and use **Start Processing & Generate Unit**.
To update an existing topic instead, leave that unit-creation option off, wait for the material to be ready, and ask the editor assistant for the precise change. See [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd).
## Add sources to a course
Source: https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd
Build training around the material your team already uses: documents, product recordings, videos, repositories, and shared knowledge. Combine sources with a clear brief so the authoring assistant can teach the right workflow and use your terminology.
For format-specific instructions, follow [Turn documents and recordings into a course](https://honen-academy.honen.com/docs/6ab38b2d3b82ff9f26dee894). For a connected library, start with [Google Drive, OneDrive, or SharePoint](https://honen-academy.honen.com/docs/6ab38b923b82ff9f26dee991), [Notion or Confluence](https://honen-academy.honen.com/docs/6ab38b913b82ff9f26dee989), [Document360](https://honen-academy.honen.com/docs/6ab38b943b82ff9f26dee999), or [Granola](https://honen-academy.honen.com/docs/6ab38b903b82ff9f26dee984).
The Knowledge Base example below uses the fictional **Customer onboarding checklist** from the demonstration workspace.
## 1. Choose where to add a source
For a new course, open **Create → Attach** before submitting the brief. For an existing course, open its editor and select **Materials**.
The existing-course Materials screen supports file upload, **Add a YouTube video**, **Add a GitHub repo**, and **Add from knowledge base**.
## 2. Upload a document from your computer
1. On the creation screen, open **Attach** and choose the file upload option. In an existing course, open **Materials** and use its file upload area.
2. Select the document in your computer's file picker. Common sources include PDF, DOCX, PPT/PPTX, Markdown, text, images, and video. The upload limit is 1 GB per file.
3. On Create, wait for uploading and processing to finish; a ready file chip shows a checkmark. In an existing course's **Materials**, review the staged files and choose **Start Processing**. To build a new unit, enable **Create unit from these materials**, choose the topic count and activity types, then use **Start Processing & Generate Unit**.
4. Describe how Honen should use the material: the audience, learning outcome, and which parts matter. Submit the creation prompt only when the attachments are ready.
For an existing course, wait for the material to become ready, then ask the editor assistant to use it for a particular change.
## 3. Attach a Knowledge Base document
1. Select **Add from knowledge base**.
2. Browse a folder or search the loaded items.
3. Check the document you want to use. Select the checkbox rather than merely opening the document preview.
4. Confirm the selected count at the bottom.
5. Select **Attach selected** in the existing-course Materials screen, or **Add selected** on Create, and wait for it to finish.
## 4. Check the attachment
1. Confirm that the Materials count increases.
2. Find the document card marked **From KB**.
3. Open its preview and verify the correct content was attached.
4. Ask the editor assistant to use that document for the specific lesson or revision you want to build.
The picker creates a **snapshot** connected to the Knowledge Base source. When that source changes, refresh the material and review the affected lessons using [Build and maintain source-backed learning](https://honen-academy.honen.com/docs/6ab3811d82700be81b7d0314).
## Add a YouTube video
Turn a public video’s transcript into source material for a lesson, course, or assessment.
1. On **Create**, open **Attach → Add YouTube video**. In an existing course, open **Materials → Add a YouTube video**.
2. Paste the public video link into **Video URL**.
3. Select **Add video**.
4. Wait for the video material to finish processing. On Create, its attachment chip shows a checkmark when ready.
5. Describe the audience and what learners should take away from the video, then submit the brief. For an existing course, ask the editor assistant to use the video for the lesson you want to change.
## Record a product walkthrough
Capture the steps your learners need to perform, then use that recording as source material for a lesson or interactive walkthrough.
1. On **Create**, open **Attach → Record a product walkthrough or workflow**.
2. Select **Record your screen**.
3. In your browser’s chooser, select the tab, window, or screen to record and select **Share**. Allow microphone access if you want to narrate the steps.
4. Perform the workflow in order. Explain the goal, the choices you make, and how to recognize the finished result.
5. Return to the recorder and select **Stop**.
6. Play the preview. Select **Use recording** to keep it, or **Re-record** to start again.
7. Wait for the recording to upload and finish processing. Add a brief explaining whether you want a lesson, a demonstration, or an interactive walkthrough, and submit it.
The saved recording appears as a course material. For an interactive walkthrough, continue with [Create and edit projects](https://honen-academy.honen.com/docs/6ab3766c78ce9f1718279677).
## Add a public GitHub repository
Use a repository’s code and documentation as reference material for technical onboarding or product training.
1. On **Create**, choose **Attach → Add GitHub repository**. In **Materials**, choose **Add a GitHub repo**.
2. Paste a public repository link, such as `https://github.com/owner/repository`, into **Repository URL**.
3. Select **Add repository** and wait for processing to finish.
4. Describe the parts of the repository learners need to understand and the task they should be able to perform.
For ongoing updates from a private or public repository, use [GitHub sync in the Knowledge Base](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc), then attach the relevant documents to your course.
## Use a connected external tool
Give the assistant access to tools you already use so it can find the relevant information while helping create your course.
1. On **Create**, open **Attach → Connect to external sources (MCP)**. If you already have connections, open **Connections → Manage connections** or **Add connection**.
2. Find your provider and select **Connect**. Providers that need assisted setup show **Contact sales**.
3. Complete the provider’s sign-in and authorization window, then return to Honen.
4. Check that the connection is marked **Connected**. Under **Attach → Connections**, turn on the connection you want the assistant to use.
5. In your brief, name the connected source and the information you want used, such as a particular project, document, or customer workflow.
Connected tools become available to the assistant. You can manage them from the same **Connections** menu. See [Integrations and MCP](https://honen-academy.honen.com/docs/6ab35ededa8e0901468ca347) for connection settings and custom servers.
If Granola is connected as a content source, **Attach → Add from Granola** opens a meeting picker. Select the meetings, choose whether to include notes, transcripts, or both, and select **Add selected** to import them as course materials.
## Set the course’s visual brand
Use **Brand** to give newly generated course images a consistent style, palette, and logo reference.
1. On **Create**, open **Attach → Brand**.
2. Choose a **Style**: **Editorial Doodle**, **Professional**, **Playful**, or **Custom**. If a workspace preset is offered, select **Apply** to use it.
3. Optionally enter a **Name** and select **Add logo**, or drag in a PNG, JPEG, or WebP image under 2 MB.
4. Set the **Primary**, **Accent**, **Canvas**, and **Ink** colors you want to customize.
5. Add **Guidelines** for the visual style. Custom guidelines replace the default style; guidelines for the other presets build on that style.
6. Select **Save**, then continue writing your course brief. The logo uploads when you save.
When the workspace enforces its brand, Honen uses that shared brand and hides the per-course **Brand** choice. You can also manage an existing course’s brand in [Course settings](https://honen-academy.honen.com/docs/6ab3613ceffafe59361d22e7); updated branding applies to future image generation.
For a course that teaches your brand itself, attach the brand guide as source material and describe the behaviors or standards learners should practice.
## Get your materials ready
Choose the workspace and folder containing your source, select the document checkbox, and use **Attach selected** or **Add selected** to confirm. For YouTube, enter the complete video URL to enable **Add video**.
Screen recording appears in browsers that support screen capture. For external connections, allow the provider’s sign-in pop-up and use **Reconnect** if the connection needs attention.
After adding new material to an existing course, ask the editor assistant for the changes you want and review the updated lessons.
## Continue with your sources
- [Create your first course](https://honen-academy.honen.com/docs/6ab35ee5da8e0901468ca374): brief, setup questions, outline approval, and post-build review.
- [Organize and use source material](https://honen-academy.honen.com/docs/6ab35ef9da8e0901468ca3d9): prepare the shared workspace library.
- [Import files and links](https://honen-academy.honen.com/docs/6ab36192effafe59361d23d7): add reusable source documents to that library.
- [Sync documentation from GitHub](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc): keep a repository folder synced to the Knowledge Base.
- [Edit and review a course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c): inspect and revise content after adding a source.
## Edit and review a course
Source: https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c
Make a focused change to a draft, verify it in Preview, then apply the revision. You need course editing access.
## 1. Open the course editor
1. Open **Organization → Courses and content**.
2. Find the course and select **Edit**.
3. If the completion screen appears, choose **Review & edit**.
4. Check the course title in the top breadcrumb before editing.
## 2. Inspect the learner preview
1. Select **Preview**.
2. Open the topic you want to change.
3. Try its reading, flashcards, or quiz using the format buttons.
4. Collapse the **Course Editor Assistant** if you need more room.
## 3. Edit a topic directly
1. Select **Edit**.
2. Expand a unit in the left course tree and select a topic.
3. Update **Topic title**, **Description**, or **Learning objectives** as needed.
4. Use **Generation instructions** for directions about generated content; changing these instructions alone is not a substitute for checking the resulting activity.
5. Wait for the save indicator. The button may show **Save & Apply** while a change is still unsaved.
A concise topic description helps authors and learners understand its purpose.
For an AI-assisted edit, open **Course Editor Assistant** and specify the exact topic and change: “Shorten the first reading's introduction and keep the five planning steps.” Review its result before applying.
## 4. Apply and verify
1. Return to **Preview** and check the changed content.
2. Select **Apply Changes** (or **Save & Apply** if shown).
3. Wait until **Applying…** finishes. Do not navigate away during the operation.
4. Confirm that **Draft changes** clears and the apply button becomes unavailable when there is nothing left to apply.
5. Open **Version History** to see the saved revision. Use **Preview** on a version to inspect it before considering **Rollback**.
The latest **Working draft** entry lets you inspect the applied revision. Follow [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) when releasing it to a catalog.
## Activity and Project Types
Source: https://honen-academy.honen.com/docs/6ab35ee2da8e0901468ca367
A course is built from activities and projects. Activities teach and check understanding; projects ask for work. Authoring one topic can produce several activity types, and the course and assignment settings determine which work is required.
A **course** contains **units**. A unit contains **topics**, and each topic contains its **activities**. **Projects** belong to the unit, where learners can bring several topics together in a practical task.
## The nine activity types
| Type | What the learner gets |
| --- | --- |
| **Reading** | An article with images, code, mathematics and callouts. Scroll progress on the edge, read time and word count. Can contain interactive widgets and embedded walkthroughs inline. Resumes where they left off. |
| **Flashcards** | Flip cards with optional hints, keyboard navigation, shuffle, and a definition-first mode. |
| **Quiz** | Multiple choice, true/false, short answer, fill in the blank and free response. The quiz can ask for confidence before revealing feedback. |
| **Visual lecture** | A swipeable card stack of illustrated slides with speaker notes. |
| **Podcast** | A two-speaker audio episode with a synced transcript that highlights along with the audio. |
| **Explainer video** | A generated or uploaded video with a transcript panel and optional captions. |
| **Comic** | An illustrated story organized into pages and panels. |
| **Jam** | Songs organized around learning goals, across genres, with lyrics alongside the audio. |
| **Arcade** | A game using the topic's own questions, with City Run combining lane choices and obstacle avoidance. |
The AI tutor supports learners alongside these formats. See [the learner experience](https://honen-academy.honen.com/docs/6ab35efbda8e0901468ca3e5).
## Project formats
Projects are where a unit stops testing recall and asks for work.
| Project | The learner |
| --- | --- |
| **Scenario** | Role-plays with AI characters, in text or voice, scored against criteria. |
| **Agent** | Works alongside a live AI agent: image generation, HTML, writing and research, spreadsheets, or a full-stack application deployed to its own live subdomain. |
| **Prompt challenge** | Writes prompts to reproduce a target image or website, scored on similarity. |
| **Code notebook** | Works through Jupyter-style cells in Python, C++ or CUDA, graded by hidden tests plus a rubric. |
| **Full sandbox** | Gets a real file tree, terminal and live preview in a browser IDE. |
| **Screen share** | Shares their screen and is coached through a real tool, step by step. |
| **Tagalong** | Scans a QR code and uses their phone camera for physical, hands-on skills. |
| **Walkthrough** | Clicks through hotspots on annotated screenshots taken from a screen recording. |
| **Form** | Fills a generated worksheet, graded against a rubric. |
Choose among these nine project types in the course editor. Start an Interactive Walkthrough from a screen recording so Honen can build its guided steps. Prebuilt simulations may also be available in your catalog.
In practice this means learners build spreadsheets, generate images, write research, write code, build web pages, role-play customer conversations, apply electrical code to a wiring problem, walk through a safety procedure with a coach watching their screen, or hold a phone over real equipment.
## Choose the format for the learning goal
| Goal | Useful formats |
| --- | --- |
| Explain a new idea | Read for depth, Lecture or Video for visual explanation, and Podcast for an audio conversation. |
| Reinforce a memorable concept | Comic for a visual story or Jam for learning through music. |
| Practice recall | Flashcards for terms, Quiz for answers and feedback, and Arcade for repeated practice. |
| Apply skills | Scenario for conversations; Agent and Prompt Challenge for working with AI; Screen Share, Code Notebook, and Full Sandbox for practical work with tools. |
| Follow a procedure | Interactive Walkthrough for a recorded workflow, or Tagalong for physical practice through a phone camera. |
## Create, edit, and try each format
Start by attaching your source and naming the topic, activity, and learning goal in the **Course Editor Assistant**. In a new course, select the formats during setup and check them in the outline before **Approve & Build**. After generation, open **Edit**, select the activity, and alternate between **Editor** and **Learner View**.
| Format | Authoring and learner workflow |
| --- | --- |
| Reading | [Edit text, insert images, and preview the reading](https://honen-academy.honen.com/docs/6ab3614eeffafe59361d231a); [read and navigate as a learner](https://honen-academy.honen.com/docs/6ab361aaeffafe59361d243e). |
| Flashcards | [Create the deck, edit terms and hints, and test card flips](https://honen-academy.honen.com/docs/6ab38b273b82ff9f26dee885#edit-the-flashcards). |
| Quiz | [Edit questions, correct answers, and explanations, then complete the quiz](https://honen-academy.honen.com/docs/6ab38b273b82ff9f26dee885#edit-the-quiz-and-its-answer-key). |
| Lecture | [Edit slide text and illustrations, then check slide navigation](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#lecture-edit-slides-and-illustrations). |
| Podcast | [Edit speaker turns, rebuild audio, and follow the transcript](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#podcast-edit-the-conversation-and-rebuild-audio). |
| Video | [Create a generated, uploaded, or hosted video and check playback](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#video-choose-generated-uploaded-or-hosted-content). |
| Comic | [Edit panel descriptions and dialogue, then read the story](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#comic-edit-the-story-and-panel-artwork). |
| Jam | [Edit song lyrics and order, regenerate, and listen](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#jam-edit-song-titles-lyrics-and-order). |
| Arcade | [Edit game questions and play the activity](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#arcade-edit-the-questions-behind-the-game). |
| AI tutor | [Ask a question, use voice, and get help alongside the lesson](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432). |
| Projects | [Configure and try the nine practical project formats](https://honen-academy.honen.com/docs/6ab3766c78ce9f1718279677); [build a Form worksheet](https://honen-academy.honen.com/docs/6ab3766e78ce9f1718279689). |
Use [Turn documents and recordings into a course](https://honen-academy.honen.com/docs/6ab38b2d3b82ff9f26dee894) to choose the source and write a brief for the format you want.
## Tests
Unit tests run in their own view with multiple choice, true/false, short answer and interactive artifact questions, with question navigation and confidence tracking. For a required test, the pass threshold is the higher of the test's own passing score and the assignment's minimum when both are set. If neither specifies a score, the default is 80%. An optional test does not gate completion; its result is informational.
See [Unit tests and remaining work](https://honen-academy.honen.com/docs/6ab361a1effafe59361d2418) and [Assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) for the learner flow and required-work settings.
## Edit readings and add images
Source: https://honen-academy.honen.com/docs/6ab3614eeffafe59361d231a
Open a generated reading in the direct editor to refine wording, formatting, and media. The screenshots show the fictional Northstar onboarding course.
## 1. Open the reading
1. In the course editor, select **Edit**.
2. Expand the unit and topic in the left course tree.
3. Select **Read** below the topic.
4. Stay on the **Editor** tab to edit; use **Learner View** to check the presentation.
## 2. Refine the content
1. Place the cursor in the reading and edit the relevant passage.
2. Select text before applying heading levels, bold, italics, lists, or links from the toolbar.
3. Use **Undo** when correcting a recent editing mistake.
4. Check the preview after changing structure, tables, or media.
The toolbar also provides **Insert Video**, **Insert embed**, and **Insert Table**. Choose the content type that fits the explanation, then follow its dialog.
## 3. Add an image
1. Position the cursor where the image belongs.
2. Select **Insert Image** in the toolbar.
3. Choose **Upload** for a local image or **From URL** for an image link.
4. Follow the dialog and wait for the image to appear in the reading.
5. Verify the image and surrounding text in **Learner View** before applying the course changes.
The upload dialog accepts PNG, JPEG, WebP, or GIF up to 10 MB. Use screenshots that show the relevant task without unrelated account information.
## 4. Adjust an existing generated image
An existing image exposes separate actions: **Edit** lets you request changes to the existing image, **Redo** requests a new generated image, and **Replace** lets you upload your own file. Inspect the result before keeping it. **Edit image caption** changes its caption. Use the caption to explain what learners should notice in the image.
After an edit, wait for the saved state, verify it in Preview, and use **Apply Changes** when ready. See [Edit and review a course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c).
## Preview and apply
Open **Learner View** to review the reading’s text, images, tables, and embeds together. When the lesson is ready, use **Apply Changes** and follow [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) to share the update.
## Create and edit flashcards and quizzes
Source: https://honen-academy.honen.com/docs/6ab38b273b82ff9f26dee885
Turn your source material into practice that helps learners remember terms and make the right decisions. Flashcards work well for focused recall; quizzes can check how a learner applies an idea in context.
## Add practice to a topic
1. Attach the source through **Materials** or choose it while creating the course. Wait for processing to finish.
2. In **Course Editor Assistant**, name the topic, the source, and the practice you want. For example: “Add three flashcards and a three-question quiz to Prepare a helpful welcome call. Use the attached checklist and test the customer's goal, approved sources, and definition of done.”
3. For a new course, request these formats during setup and check them in the outline before **Approve & Build**.
4. Wait for generation. Open **Edit**, expand the unit and topic, and select **Flashcards** or **Quiz**.
5. Use **Editor** for changes and **Learner View** to try the activity.
A topic has one activity of each format. Add cards or questions inside that activity; use another topic when you want a separate practice set.
## Edit the flashcards
1. Edit each **Term** and **Definition**. Keep one idea per card.
2. Use the hint control to add an optional hint. Write a cue that helps recall without simply repeating the answer.
3. Choose **Add Card** for another term and definition. Use the row's remove control for a card you no longer need, or drag its handle to change the order.
4. Where media controls are available, use **Generate** or **Upload** to add an image that supports the concept. Preview the image with the card.
5. Open **Learner View**, flip each card, and check the term, definition, and hint together.
Try the learner settings, including shuffle and definition-first study, when they fit your deck. The [flashcard learner guide](https://honen-academy.honen.com/docs/6ab361adeffafe59361d2450) shows the study controls and keyboard flow.
## Edit the quiz and its answer key
1. Select **Quiz → Editor**.
2. Edit **Enter the question…** so the prompt describes one clear decision.
3. Edit the answer options. Select the circular control beside the correct option; the chosen answer is highlighted.
4. Use **Add Option** when another choice is useful. The multiple-choice editor keeps between two and six options.
5. Fill in **Explain why this is the correct answer…** with the reasoning learners should take away.
6. Choose **Add Question** for another question. Reorder or remove rows as needed.
7. Where available, use **Generate** or **Upload** to add question media, then inspect it alongside the prompt and answers.
These controls edit the multiple-choice questions shown in this walkthrough. For a different question format or a broader rewrite, describe the change to the Course Editor Assistant and review the resulting question in the learner view.
## Try the complete quiz
1. Open **Learner View** and start the quiz.
2. Answer a question. When confidence is requested, choose the confidence level before continuing.
3. Read the answer feedback and explanation. Check that the selected correct option matches your source.
4. Complete the remaining questions and inspect the result.
5. Return to **Editor** to improve any ambiguous wording or weak explanation.
Follow [Take a quiz](https://honen-academy.honen.com/docs/6ab3619beffafe59361d23fe) for the learner's complete answer-and-feedback workflow. Use a [unit test](https://honen-academy.honen.com/docs/6ab361a1effafe59361d2418) when you need a separate unit-level assessment with required-work settings.
## Apply the reviewed practice
Wait for edits to save, then use the course's **Apply Changes** or **Save & Apply** control as shown. Open the course-wide **Preview** and verify that the practice follows the right lesson. Follow [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) when the revised course is ready to share.
For readings that introduce the same concepts, see [Edit readings and add images](https://honen-academy.honen.com/docs/6ab3614eeffafe59361d231a). For games using a question set, follow [Arcade authoring](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665#arcade-edit-the-questions-behind-the-game).
## Create and edit media activities
Source: https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665
Turn the same learning goal into illustrated slides, an audio conversation, an explainer video, a comic, music, or a game. Each format has a focused editor so you can refine the content and preview the experience learners will use.
## Add a format and open its editor
1. For a new course, tell the creation assistant which formats you want when it asks about the learning structure. Check that they appear in the outline before approving the build. See [Course creation](https://honen-academy.honen.com/docs/6ab35ee3da8e0901468ca36c).
2. For an existing course, open **Course Editor Assistant** and name the topic, format, source, and desired result. For example: “Add a lecture to the Welcome call topic using the attached checklist. Teach the three preparation steps.”
3. Make sure the topic has learning objectives. Lecture, Podcast, Comic, and Jam generation need goals to work from.
4. Wait for generation to complete, then open the activity to review its content and media.
5. Open **Edit**, expand the topic in the course tree, and select its activity.
6. Use **Editor** to change content and **Learner View** to inspect that activity. The course-wide **Preview** lets you check it in context.
Use a source-specific request to make the first draft useful:
| Format | Example request to the assistant |
| --- | --- |
| Lecture | “Use the attached procedure to make a visual lecture explaining the three preparation steps.” |
| Podcast | “Create a two-speaker conversation explaining the approved welcome-call process, using this checklist.” |
| Video | “Create a narrated explainer of the workflow, using these product screenshots in order.” |
| Comic | “Show a new teammate following the procedure in a short comic; keep the dialogue consistent with the checklist.” |
| Jam | “Create a song that reinforces the topic's learning goal and the three approved preparation steps.” |
| Arcade | “Add a game question set that tests the decisions in this topic, with explanations grounded in the source.” |
A topic supports one activity of each format. To give learners two separate lectures in a sequence, use separate topics.
## Lecture: edit slides and illustrations
1. Open the topic's **Lecture** activity and stay on **Editor**.
2. Select a slide in the image carousel using its thumbnails or previous/next controls.
3. Below the carousel, find the matching slide number and edit its **Title**, **Bullet Points**, **Speaker Notes**, and **Illustration Description**. Enter one bullet point per line.
4. To change the slide image, enter a focused request in **Describe changes to this slide…** and submit it.
5. Inspect the generated image preview. Choose **Accept** to keep it or **Reject** to retain the previous image.
6. Open **Learner View**. Use **Previous slide**, **Next slide**, or a numbered slide control to check the sequence and readability.
Use the text fields to refine slide content. To update wording or artwork inside the illustrated image, describe the visual change and review its generated preview.
 
### Use original document pages as slides
Attach the PDF or deck through [course materials](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd), then explicitly ask the assistant to use its actual pages as the lecture. Name the document and page range. For example: “Use pages 2–5 of the attached welcome-call deck as this lecture; preserve their order.”
If you want only the extracted diagrams or figures, say that instead. Reusing original pages and generating new illustrated slides produce different results. When splitting a source across lectures, give each lecture its own page range.
## Podcast: edit the conversation and rebuild audio
1. Open **Podcast → Editor**.
2. Edit the **Episode title**.
3. For each script segment, select its speaker and edit what they say.
4. Use **Add Segment**, or the plus control between segments, to add a turn. Use a segment's trash control to remove it; the editor keeps at least one segment.
5. Wait for your changes to save. Select **Regenerate Audio** when you want a new generated result.
6. Wait for generation to finish, then open **Learner View**. Play the episode and compare it with the **Transcript**. Use the playback position and 15-second skip controls to check the changed passage.
After editing the conversation, use **Regenerate Audio** to create the updated episode. Review the full episode and transcript together.
 
## Video: choose generated, uploaded, or hosted content
Be explicit about the source when requesting a Video activity:
| What you want | What to provide |
| --- | --- |
| A generated explainer | Ask the assistant to create a narrated video about the topic. |
| Your existing video file | Upload the file to chat or **Materials**, then ask the assistant to use that uploaded video in the activity. |
| A video on your existing host | Supply a supported Vimeo or Brightcove link and ask to use it as a hosted video. |
Use an uploaded file to bring an existing recording into the course. For hosted video, enable embedding on your learning-site domain in the host’s settings.
### Edit a generated video
1. Open the **Video** activity under the topic. Its learner-facing format can appear as **Explainer**.
2. If the editor shows one **Step** at a time, use **Previous step** and **Next step** to choose the relevant section.
3. Change **Spoken narration**, **Voice**, or **Artwork change**. A separate **Caption** field appears for the caption style that supports it; word-by-word captions follow narration.
4. Select **Apply changes** in the step editor and wait for **Changes applied**. Narration, voice, and artwork changes regenerate that step. **Discard** abandons unapplied changes in those fields.
5. If the editor instead shows a **Scenes** list, edit the relevant scene fields and select **Rebuild video**. The current video remains playable while the edited version is rebuilt.
6. Open **Learner View** and watch the affected section. Check the narration, artwork, captions, and **Show transcript** panel where available.
Use the step or scene editor for a focused change, or **Regenerate** for a broader rebuild. Where **Render options** are available, choose **Aspect ratio**, **Captions**, and **Voice** before regenerating.
 
### Add real screenshots to a generated explainer
Where the video editor provides **Screenshots**:
1. Select **Add**.
2. Choose **Upload**, **Course images**, or **Walkthrough frames**. Add up to three images.
3. Give each screenshot an accurate name and description. Reorder them if needed.
4. Select **Regenerate** to build a video with your selected screenshots.
5. Watch the new result and check that it uses the intended screens.
### Edit an uploaded or hosted video
1. Open the activity's **Editor** and correct its title.
2. For an uploaded video, edit **Notes** and **Transcript** as needed. Use these fields for the accompanying text. To replace the recording, attach the new file and ask the assistant to use it for this activity.
3. For hosted content, use **Hosted video URL or iframe code** and enter the supported link or embed. **Use hosted video** switches an existing video entry to that source type; only choose it when you intend to replace the current source.
4. Save and check **Learner View**. For hosted video, confirm playback works for the intended audience, including any host-side access restrictions.
Use **Regenerate** for generated videos. For hosted content, supply a transcript alongside the player when you want learners to follow the video in text.
## Comic: edit the story and panel artwork
1. Open **Comic → Editor**.
2. Select the panel you want to inspect in the image carousel.
3. Edit its **Scene Description**, **Alt Text**, and **Dialogue**. Use **Add line** for another speaker's line and fill in the speaker and text.
4. To change the actual image, use **Describe changes to this panel…**. Inspect the preview and choose **Accept** or **Reject**.
5. Open **Learner View**. Check every panel, including dialogue rendered in the artwork.
6. Choose **Flat view** for a straightforward reader or **3D view** for an interactive presentation. **Switch to flat view** opens the flat reader from the 3D screen.
Use dialogue fields to refine the accompanying text, and request an image change to update illustrated speech bubbles. In flat view, use **Previous panel** and **Next panel**; the 3D reader provides page-selection, zoom, and rotation controls.
 
Use **Next panel** to continue. The page indicator and dialogue update with the selected panel.
## Jam: edit song titles, lyrics, and order
1. Open the topic's **Jam** activity. It may be labeled **Jam session** in creation controls.
2. In **Editor**, expand a song row to inspect its title and lyrics. The genre badge and associated learning goal help identify the track.
3. Edit the song title or lyrics. Drag song rows to change their order.
4. Wait for changes to save, then use **Regenerate** to create audio from the updated lyrics. You can also describe the music change to the Course Editor Assistant.
5. Open **Learner View** or the course **Preview**, choose **Jam session**, select a song, and use the playback controls. Compare the sung words and displayed lyrics, especially after a change.
A generated Jam organizes songs around the topic's learning goals. Review the result for factual accuracy as well as musical presentation.
 
## Arcade: edit the questions behind the game
1. Open **Game** or **Arcade** under the topic in **Edit**.
2. Inspect each question, its options, the selected correct answer, and explanation.
3. Use **Add Game Question** to add another question and **Add Option** for an additional choice. Keep the question and choices short enough to read during play.
4. Save your changes and open **Learner View** on a desktop or laptop.
5. Wait for the game to load, then select **Start game**. In **City Run**, select **Run!** to begin.
6. In City Run, use the left and right arrow keys to move into the lane for your answer while avoiding obstacles. Use the game's mute, restart, and full-screen controls as needed.
Arcade brings your question set into interactive games. Keep prompts and answer choices concise, and have learners open the game on a desktop or laptop.
 
## Save and share the updated course
Text edits are saved to the course draft. Use **Apply changes**, **Accept**, or **Rebuild video** within the media editor to finish the corresponding update, then preview the result.
When the course draft is ready, use the course-level **Apply Changes** or **Save & Apply** as shown. Wait for it to finish. Then follow [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) if the updated course should reach learners. See [Edit and review a course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c) for draft and revision handling.
Play the updated media in **Learner View** to check the pacing, clarity, and fit with the lesson before sharing the course.
## Create and edit projects
Source: https://honen-academy.honen.com/docs/6ab3766c78ce9f1718279677
Projects give learners a task to perform: a conversation, a guided procedure, an AI-assisted artifact, a programming exercise, or a clickable walkthrough. Choose a format that matches the work and the equipment learners will use.
The examples use fictional content in Northstar Academy · Demo. Start with [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd) when your project should follow an existing procedure.
## Open a project in the course editor
1. Open the course's manage screen and select **Edit**.
2. Select a project in the course outline. If you need a new project, ask the course editor assistant to add one to a named unit, specifying its type and what the learner should demonstrate.
3. For an unconfigured project, use **Choose a template** to select the format. Configured projects open their existing editor.
4. Attach the relevant course materials and describe the result learners should produce.
5. After editing, use that project's save control and reopen it to check the saved configuration. Saving a project draft is separate from publishing the course.
For example: “Add a Scenario project to Product onboarding. The learner should ask a fictional customer about their training goal and confirm the next step. Use fictional names and three clear evaluation criteria.”
## Scenario: practice a conversation
Use **Scenario** to rehearse customer conversations, coaching, interviews, or other interactions with AI characters. Start with a written description of the situation and the skills learners should practice.
1. Describe the setting, characters, learner goal, and behavior to evaluate under **Create your scenario**.
2. Enable **Scene Images** if the scenario needs visual aids, then select **Generate Scenario**.
3. In **Story**, review **Situation Context**, **Learner Goal**, and **Greeting Message**.
4. In **Characters**, edit each character's **Name**, **Role**, **Description**, **Personality**, and **Knowledge**. Use **Add Character** when the role-play needs another participant. Review the selected **Voice** and generated portrait.
5. In **Evaluation**, edit the criteria and their weights. Make each criterion describe observable learner behavior.
6. In **Settings**, choose **Text Only**, **Voice Only**, or **Text & Voice**. Review **Custom Prompt Instructions** and the optional **Finish Button Label**.
7. If appropriate, configure **Language Learning**, its target/source languages, and voice-session recording options. Use **Record sessions** to retain voice conversations.
8. Select **Save**, then open the learner view to try the conversation and its evaluation.
Choose Text Only for typed conversation. For voice practice, connect a microphone and allow browser microphone access. Configure recording and learner replay to suit your program. Use direct field edits for small refinements or **Regenerate** to create a new version.
### Complete a text role-play
1. Read **Your mission**, including the situation, goal, and character, then select **Start scenario**.
2. Type in **Message to Jordan Rivera** and select **Send message**. In this example, start by asking what Acorn Team wants to achieve in its first week.
3. Use the character’s reply to guide the conversation. Recommend the **Customer onboarding checklist**, agree on one practice task and the Help channel, then confirm a Friday check-in.
4. Select **End the call** when the conversation is complete.
5. Review the score, **Feedback**, **Strengths**, **To improve**, and **Performance breakdown**. Select **Try again** for another practice round.
## Tagalong: guide a physical task
Use **Tagalong** when a learner will show an in-person task through a phone camera. Prepare concrete steps that can be recognized visually.
1. Select **Tagalong** and choose **Describe** or **Video** under **Create Tagalong**. You can also choose **Skip** to create the steps manually.
2. For **Describe**, explain the physical task. Use **Attach file** if an approved procedure document should inform the steps, then choose **Generate Steps**.
3. For **Video**, choose **Upload a phone video**. The picker accepts MP4, WebM, or MOV up to 500 MB. Review the selected recording, then choose **Generate from Video**.
4. Edit **Title**, **Description**, and **Greeting Message**.
5. Review **Steps**. Each needs a title, a physical action, and an optional hint. Use **Add Step**, **Move step up**, **Move step down**, and **Remove step** to arrange the procedure.
6. To attach a reference to a step, choose **Add link or reference**, select **URL** or **Image**, enter the URL and an optional label, and choose **Add**. Select **Save**, reopen the project, and check the step order, text, and references.
7. In the learner view, choose **Start session**, follow the phone-pairing flow, and allow the requested camera and microphone access. Test whether the actual camera view makes each required action visible.
Step references open from the desktop learner step list and session checklist. Link to resources your learners can access.
Align each step with the procedure learners will perform, and frame the camera so the required action is visible.
## Use an Agent: create an artifact with AI
This is a learner project format, separate from the workspace Agents administration area.
1. Select **Use an Agent**.
2. Choose **Image Generation**, **HTML & Web**, **Writing & Research**, **Spreadsheet**, or **Full Stack App**.
3. Describe the artifact the learner should produce and the constraints they must satisfy. Select **Generate**.
4. In **Preview**, review the generated steps. Edit their titles/descriptions, reorder them, or add/remove steps. Review the Agent context and available chat appearance controls.
5. In **Instructions**, write what the learner should do. In **Rubric**, review the grading criteria, descriptions, and weights.
6. To request a broader change, describe it in the AI edit bar and choose **Apply**. Inspect the result, then **Approve** to save it or **Reject** to restore the previous configuration. Use **Save** for direct edits.
7. In the learner view, choose **Begin**, work through the steps with the project Agent, inspect the resulting artifact, and submit when the task is ready.
For **Full Stack App**, the learner publishes the application and completes its live check before submitting the project.
The demo below shows all three guided steps complete and a generated welcome-email draft. Review the artifact before selecting **Submit project**; finishing the steps is separate from submitting for grading.
## Prompt Challenge: reproduce a reference
Use **Prompt Challenge** when the learner should iteratively prompt an AI to match an image or website reference.
1. Select **Prompt Challenge**, then choose the image or website challenge option.
2. Describe the reference and what a successful match should demonstrate. Choose **Generate**.
3. In **Preview**, review the generated image or website reference and refine it to match the skill you want learners to practice.
4. Review **Instructions**, **Rubric**, and the displayed passing score. Use the AI edit bar to request a change to the task or reference; inspect the result before approving it.
5. Save direct edits and reopen the project to check that the reference and instructions remain correct.
6. In the learner view, choose **Begin**. Describe the reference in the prompt box and send your prompt. Compare the generated image with the reference, then select **View Feedback** to see what to refine.
7. Try another prompt if needed. When ready, select **Submit project** to receive the project’s rubric evaluation.
Use the match score and feedback to guide another prompt. Learners can refine their wording, compare successive results, and submit their strongest attempt.
The example describes the badge’s shape, text, star, colors, and illustration style. The generated attempt appears beside the reference, with a visual match score and feedback.
**Submit project** evaluates the work against the project’s rubric. This is a separate result from the image-match score: the example received an 85% visual match and 90/100 for its prompting criteria.
## Code Notebook: program in cells
Use **Code Notebook** for code and Markdown cells with optional guided steps and test cases.
1. Select **Code Notebook** and describe the programming task and language.
2. Enter the required packages, decide whether to include guided steps, and specify a GPU only when the task needs one. These values guide generation; inspect the generated environment before use.
3. Choose **Generate**.
4. In **Preview**, edit the starter cells inline. Add code or Markdown cells, change their order, remove unnecessary cells, and lock cells that learners should not edit.
5. Review guided-step completion criteria, test cases, expected results, and weights. Edit the package list and supported environment settings as needed.
6. Review **Instructions** and **Rubric**, then **Save**.
7. In the learner view, begin the notebook, run its cells, inspect output/errors, and complete the task. **Submit** is disabled while a cell is running.
Choose packages and compute resources for the exercise, then run the starter cells and test cases. Learners can use a new attempt when they want a fresh workspace.
The demo reads three fictional customer records, counts the two with status `done`, and returns `2`. Its submitted solution received 100/100. After submission, **View work** opens the notebook read-only. Use **Back to results** to return to feedback, or start a new attempt to make changes.
## Screen Share: guide work in a real application
Use **Screen Share** when the learner performs the task in another application while sharing their screen with Honen.
1. Select **Screen Share**. Under **Create Screen Share**, choose **Describe**, **Record**, or **Video**. For a hand-authored procedure, choose **Skip** and create the steps manually.
2. In **Describe**, explain the task and optionally **Attach file**, then choose **Generate Steps**.
3. In **Record**, follow the recorder's screen-selection and permission prompts. In **Video**, upload an MP4, WebM, or MOV recording up to 500 MB and choose **Generate from Video**.
4. Edit **Title**, **Description**, **Greeting Message**, and the ordered **Steps**. Each step should name an action visible on screen; add a hint for likely difficulties.
5. Use **Add Step**, the move controls, and **Remove step** to refine the sequence. Use **Add link or reference** for supporting links or image URLs, then **Save** and reopen to verify them.
6. In the learner view, choose **Start session** and share the appropriate application or screen through the browser picker. Check guidance and completion feedback against the real task.
Learners open the target application with their own access and share it through the browser. Choose **Screen Share** for live guidance, or **Interactive Walkthrough** below for a recorded practice experience.
## Full Sandbox: build a development workspace
Use **Full Sandbox** for a provisioned development environment with starter files and grading checks.
1. Select **Full Sandbox**. In **Project**, choose a template such as **HTML, CSS, and JavaScript**, **React with Vite**, **Next.js**, **Python**, **Node.js**, or **Custom project**. Write the project brief and steps.
2. In **Code**, edit starter files, upload files/a folder, or import a **Public Github Repository**. Review the imported files as the starting point for each learner’s workspace.
3. In **Environment**, review the available editor tools/extensions.
4. In **Environment**, configure the run command, preview port, compute, runtime, and any setup commands. Use dependencies and resources appropriate to the exercise.
5. In **Grading**, add automatic checks with their descriptions, points, commands, and timeouts. Review the available check types and any AI review criteria.
6. Choose whether grading finalizes the attempt or returns feedback while allowing continued work. Optionally provide a reference solution and a known-bad solution for grading self-tests.
7. Choose **Save draft**, then **Build** to validate the configuration. Resolve reported errors. Editing the configuration invalidates the previous validation result.
8. Complete the course publication flow to make the sandbox available to learners.
9. In the learner view, create an attempt, wait for setup, open the editor, run the task, and use the available grading action. Review check results and any runtime errors.
Try the learner workspace to review the starter files, terminal, live preview, and grading results as one complete exercise.
The Northstar example uses three starter files and an automatic check for a welcome heading. **Build** reports **Sandbox Configuration Checked** before the learner opens a workspace.
In the learner workspace, edit `index.html` with fictional customer details and save it. Run the configured development command in the terminal, then select **Preview** to inspect the page. This example uses `python3 -m http.server 4173 --bind 0.0.0.0`; use your own project's configured command and port.
After checking the preview, select **Grade attempt** and inspect the result. This demo received **Passed**, 100/100, for the configured welcome-heading check. That result applies to this exercise and its rubric.
## Interactive Walkthrough: create a clickable recording
Use **Interactive Walkthrough** for a recorded interface with guided targets. Prepare a screen recording of the exact workflow, using fictional or approved material.
1. Select **Interactive Walkthrough** and choose **Upload a recording**. Select MP4, WebM, or MOV.
2. Wait for recording analysis and saving to finish. Long recordings can take several minutes. Open the generated walkthrough when it is ready.
3. Open **Preview** and click through every step. Check frame choice, sequence, target placement, and captions.
4. Choose **Advanced edit**. Select a step and edit **Step type**, **Target label**, and **Caption**. Drag the highlight and click point onto the intended target, then choose **Save step**.
5. To change the image, save current edits first, choose **Choose frame**, seek in **Source recording**, and select **Use frame**.
6. Use **Duplicate step**, **Move earlier**, **Move later**, or **Delete step** to adjust the sequence. At least one step must remain.
7. Choose **Done editing**, then replay the walkthrough. For continuous step types, the learner’s interaction advances to the next step in the recording.
8. If public sharing is intended, review the complete recording-derived content before using **Public embed → Enable embed**. Copy the generated embed only after that review; **Disable** turns off the public embed.
Changing a recording is a different operation from correcting a hotspot. Save pending step edits before switching steps, changing frames, or uploading another recording. If the walkthrough changed elsewhere, reload the editor rather than overwriting a newer version.
## Form: collect a structured response
Use a Form project when learners should complete a worksheet or submit several related answers. Describe the task and attach the source procedure, then review the generated questions and grading rubric. Preview the form, complete each field as a learner, and inspect the submitted feedback before sharing it.
Follow [Create a Form project](https://honen-academy.honen.com/docs/6ab3766e78ce9f1718279689) for the complete generation, direct-editing, learner submission, and feedback walkthrough.
## Preview and deliver your project
Open the saved project as a learner, follow its instructions, and review the completed result and feedback. This gives you a final opportunity to refine the task, supporting materials, and evaluation criteria before assigning it.
For structured learner responses, follow [Create a Form project](https://honen-academy.honen.com/docs/6ab3766e78ce9f1718279689).
See [Activity and Project Types](https://honen-academy.honen.com/docs/6ab35ee2da8e0901468ca367) for the format overview, [Add sources to a course](https://honen-academy.honen.com/docs/6ab36136effafe59361d22cd) for source preparation, [Edit and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c) for the editor, and [Publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) before release. Use [Assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) to set required projects for a cohort.
## Create and grade a form project
Source: https://honen-academy.honen.com/docs/6ab3766e78ce9f1718279689
Use a form project when learners should submit a structured response, such as a plan, reflection, or checklist. This walkthrough uses fictional welcome-call data in the Northstar demonstration course.
## 1. Create the exercise
1. Open the course editor and its **Course Editor Assistant**.
2. Name the unit that should contain the project and describe the fields, learner task, and evaluation criteria.
3. Ask for a **form project**. For this example: “Add a welcome-call planning form to the practice unit. Ask for the customer's week-one goal, one approved guide, and a three-part definition of done. Use fictional data. Grade each part against the supplied welcome-call playbook.”
4. Wait for generation, then select the project in the **Edit** course tree.
5. Check the form's **Preview** tab. Confirm each field has a clear label and the expected input type.
## 2. Check learner instructions and grading
1. Open **Instructions**. Write directions to the learner, including the scenario, what to submit, and the sources they should use.
2. Open **Rubric**. Check each criterion's name, weight, and description.
3. Make the expected answer concrete. If **Customer onboarding checklist** is the approved guide, say so in both the task and the relevant criterion. Learners can then use the same criteria to prepare their response.
4. Select **Save**, then **Apply Changes** when the course has a saved draft to apply.
In this example, the three criteria are **Goal captured**, **Approved guide named**, and **Definition of done**. Describe the evidence you expect and allow equivalent correct wording.
## 3. Try the learner submission
1. Open the project's **Preview** link to enter the learner experience.
2. Read **Instructions** and select **Begin**.
3. Complete all three fields using the fictional customer scenario.
4. Select **Submit** and wait for evaluation.
5. Review the score, criterion breakdown, and feedback to see how the response meets the rubric.
Use **View work** to inspect a submitted response. If you change the instructions or rubric after testing, apply the change and use **New attempt** to check it again. An existing attempt's feedback remains evidence of the earlier submission.
## Continue
See [Activities and projects](https://honen-academy.honen.com/docs/6ab35ee2da8e0901468ca367) to choose another exercise type, [Edit and review a course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c) to manage revisions, and [Role-based training](https://honen-academy.honen.com/docs/6ab3767c78ce9f17182796e6) to connect the exercise to a real work task.
## Configure course and tutor settings
Source: https://honen-academy.honen.com/docs/6ab3613ceffafe59361d22e7
Use course Settings to control metadata, topic entry, and tutor behavior. You need editing access to the course.
## 1. Check basic information
1. Open the course editor and select **Settings**.
2. Select **General**.
3. Review **Course Title**, **Description**, and **Content type**.
4. Make your changes and select **Save Changes** when it becomes available.
5. If using a reusable format, inspect **Course template** beneath the basic fields.
The short description appears on course cards and has a character limit. Changing the content type updates presentation and how AI scopes new content. Use the editor to revise existing activities.
## 2. Choose how a topic opens
1. Select **Learner experience**.
2. Choose **Topic start screen** to show goals and the activity picker, or **Inline intro banner** to start on an activity with a compact introduction.
3. Choose **Start learners on** for the default activity used when a topic has one activity or when resuming from a direct link.
4. Inspect the preview and save your changes.
The settings panel's preview is a built-in example. Check your actual course with **View as Learner** too.
## 3. Review tutor behavior
1. Select **Tutor** in the settings navigation.
2. Choose **Standard** for the activity-focused voice/plain-text tutor, or **Advanced** for richer formatted responses and optional research.
3. If Advanced is selected, inspect the available switches for **Search the knowledge base**, **Search the whole course**, and **Generate illustrations**.
4. Mode and capability changes save as you select them. Wait for the saving state to finish, and check for errors. Review **Tutor Personality** below the mode controls.
5. Check the learner experience in a new tutor session; the screen states that changes apply to the next session.
Knowledge Base search is constrained by the learner's access. Course **Guardrails** are configured separately. Use [Tutor guardrails](https://honen-academy.honen.com/docs/6ab38b7b3b82ff9f26dee95f) to set the coaching boundaries that apply across courses.
## Tips for your next step
Start a new tutor session after changing its mode or capabilities. Use the course's [publishing workflow](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) when releasing changes to the learning content.
## Adapt a course to your audience
Source: https://honen-academy.honen.com/docs/6ab380f882700be81b7d02c1
Make the same expertise useful to different people. Give the Course Editor Assistant a clear audience, learning goal, and scope, then review the adapted lessons and practice together.
## 1. Choose the shape of the training
Decide how your learners will use the material before asking for changes.
| Your goal | Course structure |
| --- | --- |
| Each role needs its own examples, practice, and delivery | Create a separate course for each role from the same approved sources. |
| Several roles share a foundation and then branch into different responsibilities | Ask for a course with shared material and clearly named role-specific units. |
| An existing cohort needs a clearer or shorter explanation | Edit the relevant topics in the existing course. |
| A program spans several courses | Organize the courses into a [learning path](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350). |
For a new course, follow [Create your first course](https://honen-academy.honen.com/docs/6ab35ee5da8e0901468ca374). Name the role in the brief and inspect its proposed outline before approving generation. For example:
> Build a beginner course for customer onboarding specialists from the attached playbook. Focus on preparing a welcome call, confirming the customer's goal, and agreeing on next steps. Include a short reading, practice quiz, and conversation scenario.
## 2. Open the existing course and define the change
1. Open **Organization → Courses and content**, find the course, and select **Edit**.
2. Use **Preview** to inspect the current topic and its available activities.
3. Open **Course Editor Assistant**.
4. Identify the unit or topic, the intended audience, and what should change.
5. Name the learning goals, source facts, or terminology to retain.
A focused request gives you a clear result to review:
> Adapt the Welcome call topic for new support specialists. Explain unfamiliar terms before using them and use an example from the attached onboarding checklist. Keep the three preparation steps and the existing learning objectives.
For direct changes, select **Edit**, open the topic, and review **Learning objectives** and **Generation instructions**. Use the assistant to revise the existing activities to match those directions.
## 3. Specify language, reading level, length, or format
Use the change that serves the learning task. Combine compatible requests when the result is easy to review.
| Adaptation | Example request |
| --- | --- |
| Language | “Translate the Welcome call topic into Spanish, including the reading, flashcards, quiz questions, answer explanations, and project instructions. Keep product names in English.” |
| Reading level | “Explain this topic for a beginner. Define each technical term, shorten long sentences, and preserve the required procedure.” |
| Audience and tone | “Use examples for an account executive preparing a discovery call. Keep the source's product facts and use direct, practical language.” |
| Length | “Make this a ten-minute introduction. Keep the safety-critical steps, remove repeated background, and shorten the practice to the essential decisions.” |
| Modality | “Create a short podcast for this topic using the attached checklist. Teach the same learning goals and include a worked example.” |
For translated material, include your preferred terminology and regional language choices. For shorter training, identify which decisions or procedures remain essential. For audio or illustrated activities, review the generated media as well as its script or text using [Create and edit media activities](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665).
## 4. Choose evidence that matches the skill
Adapt the practice alongside the explanation. A new audience may need different examples while demonstrating the same skill.
| What the learner should demonstrate | Choose | How to interpret the result |
| --- | --- | --- |
| Recognize a correct fact or decision | Quiz or unit-test questions with reviewed answers | Responses are checked against the configured answers; explanations help the learner understand mistakes. |
| Explain a choice or produce a written artifact | Form or Agent project | Review the authored rubric and AI feedback against the submitted work. |
| Handle a conversation | Scenario | Use the character's goal and weighted evaluation criteria to assess the interaction. |
| Write functioning, readable code | Code Notebook | Executed test cases check defined behavior; rubric criteria assess qualities such as clarity. Set the point allocation for both. |
| Improve a prompt toward a visual reference | Prompt Challenge | Compare the generated result with the reference and use the match feedback to guide another attempt. |
| Follow a procedure | Interactive Walkthrough, Screen Share, or Tagalong | Select the format for a recorded interface, a live screen, or a physical task, then inspect its steps and evaluation settings. |
[Create and edit projects](https://honen-academy.honen.com/docs/6ab3766c78ce9f1718279677) explains the project controls. Use [Assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) to set which work is required and the passing criteria. A [curriculum certificate](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350) represents the configured learning path and its completion requirements.
## 5. Review the adapted experience
1. Return to **Preview** and open each affected activity.
2. Check that the explanation, terminology, examples, and source facts fit the audience.
3. Answer the revised quiz questions and inspect their explanations.
4. Open project instructions and rubrics. Confirm that the requested task and evaluation criteria agree.
5. For translated content, check navigation between affected activities and read the questions, answers, and feedback in the intended language.
6. Select **Apply Changes**, or **Save & Apply** when shown, and wait for the operation to finish.
Use **Version History** to inspect the resulting revision. Follow your [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) workflow when the course is ready for its delivery destination.
## Reuse a successful adaptation
Put a recurring audience brief, terminology preferences, and source instructions into a [template or Skill](https://honen-academy.honen.com/docs/6ab35ee8da8e0901468ca386). Use the same learning goals across role variants when you want to compare their outcomes. [Build a role-based training program](https://honen-academy.honen.com/docs/6ab3767c78ce9f17182796e6) connects those courses to cohorts, assignments, and reporting.
## Personalize the experience for individual learners
For learner-specific examples and support within one course, use [Course personalization](https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2), [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0), and [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf). These controls let learners share their goals, receive timely support, and accept optional topics in their own lesson plan. Start with [Enable and review adaptive learning](https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2).
## Templates, Rules, and Skills
Source: https://honen-academy.honen.com/docs/6ab35ee8da8e0901468ca386
Give your team a repeatable way to create learning. Templates define the starting format, Rules apply standing requirements, and Skills make useful prompts available on demand. Manage them in **Organization → Rules, Skills & Templates**.
## Choose your starting point
| Control | What it does | Example |
| --- | --- | --- |
| Template | Packages setup questions, structure, instructions, Skills, and source folders for a Course, Atom, or Assessment | A first-week onboarding course |
| Rule | Applies an enabled standing instruction on selected AI surfaces | Use numbered steps and a concrete success check |
| Skill | Runs a reusable prompt when someone invokes it | Turn a learning goal into a checklist |
Management permissions for Rules, Skills, and Templates are separate, so your organization can delegate each responsibility.
## Start with a template
1. Open **Create** and select an enabled template offered for the content type.
2. Complete its starter fields and add your subject or source material.
3. Answer the setup questions and review the proposed outline.
4. Approve the outline to begin building the content.
5. Preview and edit the completed draft before publishing.
A template sets its content type. Clear it to return to your own prompt or choose a different type. Your team controls which enabled templates appear through **Replace course suggestions with templates**.
For the full setup, including starter fields, custom questions, activity choices, source folders, covers, and template lifecycle, see [Create and manage templates](https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923).
## Apply reusable guidance
Create a [Rule](https://honen-academy.honen.com/docs/6ab38b6b3b82ff9f26dee938) when an instruction should apply every time on chosen surfaces. Create a [Skill](https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a) when an author should choose when to run a task. New Skills start restricted; [share them](https://honen-academy.honen.com/docs/6ab38b703b82ff9f26dee941) with the intended people or groups.
Use [Brand standards](https://honen-academy.honen.com/docs/6ab38b5f3b82ff9f26dee916) for generated visuals and [Tutor guardrails](https://honen-academy.honen.com/docs/6ab38b7b3b82ff9f26dee95f) for learner-facing coaching behavior.
## Use a template on an existing course
Open **Settings → General → Course template** in the course editor. Attach or change a template to guide future editing, then ask the assistant for the changes you want. Selecting a template keeps the existing content.
A course retains its saved template instructions if the original template is later removed or unavailable. Selected Skills and Knowledge Base folders retain their own access requirements.
Continue with [Governance](https://honen-academy.honen.com/docs/6ab38b5e3b82ff9f26dee911) to connect authoring standards, source ownership, and publishing approvals.
## Catalogs, Publishing, and Review
Source: https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381
Team workspaces can review a submitted course version before it reaches a catalog. Publishing approvals are a workspace setting, with review policies and assigned reviewers on each catalog. Personal workspaces do not have catalog publishing reviews.
## Set up a destination
In **Publishing**, manage catalogs and their covers, descriptions, audiences, courses, and ordered curricula. Enable workspace publishing approvals when your team needs them, then select the catalog’s reviewers and required number of approvals. Catalog management has its own role permission.
Catalogs have browse pages and can be connected to groups or Sites. A catalog’s audience determines who can access it. Review approval does not grant an audience access outside those settings.
## Submit and review
1. Finish the working draft and open **Publish**. Choose the destination catalogs; one submission can target several catalogs.
2. Where approval is required, a request holds the submitted revision. Authors can continue editing without changing the version under review.
3. Open **Publishing reviews** or a request from **Inbox**. Search and filter the queue, then select a request.
4. **Changes** compares the lessons, questions, media, and settings affected by the update. **Course preview** shows the submitted learner experience.
5. Leave comments on changed content or select a passage in the preview to start a thread. Choose **Approve** or **Send back** with feedback.
6. Once the required approvals are satisfied, the publication can be delivered to its selected catalog. An approved request and a successfully delivered publication are distinct states.
Inbox collects review requests, course feedback, and publishing decisions across workspaces. Access to a request and permission to decide it are checked for each person.
## Agent proposals
An Agent with permission to propose changes can prepare an update to selected courses and submit it to course editors or a catalog’s review queue. Its instructions describe the work; its access policy determines which knowledge, courses, and actions it can use. A proposal does not bypass the review policy.
Schedule recurring checks with [Automations](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331). The **Knowledge base drift** automation starter identifies affected courses and suggests updates; its default instructions do not edit them. To prepare actual changes, configure an Agent with proposal access and describe that task explicitly.
## Drafts and history
A working draft, a submitted revision, and a catalog publication serve different purposes. Review uses the submitted version. **Filesystem** in course settings lets editors inspect saved versions and their files; optional branches provide a separate place to prepare changes. Version history and existing learner records remain available.
## The Learner Experience
Source: https://honen-academy.honen.com/docs/6ab35efbda8e0901468ca3e5
A Honen course brings lessons, practice, projects, and a tutor into one learning experience. The formats you see depend on what the author included. Your course and assignment settings determine what you must complete.
## Open a topic and choose a format
1. Open your course or assignment and select a topic from its lesson plan.
2. If a start screen appears, read the goals and choose an available activity.
3. Use **Read** for the lesson, **Flashcards** for recall practice, or **Quiz** to check understanding. Media formats appear when the course includes them.
4. On desktop, use **Add another activity pane** to keep two formats visible.
Follow the detailed walkthroughs to [read and navigate](https://honen-academy.honen.com/docs/6ab361aaeffafe59361d243e), [study flashcards](https://honen-academy.honen.com/docs/6ab361adeffafe59361d2450), [take a quiz](https://honen-academy.honen.com/docs/6ab3619beffafe59361d23fe), or [study side by side](https://honen-academy.honen.com/docs/6ab361b3effafe59361d2467).
## Ask for help
Open the tutor alongside the current activity. Start a session, ask a specific question, and use the microphone and audio controls independently. You can use text with both muted. Pause the session when taking a break.
Your author selects Standard or Advanced tutor mode and the tools available in the course. Advanced mode supports richer responses and optional course or Knowledge Base search, with access and assessment settings tailored to the learning experience.
See [Ask the AI tutor for help](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432).
## Practice and demonstrate a skill
A topic quiz provides feedback on its questions. When a confidence step appears, record how certain you are before reading the explanation. Projects ask you to do work, such as handle a scenario, write a prompt, complete a worksheet, or build an artifact. Read the project's instructions and grading criteria before submitting.
Unit tests are separate from practice quizzes. Open the unit's test from the lesson plan, complete its required responses, and submit it explicitly.
## Check progress and remaining work
Open the lesson plan and inspect **Finish the course**. The remaining-work list takes you to the tests, projects, and activities needed to complete your course.
Your course, assignment, and curriculum each have completion requirements chosen by the author. Complete the required tests, projects, and activities to progress toward your certificate. See [unit tests and remaining work](https://honen-academy.honen.com/docs/6ab361a1effafe59361d2418).
## Continue practicing
Study banks offer self-directed review of flashcards and quiz questions. Keep sharp provides separately configured course refreshers and follow-up checks. Use them alongside your course's required tests and projects. See [Study banks and spaced repetition](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718) · [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045).
## Sources and personalization
Source citations can appear in readings grounded in Knowledge Base documents. The course's citation visibility settings and your permissions determine which sources you can open.
Where personalization is offered, review the adapted explanation against the original learning goal. Ask the tutor about an unclear passage and check important procedures against the approved source.
## Learning, practice, and progress
Source: https://honen-academy.honen.com/docs/6ab3812782700be81b7d032e
A course offers several ways to study a concept, practice it, get feedback, and return to material that needs more work.
This guide follows the learner-facing controls you can use in a course. Available formats and requirements depend on how the course and assignment are configured.
## Study the concept
Open a topic and read its learning goals. Choose an available format, such as a reading, lecture, video, or podcast. Use another format when a different explanation would help. On desktop, you can keep two activity panes open together.
[Read and navigate a course](https://honen-academy.honen.com/docs/6ab361aaeffafe59361d243e) · [Study side by side](https://honen-academy.honen.com/docs/6ab361b3effafe59361d2467)
## Recall, answer, and get feedback
Try to recall a flashcard's answer before revealing it. In a quiz, answer the question and record your confidence when prompted. Read the explanation before continuing: a correct guess and a confident, well-understood answer are different learning signals.
[Study flashcards](https://honen-academy.honen.com/docs/6ab361adeffafe59361d2450) · [Take a quiz](https://honen-academy.honen.com/docs/6ab3619beffafe59361d23fe)
## Ask for an explanation and apply the skill
Use the tutor to work through an unclear concept or example alongside the activity. Projects provide another kind of evidence: the learner performs a task, follows a procedure, builds an artifact, or responds to a scenario. The project's instructions and criteria explain what it asks the learner to demonstrate.
[Ask the tutor](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432) · [Activity and project formats](https://honen-academy.honen.com/docs/6ab35ee2da8e0901468ca367)
## Return for practice
Study banks offer spaced-repetition review and free practice. Reveal an answer, rate your recall, and use the displayed review intervals. Keep sharp adds retention checks where the author or assignment has enabled them.
[Study banks and spaced repetition](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718) · [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045)
## Understand completion
Use the lesson plan to see remaining work and submit required tests and projects explicitly. Completion follows the course and assignment requirements, while practice and feedback help you develop the underlying skills.
[Unit tests and remaining work](https://honen-academy.honen.com/docs/6ab361a1effafe59361d2418)
See [The Learn Engine](https://honen-academy.honen.com/docs/6ab35efada8e0901468ca3e0) for the adaptive learning system behind mastery measurement and personalized study.
## The Learn Engine
Source: https://honen-academy.honen.com/docs/6ab35efada8e0901468ca3e0
The Learn Engine is Honen’s adaptive learning system. It brings together mastery measurement, topic clustering, and smart recommendations to help learners choose useful study material and build understanding over time.
Answers, confidence, the material studied, and progress through a subject provide learning signals. The system uses those signals to guide study toward stronger understanding of the topic.
## Three parts working together
| Component | What it contributes |
| --- | --- |
| **K-Score** | A measure of topic mastery informed by performance, question difficulty, confidence, and learning interactions. |
| **Topic clustering** | Connects learning signals from people studying the same topics, so relevant learning experiences can be considered together. |
| **Smart recommendations** | Uses those patterns to identify materials and study sequences associated with improvements in mastery. |
### K-Score: understanding a topic
K-Score is the Learn Engine’s mastery measure. It considers how a learner performs on questions, the difficulty of those questions, their confidence, and their continuing interactions with study material.
The goal is a developing picture of understanding. For example, a correct answer with low confidence offers a different signal from a correct answer the learner can explain confidently. Further practice adds evidence as the learner works through the topic.
K-Scores describe learning within the platform, in the context of others studying the same material. Use that learning context to understand what needs practice and what is becoming more secure.
### Topic clustering: learn from relevant patterns
Topic clustering brings together signals about shared subject matter. This gives the system a way to consider what helped other learners studying the same concepts, alongside the individual learner’s own work.
For example, learners studying a particular concept may benefit from a visual explanation followed by a question set. Connecting those experiences by topic helps the system identify useful patterns in the material and study sequence.
### Smart recommendations: guide the next study step
Smart recommendations draw on learning history to identify content associated with stronger mastery. Existing explanations, practice materials, and effective study sequences can all contribute to a useful next step.
As learners study and answer more questions, the system gains new information about how the recommended material helped. Its design supports an ongoing cycle:
1. Measure understanding of a topic.
2. Connect relevant learning experiences around that topic.
3. Recommend materials associated with improved mastery.
4. Use subsequent performance to update the picture of understanding.
5. Refine future recommendations from the new evidence.
## The learner’s role
Engage with the material, try questions before looking at explanations, and report confidence honestly when asked. Use the tutor to work through uncertainty, then apply the concept in practice.
Honen offers several ways to do this: readings and media for explanations, flashcards and quizzes for recall, projects for applying skills, and Study banks and Keep sharp for continued practice. These are the course controls you use day to day; the Learn Engine describes the adaptive system connecting mastery and recommendations.
Follow [Learning, practice, and progress](https://honen-academy.honen.com/docs/6ab3812782700be81b7d032e) for the practical study flow. See [Take a quiz](https://honen-academy.honen.com/docs/6ab3619beffafe59361d23fe), [Ask the tutor](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432), [Study banks and spaced repetition](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718), and [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045) for individual walkthroughs.
## Read a lesson and navigate the course
Source: https://honen-academy.honen.com/docs/6ab361aaeffafe59361d243e
Open a topic, study its content, and move between lessons. The examples use the fictional Northstar onboarding course.
## 1. Enter the course
1. Open a course you can access from **My Courses** or its assigned link.
2. Choose a topic from the course outline.
3. If a topic start screen appears, review the learning goals and choose an available format.
4. Select **Read** to open the reading.
Course authors can also use **View as Learner** from the editor. That view has author controls ordinary learners may not see.
## 2. Work through the topic
1. Read the content and inspect its images and examples.
2. Complete any interactive elements in the reading.
3. Use the format buttons to practice with **Flashcards** or **Quiz**, when available.
4. Use **Next** to move onward after the work is complete.
Available formats depend on what the author generated. The demo includes reading, flashcards, and quiz; a topic does not necessarily include every format.
## 3. Use the lesson plan
1. Select the topic title or lesson-plan icon in the top bar.
2. Expand the relevant unit.
3. Select a topic or unit test.
4. Read any remaining-work message near **Finish the course**.
5. Close the lesson plan to return to the current activity.
In an author's learner view, a warning can appear when the live learner version differs from the latest draft. Use the editor's Preview to inspect draft changes.
Continue with [flashcards](https://honen-academy.honen.com/docs/6ab361adeffafe59361d2450), [a quiz](https://honen-academy.honen.com/docs/6ab3619beffafe59361d23fe), or [the tutor](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432).
## Study with two activity panes
Source: https://honen-academy.honen.com/docs/6ab361b3effafe59361d2467
Keep a reference visible while practicing by opening two formats beside each other on desktop.
## 1. Open the first activity
1. Open a topic with more than one format.
2. Select **Read**, or another format you want as your reference.
3. Select the plus control labeled **Add another activity pane** at the right edge.
## 2. Pick the second format
1. In the new pane, open the relevant activity group.
2. Choose an available activity, such as **Flashcards**.
3. Use the format controls within each pane to change what it shows.
4. Drag the divider between panes if you need to adjust their widths.
## 3. Return to one pane
Select **Close activity pane** (the X in that pane's toolbar). The other activity remains available. On narrower screens, use one activity at a time for a readable layout.
## Ask the AI tutor for help
Source: https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432
Ask for an explanation while keeping the lesson in view. Use text, voice, or both, with separate controls for microphone input and audio output.
## 1. Open the tutor
1. Open a course topic.
2. Select **Open tutor chat** at the bottom right.
3. Select **Start tutor** to begin the session.
4. If using text only, use the microphone and audio controls to keep them muted.
For voice, your browser may ask for microphone permission. Only enable it when you want to speak.
## 2. Ask a focused question
1. Type in **Message your tutor…**.
2. Ask about the current concept, a confusing example, or a practice step.
3. Send the message and read the response.
4. Ask a follow-up if the explanation does not resolve the question.
Example: “Explain a measurable onboarding outcome using a fictional task-management example.”
The tutor can help explain the lesson; check critical procedures against the course's approved source material.
## 3. Manage the session
1. Use **Pause** when taking a break. The interface changes to **Tutor paused** and **Resume**.
2. Select **Resume** to continue.
3. Use the microphone and audio buttons to control input and output separately.
4. Open **Tutor settings** for the controls available in your course.
5. Use **Close tutor chat** when you want more room for the lesson.
Closing the chat panel and pausing the session are different controls. Pause before leaving the conversation if you are done for now.
## Tips for your next step
Select **Start tutor** to begin the session. Choose your preferred microphone, speaker, and mute settings for voice conversations. Available tools follow the course’s Tutor settings and your access, with test-specific assistance and attachment controls.
## Proactive help and optional practice
When the course enables [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0), a thought bubble can offer help or acknowledge progress while you learn. Click it to open the same tutor pane. With [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf), the tutor can also suggest optional topics that you accept with **Add & start**.
## Study with flashcards
Source: https://honen-academy.honen.com/docs/6ab361adeffafe59361d2450
Practice recall by answering the front of a card before flipping it. Flashcards must be available for the current topic.
## 1. Open the deck
1. Open a topic.
2. Select **Flashcards** in the format bar.
3. Check the card count at the top.
4. Read the term or question and try to answer it before flipping.
## 2. Reveal and continue
1. Select the card or use **Flip**. The control also shows the Space shortcut.
2. Compare your answer with the revealed definition.
3. Use **Next card** or **Previous card** to move through the deck.
4. Use a numbered progress dot to jump to a particular card.
5. Select **Show hint** when available if you need a prompt before revealing the answer.
## 3. Change practice order
1. Open **Flashcard settings** (the three-dot control).
2. Choose **Shuffle** to vary the order.
3. Choose **Show term first** or **Show definition first** to change the direction of recall.
4. Use **Restart** when you want to begin again.
You can also [open the reading beside the deck](https://honen-academy.honen.com/docs/6ab361b3effafe59361d2467) using **Add another activity pane** on desktop. For scheduled recall ratings, use [Study banks](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718).
## Take a quiz and review feedback
Source: https://honen-academy.honen.com/docs/6ab3619beffafe59361d23fe
Use a topic quiz to check understanding, record confidence, and learn from explanations. The example uses a six-question quiz about planning an onboarding lesson.
## 1. Open the quiz
1. Open the topic and select **Quiz**.
2. Read the question and all answer choices.
3. Select an answer. Choose **I don't know**, when offered, if you cannot answer yet.
## 2. Record confidence
1. Check the answer shown under **Your answer**.
2. Use **Change answer** if you selected the wrong option by mistake.
3. Choose **Not sure**, **Somewhat sure**, or **Very sure**.
The interface lists keyboard shortcuts: letter keys choose an answer, 1–3 choose confidence, and Enter advances when the next action is available.
## 3. Read the explanation
1. Review whether the answer was correct.
2. Read the explanation below it, even if you answered correctly.
3. Select **Next question**.
4. Repeat for the remaining questions. The progress dots show answered and unanswered items.
## 4. Complete the quiz
1. After the final response, select **Complete**.
2. Confirm **Quiz complete** and inspect the result.
3. Select **Try again** for more practice or move to the next topic.
A topic quiz result is separate from a unit test, assignment pass requirement, or course completion. Check the lesson plan for any remaining work.
## Find unit tests and remaining work
Source: https://honen-academy.honen.com/docs/6ab361a1effafe59361d2418
Use the lesson plan to locate a unit test and see what still needs to be completed. A test is separate from a topic's practice quiz.
## 1. Find the test
1. Open a course topic.
2. Select the topic title or lesson-plan icon at the top.
3. Expand the unit.
4. Select its **Unit Test** entry.
## 2. Work through the test
1. Read the current question and select an answer.
2. Follow any confidence or other response prompts shown by the test.
3. Use the question navigation to review progress and find unanswered items.
4. Complete the required responses before using **Submit test**.
After submitting, review the result and any feedback the test provides. Return to the lesson plan to see the work remaining in the course.
## 3. Check remaining requirements
1. Reopen the lesson plan.
2. Inspect **Finish the course**.
3. If it is locked, read the listed remaining activities and return to those sections.
4. Complete the required work, then return to the finish action.
Course completion, assignment criteria, and curriculum certificates are different outcomes. A passing practice quiz does not by itself prove all three are complete. A required test uses the higher of its authored passing score and the assignment minimum when both exist; if neither is set, the default is 80%. Optional tests do not gate completion. See [Assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) for the required-work settings.
## Study banks and spaced repetition
Source: https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718
Study banks collect a course’s flashcards and quiz questions for self-directed review. Use spaced repetition to schedule recall practice, or practice freely while preparing for a standardized test or revisiting course material.
## What the learner sees
The Study bank dashboard shows due work and unseen items. A scheduled flashcard review presents a question, reveals its answer when requested, and asks the learner to rate recall. Those ratings determine when that item returns.
## Why use it
Use a review routine to revisit course material while preparing for a standardized test or maintaining knowledge. Trying to recall before revealing the answer gives the learner a more useful check than rereading alone. Rate recall honestly and check performance on new questions; review counts do not establish mastery.
## Get started step by step
### 1. Open the learner's Study banks
1. Open a course and its lesson plan.
2. Select **Study banks**.
3. Read the dashboard's due-work and unseen-item counts.
4. Use **Learn new** if no items are due and there are unseen items.
The dashboard distinguishes cards you have rated from items not yet seen. **Nothing due today** can still appear alongside new material to learn.
### 2. Complete a scheduled review
1. Open **Flashcards** in **Spaced repetition** mode.
2. Try to recall the term's meaning before selecting **Show answer**.
3. Compare your answer with the definition.
4. Rate your recall with **Again**, **Hard**, **Good**, or **Easy**. Read the interval displayed on each button.
5. Continue to the next item. Return to the dashboard to inspect the updated review activity.
After you rate a card, Honen moves to the next item and schedules future practice using your recall rating. Your unit-test results remain available in the course.
### 3. Choose free practice when useful
Use **Practice with flashcards** or **Practice with quiz questions** from the dashboard to work through the material without scheduling or grading it. Use the mode picker to distinguish free practice from spaced repetition, and **List** to inspect the available items.
## Check the result
1. Reveal and rate a card. Confirm that the next card appears and inspect the interval displayed for your rating.
2. Return to the dashboard and check the updated review activity and new/due counts.
3. Use free practice and confirm that you are in the intended mode before reviewing.
4. Build a routine around available course materials. Check whether you can answer new questions without looking at the source; keep required course tests and projects in view.
## Course refreshers and follow-ups
[Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045) are configured separately through **Settings → Retention → Keep sharp**. They add refresher stops to the course and schedule later check-ins. Read that guide to configure reinforcement within the learning path.
## Sites and Distribution
Source: https://honen-academy.honen.com/docs/6ab35eedda8e0901468ca39f
Start with who needs the content. Share links and assignments serve people you manage in your workspace; a Site gives people outside that workspace a branded place to discover documentation and learning.
| Delivery route | Use it for |
| --- | --- |
| Course share link | Quickly give an internal colleague or learner access to one course, subject to the course and workspace sharing settings. |
| Assignment | Give named internal learners, students, or groups required or recommended coursework, with completion criteria and an optional due date. |
| Curriculum | Arrange several courses into a learning path with an optional certificate. Offer it to an internal group or feature it on a Site. |
| Catalog | Curate approved courses and paths for a defined audience. Use its access and review settings before showing it in the workspace or on a Site. |
| Site | Publish external-facing product documentation, a developer portal, or a customer or partner academy under your brand. Choose public or sign-in-restricted access. |
| LMS | Deliver Honen learning through a school or organization's existing learning platform. |
A course link can allow access outside the workspace if its sharing mode and workspace policy permit it. Use a Site when an external audience needs navigation, documentation, multiple courses, or its own branded entry point.
## 1. Prepare a catalog
1. Open **Organization → Publishing**.
2. Choose **New catalog**, or open an existing catalog you manage.
3. On **Overview**, enter **Catalog name** and **Description**.
4. Add a cover with **Upload image** or **Generate**. The UI recommends a 16:9 image and accepts PNG, JPEG, or WebP up to 5 MB.
5. Choose **Save changes** when ready.
## 2. Add learning content
1. Open the catalog's **Content** tab.
2. Use **Add curricula** for ordered learning paths.
3. Use **Add courses** for individual courses.
4. Review each item's status. An **In review** item includes **View request** so you can inspect the publication request.
5. Use **View catalog** to inspect the learner-facing collection when available.
Adding and removing courses follows the catalog's review process. Complete the required review to make the approved release available to its audience.
## 3. Review audience and publishing policy
Use **Access** to configure who can view the catalog. Use **Publishing** to review **Catalog available**, **Review required**, reviewers, and **Required approvals**. Reviewers approve changes; viewing access is configured separately.
Keep internal training in catalogs with the appropriate workspace access. Select only approved, external-facing catalogs and Knowledge Base folders for a customer or partner Site; catalog approval alone does not make internal material suitable for publication.
## 4. Choose the final delivery surface
For external documentation or an academy, follow [Publish an academy](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397), then [curate its courses, paths, and documentation](https://honen-academy.honen.com/docs/6ab38b463b82ff9f26dee8d9). For internal coursework with named recipients and completion criteria, follow [Assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d). If learners already work in another learning platform, start with [LMS Integrations](https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392).
## Tips for a smooth setup
If content is absent from a learner-facing catalog, inspect its publication status and audience before adding it again. A Site can display approved releases from selected catalogs, while the same workspace continues to manage authoring and learner administration.
## Design and navigate a Site
Source: https://honen-academy.honen.com/docs/6ab38b493b82ff9f26dee8e3
Create a consistent branded journey from the first academy page to the learner's course. Use the Default visual editor for templates and page blocks, or Custom mode for an assistant-built experience.
## Choose a starting layout
1. Open the Site and keep **Default** selected.
2. In the right-hand **Layout** tab, choose **Template**: **Courses & documentation**, **Academy**, **Knowledge Base**, or **Developer docs**.
3. Expand **Introduction** and write a clear heading and description.
4. Review the preview and choose **Save**.
Templates provide a starting arrangement. Your selected content and brand settings remain part of the Site.
## Arrange page blocks
1. In **Layout**, use **Add block** to choose the section you need.
2. Expand the new block and fill its fields.
3. Use **Move block up** and **Move block down** to arrange the page.
4. Use **Remove block** for a block you no longer need.
5. Save and review the complete page.
| Block | Use it for |
| --- | --- |
| Introduction | The page's opening message and next action. |
| Courses | Selected learning content. |
| Documentation | Entry points into the guide library. |
| API reference | A developer reference entry point. |
| Text or Callout | An explanation or emphasized instruction. |
| Cards | A set of related destinations. |
| Questions | Common questions and answers. |
| Code | A code example. |
| Steps | A sequence the visitor can follow. |
| Image | A visual with the accompanying fields offered by the editor. |
Use [Curate Site content](https://honen-academy.honen.com/docs/6ab38b463b82ff9f26dee8d9) to prepare the courses, paths, and documentation behind those blocks.
## Apply your brand
1. Open **Design → Branding** and upload the **Logo** and **Favicon**.
2. Under **Colors**, choose a palette: **Editorial**, **Clean**, **Bold**, **Academic**, **Warm**, **Midnight**, or **Custom**.
3. Adjust **Primary**, **Background**, **Text**, **Card**, and primary/secondary button text colors using the pickers or hex fields.
4. Expand **Typography** to choose heading and body fonts.
5. Expand **Layout** to choose corner radius and spacing.
6. Save and inspect headings, body text, cards, and buttons together.
For a consistent signed-in experience, enable **Theme dashboard and courses** under **Learning experience**. Set the light and dark palettes, or use **Copy brand palette** for the selected mode, then review the contrast checks. These settings apply when learners enter through the verified workspace or Site domain. Choose **Learner experience** from Pages to preview the result.
## Configure the top bar and navigation
1. In **Layout**, expand **Top bar & navigation**.
2. Choose whether to **Keep navigation visible**, show **Search**, show the **Name beside logo**, and display **Section tabs**.
3. Adjust the top bar height.
4. Add **Top links** with a label and destination, such as an internal `/docs` route or an HTTPS destination. Reorder or remove links as needed.
5. Enable the primary button, enter its label and destination, and choose its **Button placement**: top bar or top of the left sidebar.
6. Use **Choose section tabs** to curate section destinations and their order.
7. Save and follow each destination in the preview.
Use up to eight top links to keep the primary navigation focused. Match labels to the task visitors want to complete, such as “Learn,” “Guides,” or “API reference.”
## Tune spacing and page actions
1. Expand **Padding & spacing**.
2. Adjust side padding, top/bottom padding, space between sections, and navigation width. Use **Reset spacing** to return to the starting values.
3. Expand **Page actions** and choose the reader tools to offer: copy as Markdown, copy an LLM prompt, download Markdown, and copy the page link.
4. Review the page at a narrow and wide browser width. Spacing scales down for smaller screens.
## Add a standalone page
1. Return to **Pages** in the left sidebar.
2. Choose **Add page** and enter the page title in the prompt.
3. Open the new page from Pages. It receives its own page route and a top-navigation link.
4. Use the Site's **AI assistant** to describe the page content you want, naming the selected page and the desired visitor action.
5. Review the generated page, save the draft, and include it in your next publication.
To remove a standalone page, use its remove control in Pages and confirm the named page. Review navigation afterward. Built-in Home, Course page, Docs, and learner pages have their own content and configuration controls.
## Work in Custom mode
1. Save the current draft.
2. Choose **Custom**, read the mode description, and confirm the switch.
3. Describe the page structure, content, and interactions in the Site assistant. Use concrete instructions, for example: “Create a customer onboarding homepage with a welcome message, three learning steps, and links to our selected guides.”
4. Review the generated preview, then ask for focused refinements.
5. Save and publish after reviewing the complete visitor journey.
Default layout settings are retained for Default mode; brand and selected content are shared across modes. Review the mode switch and preview before publishing a change of presentation.
Continue with [API reference and visitor assistant](https://honen-academy.honen.com/docs/6ab38b363b82ff9f26dee8ac) or [access and onboarding](https://honen-academy.honen.com/docs/6ab38b5a3b82ff9f26dee901).
## Curate Site courses, paths, and documentation
Source: https://honen-academy.honen.com/docs/6ab38b463b82ff9f26dee8d9
Build an academy around what your audience should learn next. Combine a selected course collection, an ordered learning path, and a searchable documentation library in the same Site.
Start by [creating a Site](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397). The steps below use the **Default** editor.
## Add a course section
1. Open **Sites** and choose the Site.
2. Open **Content → Courses → Add section**.
3. Enter the **Title** and optional **Subtitle**.
4. Choose **Course row**, **Featured**, or **Trending**, then choose **Add section**.
5. In the section, choose **Add course**. Search and select the intended courses; selected results change to **Added**.
6. Close the picker and choose **Save**. Wait for **Draft saved**.
7. Include a **Courses** block in **Layout**, or choose a template that displays courses, to show the collection on the home page.
Use **Edit section** to change a section's title, supporting text, or layout. Use **Remove course** to remove an individual item, or **Delete section** to remove the section. Draft courses can be selected while preparing the Site; publish the courses before launching them to learners.
## Show approved catalog content
1. Open **Content → Catalogs**.
2. Select the catalog whose approved releases should appear.
3. Review the catalog's entries and their Site placement. Use the available section, visibility, featured, and ordering controls to arrange them.
4. Review the preview after each update. Catalog-source placement controls persist their changes as you edit.
The catalog continues to manage review and publication. Follow [Sites and Distribution](https://honen-academy.honen.com/docs/6ab35eedda8e0901468ca39f) to prepare the collection and its audience.
## Add a learning path
1. Open **Content → Learning paths**.
2. Choose **Add** and select the intended curriculum.
3. Review the selected path and course count. A certificate badge identifies a curriculum with a certificate.
4. Save the Site draft and review how the path appears to visitors.
Maintain course order, requirements, and certification in the [curriculum editor](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350). Use the remove action in the Site's learning-path list when a path should leave this academy.
## Connect documentation
1. Open **Content → Docs** and enable **Publish docs at /docs**.
2. Set the documentation title.
3. Choose **Add folder**, search for the source folder, choose **Add**, and close the picker.
4. Review the sidebar heading and save.
For more detailed selection, use the right-hand **Knowledge Base** tab:
1. Enable **Documentation** and set its title.
2. Search the Knowledge Base and select the publishable folders or documents for this audience.
3. For a folder, decide whether to **Include all descendants and future additions**, or curate individual descendants.
4. Use the exclusion controls to leave particular descendants out of the Site.
5. Under **Navigation order and labels**, move sources up or down and set a reader-friendly navigation label.
6. Save and review the documentation preview.
Selected Knowledge Base documents remain connected to their sources, so document edits can appear on the Site without a separate layout publication. Select content intended for the Site's audience, including future additions when you choose that option. Repository content can use the same flow after [GitHub sync](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc) imports it.
## Organize documentation categories
1. In **Layout**, expand **Documentation categories**.
2. Enter a **Category name** and choose **Add documentation category**.
3. Give the category a useful label and description.
4. Assign the selected folders, individual guides, or imported API specifications that belong together.
5. Reorder categories and remove unused ones. Review both the navigation and category overview.
Categories organize selected content; the Knowledge Base selection determines which documentation is available. The Site supports up to 24 categories. An API import creates its own category, which you can rename and position alongside the guides.
## Review the complete learning journey
Preview **Home**, **Docs**, **Course page**, and **Learner experience**. Check that a first-time visitor can find the starting course, open its supporting guide, and continue to the learning path. Then [configure access and onboarding](https://honen-academy.honen.com/docs/6ab38b5a3b82ff9f26dee901) and [publish the academy](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397#7-publish-and-verify).
## Manage Site access, onboarding, and lifecycle
Source: https://honen-academy.honen.com/docs/6ab38b5a3b82ff9f26dee901
Choose how visitors discover your academy, how learners sign in, and who can maintain the Site. Keep those choices aligned with the audience for the selected courses and documentation.
## Set visibility and sign-in
1. Open the Site's **Settings**.
2. Choose **Visibility**: **Public**, **Unlisted**, or **Auth required**.
3. Choose whether search engines may index the Site.
4. Use **Public only** for an open documentation destination, or configure sign-in for a learning program.
5. Enable **Require sign-in to take courses** when learners should authenticate before entering courses.
6. Save your settings and review the experience as the intended visitor.
An unlisted address can still be shared with someone who has the link. Use authentication when the audience should sign in. Public-only mode removes account-dependent onboarding options.
## Set up custom onboarding
1. In **Settings**, enable custom onboarding for a Site that supports sign-in.
2. Save, then open **Onboarding** from Pages.
3. Use the Site assistant to describe the questions and welcome flow, such as the learner's role, product experience, and learning goal.
4. Review the onboarding preview and refine the flow before publishing.
5. Choose whether **Show onboarding data in People** should expose submitted answers to authorized Site managers.
6. Publish when the welcome flow and access settings are ready for new learners.
Onboarding helps a new learner enter the program with the right context. Signing in through the Site places new external learners in the Site's external learner group and gives them the learning access associated with that Site. Internal workspace members retain their existing workspace membership.
## Review onboarding responses
1. Open the Site editor and select **Onboarding**.
2. Open **Data** when the Site's onboarding database is available.
3. Choose a database and table to browse collected responses.
4. Use the read-only query editor when you need a more focused view of the stored data.
5. Review the associated member information in People when that option is enabled and your role permits it.
Keep response access with the people managing the program. Ask only the questions needed to support the learner's experience.
## Share Site editing responsibilities
1. Open **Share** as a Site publisher or manager.
2. Search for a person already in the workspace.
3. Choose **Can edit** for drafting, or **Can edit and publish** for someone who should release changes.
4. Choose **Share** and review the editor list.
5. Remove a person's Site-specific grant when their responsibility ends.
People with workspace-wide Sites permissions retain that access. Sharing a Site's editor is separate from configuring its visitor audience.
## Prepare search and social previews
1. In **Settings**, open the SEO and sharing controls.
2. Enter the **Page title** and **Description**. The editor allows up to 70 and 200 characters respectively.
3. Upload a social sharing image. Use the recommended 1200 × 630 format and keep the file within the displayed 5 MB limit.
4. Save, then review the Site's title, description, and sharing appearance at its published address.
Use a specific title and description that explain who the academy serves and what visitors can achieve.
## Manage addresses and embedding
Use **Settings → Address** for the included Honen subdomain and custom hostnames. Follow [Connect your custom domain](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397#connect-your-custom-domain) for DNS provisioning, or [Mount under an existing website](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397#6-mount-under-an-existing-website) for a path such as `/docs`.
Add intended website origins to **Allowed embedding origins** when mounting or embedding the Site. Review nested links, documentation images, sign-in, and assistant behavior from the final address.
## Save, publish, and maintain the Site
1. Use **Save** to preserve the draft and **Publish** to release it.
2. Use **Reset** when you want to discard unsaved editor changes and return to the saved version.
3. In **Settings → General**, maintain the Site name and slug. A slug uses lowercase letters, numbers, and hyphens; changing it also affects the included address and may require provisioning.
4. Use **Archive site** in the advanced settings when the Site should go offline.
5. Use **Delete site** only when you intend permanent removal; review the confirmation before completing it.
Review the public home page, a nested guide, search, course entry, and the expected authentication flow after each release. See [Publish an academy](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397) for the full launch sequence.
## Add an API reference and visitor assistant
Source: https://honen-academy.honen.com/docs/6ab38b363b82ff9f26dee8ac
Put developer reference material and guided answers beside your academy documentation. Import an OpenAPI specification for a browsable reference, then connect an Agent to help visitors find answers from the knowledge you select.
## Import an API specification
1. Open the Site in **Default** mode.
2. Select the right-hand **API** tab.
3. Choose **Upload specification** for a JSON or YAML file smaller than 2 MB, or enter an **OpenAPI specification URL** and choose **Import**.
4. Review the imported specification title and its new documentation category.
5. Edit **Category name** to use a clear navigation label.
6. Choose **Choose endpoints** and select the operations to include. Operations are grouped by tag and labeled with their HTTP method and path.
7. Choose **Preview category** to inspect the reference, then save the Site draft.
A Site supports up to ten specifications. Use **Layout → Documentation categories** to arrange their categories beside your how-to guides. Use **Remove API specification** to remove a reference from the Site configuration, then save your changes.
Keep the specification's descriptions, parameters, schemas, and examples current at the source. When replacing a reference, import the intended specification and review its selected endpoints before publishing. For Honen's own API and authentication guidance, see [API and OpenAPI](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e).
## Connect a visitor assistant
1. Open the right-hand **Assistant** tab.
2. Under **Attach an existing agent**, select an active public website embed, or choose **Set up an existing agent** to prepare one in Agents.
3. If you are creating a new assistant and have the required permissions, choose **Create an agent**, enter its name, and complete the creation flow.
4. Use **Manage knowledge & behavior** to configure the Agent's selected knowledge, instructions, and allowed origins.
5. Enable **Show assistant on this site**.
An existing Agent keeps its knowledge, permissions, and allowed origins. Select sources suitable for the Site's audience and include the Site's intended origin in the embed setup. See [Embedding on your own site](https://honen-academy.honen.com/docs/6ab35edbda8e0901468ca336#embedding-on-your-own-site) for the complete Agent configuration.
## Choose where visitors can ask
1. Set **Button & page name**, such as “Ask Northstar.”
2. In **Show the sidebar on**, choose **Overview and documentation** or **Every page**.
3. Decide whether to **Open the sidebar by default**.
4. Choose **Citation links → Site pages** to send readers to published pages on this Site, or **Internal Knowledge Base** for an audience with permission to open the original records.
5. Enable **Include a full-page chat** if the academy should also offer a dedicated `/assistant` page.
6. Choose whether to **Show full-page chat header**, then use **Preview assistant page**.
7. Save and include these settings in the next Site publication.
Select the source pages in the Site as well as the Agent when you want citations to open publicly readable documentation. Internal Knowledge Base links require the visitor's source permissions.
## Review the visitor experience
1. Ask a question answered by a selected guide.
2. Follow its citation and confirm it opens the intended published page.
3. Ask a follow-up to confirm the answer uses the right product context.
4. Check the sidebar and full-page chat at desktop and mobile widths.
5. Revisit **Manage knowledge & behavior** when changing the assistant's audience or source collection.
Continue with [Site design and navigation](https://honen-academy.honen.com/docs/6ab38b493b82ff9f26dee8e3) and [publishing the academy](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397).
## Publish an academy
Source: https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397
Give people outside your workspace one branded place to find answers and build skills. Use a Site for product or developer documentation, customer education, partner enablement, or another external academy. A Site brings selected courses, learning paths, and Knowledge Base documentation together. For internal team training, use workspace sharing and [assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d). The examples use **Northstar Product Academy · Demo**.
Use the focused guides as you build:
- [Curate courses, paths, and documentation](https://honen-academy.honen.com/docs/6ab38b463b82ff9f26dee8d9).
- [Design pages, branding, and navigation](https://honen-academy.honen.com/docs/6ab38b493b82ff9f26dee8e3).
- [Add API reference and visitor assistance](https://honen-academy.honen.com/docs/6ab38b363b82ff9f26dee8ac).
- [Manage access, onboarding, and the Site lifecycle](https://honen-academy.honen.com/docs/6ab38b5a3b82ff9f26dee901).
## 1. Create the Site
1. Open **Organization → Sites**.
2. Choose **New site**.
3. Enter the site name and choose **Create**.
4. Confirm the editor opens with your site name and included Honen subdomain.
Sites must be enabled for your workspace. Your Honen administrator or account team can help with access.
## 2. Choose a layout
1. Keep **Default** selected for the visual editor.
2. In the right-hand **Layout** tab, choose a **Template**. The choices include **Courses & documentation**, **Academy**, **Knowledge Base**, and **Developer docs**.
3. Expand **Introduction** and enter the heading and description.
4. Choose **Save** and wait for **Draft saved**.
The preview updates while you edit. **Save** preserves the draft; **Publish** controls the public release.
## 3. Add Knowledge Base documentation
1. Open **Content** on the left.
2. Expand **Docs**.
3. Enable **Publish docs at /docs**.
4. Choose **Add folder** and search for the intended Knowledge Base folder.
5. Choose **Add** beside the folder, then close the picker.
6. Review its sidebar heading and the preview; choose **Save**.
Only select content intended for the site's audience. The UI notes that document edits go live immediately; a content update is different from a layout draft. GitHub-synced folders can serve as the same source once imported into the Knowledge Base.
## 4. Add learning content
In **Content**, select catalogs to show their approved releases. Use **Courses → Add section** to curate course sections. Expand **Learning paths** for curricula. For a documentation-only site, those sections can remain unused.
## 5. Review access and address
1. Open **Settings**.
2. Review **Visibility**: **Public**, **Unlisted**, or **Auth required**.
3. Decide whether search engines may index the site.
4. Choose **Public only** for open documentation with no account flow, or **Require sign-in to take courses** for a learning experience that needs accounts.
5. Save the settings you intend to apply.
Under **Address**, inspect the included subdomain. For a custom hostname, enter a domain you control, choose **Add domain**, and complete the displayed DNS instructions. Wait for provisioning to finish before relying on the hostname.
### Connect your custom domain
1. In **Settings → Address**, enter the hostname you control and choose **Add domain**.
2. Copy the displayed DNS record type, name, and value into your DNS provider. Use the values shown for this hostname.
3. Return to the domain row and choose **Re-check status** to update its provisioning status.
4. When the status is **Active**, open the HTTPS address and check the homepage and a nested page. The included Honen address remains available while your custom domain provisions.
A custom hostname such as `academy.example.com` and a path such as `example.com/docs` use different routing. Use the mount setup below for a path on an existing website.
## 6. Mount under an existing website
A path such as `example.com/docs` requires the existing website to proxy that path to the Site. In the Site's **Mount path on another site**, set the matching prefix such as `/docs`. Keep that prefix in the visitor's browser URL; configure the forwarding rule to strip the prefix before requesting the Site. For example, `/docs/getting-started` on the original website should request `/getting-started` from the Site.
Configure the forwarding rule with the website owner, add the original website's origin to **Allowed embedding origins**, and test nested document links and images.
## 7. Publish and verify
After saving and reviewing the draft, choose **Publish**. Open the public address and verify the home page, a nested documentation page, images, search, and the expected sign-in behavior as an ordinary visitor.
## 8. Welcome learners into a program
1. Publish the courses and [curriculum](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350) for your audience, then include them in the Site’s selected catalogs or learning paths.
2. For a customer or partner program, choose the sign-in experience that lets visitors take courses and retain their progress. Use **Public only** for open documentation.
3. Open the academy as a new visitor, find a course or learning path, and follow its start action and sign-in prompts.
4. New learners signing in through the Site join its external learner group and receive access to the learning content available through that Site. Existing internal workspace members keep their workspace membership.
5. Manage named cohorts and their required work with [assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) when they need a due date and completion requirements. The Site remains the external place to browse and enter the program.
6. Follow activity in [Analytics and Reporting](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e). Learners who meet a certificate-enabled curriculum’s requirements can [download and share their credential](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350#5-earn-verify-and-share-a-certificate).
Use this sequence for customer onboarding, partner enablement, or a sponsored learning program: focused content, a branded entry point, a clear learning path, and reporting for the intended cohort.
For repository-backed content, follow [GitHub sync](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc). Review [access and roles](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353) and [catalog distribution](https://honen-academy.honen.com/docs/6ab35eedda8e0901468ca39f) before choosing the public audience.
## Assignments
Source: https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d
Use assignments to give named learners, students, or groups in your workspace a clear next step. Choose a course or selected lessons, set completion requirements, and add a due date or welcome message. For external documentation or a customer or partner academy, use a [Site](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397).
## 1. Choose the course
1. Open **Assignments → New assignment**. You can also open the course’s manage screen and choose **Assign**.
2. Add an optional **Name**, such as **Product onboarding practice**.
3. Search under **Course**, or use **Browse catalog**.
4. Select the intended course by its title and cover. The selected course appears as a chip.
Search may return other courses you can access. Confirm the exact title before selecting it.
## 2. Choose all or part of the course
1. Under **What to assign**, keep **Whole course** for the complete course.
2. To narrow the work, choose **Part of course**.
3. Expand the unit with its disclosure arrow.
4. Select the unit, individual lessons, or test you intend to require.
5. Confirm the selected-item count.
Select the lessons and tests that support the assignment’s goal, then set the activity and score requirements below.
## 3. Choose recipients and timing
1. Search **Assign to** for a group or person.
2. Expand a group to inspect its members, or collapse it for a concise review.
3. Select only the intended recipients. Selecting the workspace applies broadly.
4. Set an optional **Due date**.
Without a due date, the interface describes the work as a standing recommendation with no overdue flag. Invited people receive access after accepting their invitation; the due date stays as configured.
## 4. Set completion requirements
1. Set **Activities per topic** to a number, or choose **All**.
2. Set a **Minimum quiz score** if needed; a blank value counts any completion.
3. Decide whether **Unit tests required** should apply and set the **Minimum test score**.
4. Decide whether **Projects required** should apply.
5. Optionally enable **Custom retention** to override this content's check-in schedule for the assignment.
Review the selected requirements together so learners have a clear definition of completion.
## 5. Review and send
Add an optional **Message**, review the content and recipient selection, then choose **Assign** when ready. The form states that the message is sent once to everyone receiving the assignment.
Return to **Assignments** to inspect course, recipients, completion, due date, and assigned-by details. Use the course, recipient, and status filters to narrow the list. Learners find their work under **My Assignments**.
## Tips for a smooth setup
- **Complete the selection:** choose content and at least one recipient. A partial assignment also needs at least one selected item.
- **Confirm the course:** check its title and cover; use the chip's remove control to change it.
- **Compare completion fairly:** review each learner's assignments and requirements alongside their progress.
Prepare recipients with [People, Groups and Workspaces](https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca360), then inspect results in [Analytics and Reporting](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e). For a path spanning several courses, use [Curricula and certificates](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350).
## Build a learning path and certificate
Source: https://honen-academy.honen.com/docs/6ab36166effafe59361d2350
A curriculum orders several courses into a learning path and can issue a certificate on completion. Prepare the curriculum as a hidden draft before making it available to learners.
## 1. Create the curriculum
1. Open **Organization → Manage Curricula**.
2. Choose **New curriculum**.
3. Enter **Title**, **Slug**, and **Description**.
4. Explain **Why this curriculum** and enter **Learning outcomes**, one per line.
5. Add a cover with **Generate** or **Upload** if needed.
The slug is the readable identifier used for the learning path. Use a stable, descriptive value.
## 2. Add and order courses
1. Scroll to **Add existing courses**.
2. Search for the intended course.
3. Choose its exact title and cover.
4. Use **Move up** and **Move down** beside selected courses to set the order.
5. Remove an accidental selection with **Remove course**.
Use **Planned courses → Add a planned course** when you want to sketch the structure before building every course. An existing course can be attached while the curriculum remains a draft.
## 3. Configure the certificate
1. Enable **Certificate**.
2. Set **Certificate name** and **Certificate description**.
3. Review **Require all courses**. When on, every attached course must be completed; when off, completing any one attached course can satisfy this rule.
4. Choose **Classic**, **Modern**, or **Minimal** for the design.
5. Set workspace name, accent color, logo, signatory name/title, optional signature image, and body text.
6. Inspect the preview before saving.
The preview uses sample details so you can check the design. **Share publicly** controls the curriculum landing page; issued certificates have their own public verification link.
## 4. Save and deliver
1. Leave **Published** off to keep the curriculum a **Hidden draft**.
2. Leave **Share publicly** off unless you intend to expose the curriculum's public landing page.
3. Choose **Save**.
4. Confirm the curriculum card shows its title and course count.
5. Once approved for delivery, publish it and add it through a group's **Curricula → Add curricula** or a Site's **Learning paths** controls.
Use a hidden draft to prepare the learning path, then publish it when its courses and certificate design are ready.
## 5. Earn, verify, and share a certificate
Learners earn a curriculum certificate by meeting its configured course-completion and grade requirements. Certificate viewing and sharing require the workspace’s certifications feature.
1. Open the learning path and complete its required courses. Follow the progress shown on the curriculum page.
2. Once the certificate is issued, choose **View certificate**, or open **Achievements → Certificates**.
3. Review the curriculum name, issue date, grade, and **Certificate No.**
4. Choose **Download PDF** to keep a copy, or **Verify** to open the public verification page.
5. Use **Add to LinkedIn** to open LinkedIn’s certification form with the credential name, issue date, verification link, and certificate number filled in. Review it there before saving.
6. Share the verification page when someone needs to confirm the credential and its current status.
The certificate design preview helps you prepare the appearance. Issued certificates carry the actual learner details and verification number. Verification links are public to anyone who has the link.
## Tips for a smooth setup
Publish the saved curriculum before adding it to a group. When course search returns similar titles, use the cover and exact name to select the intended course.
Next, link the published path to [a group](https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca360), include it in [a catalog](https://honen-academy.honen.com/docs/6ab35eedda8e0901468ca39f), or add it to [an academy](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397). Use [Assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) for a course with explicit recipients and completion criteria.
## LMS Integrations
Source: https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392
Bring Honen learning into the LMS your organization already uses. Select your platform to see its connection guide, then choose the launch and reporting options that fit your program.
## 1. Choose your LMS
1. Open **Organization → Integrations**.
2. Select **Your LMS**.
3. Choose your platform. Canvas, Moodle, Blackboard, Brightspace, and Skilljar use the LTI path. Canvas and Moodle have their own guides; Blackboard and Brightspace open the generic LTI 1.3 setup. Skilljar uses manual, launch-only setup without Deep Linking, roster sync, or grade passback.
4. For a package-based platform such as Cornerstone, Docebo, SAP SuccessFactors, Workday Learning, or TalentLMS, choose its SCORM card.
5. If your platform is absent, use **Another LMS with LTI 1.3**, **My LMS supports xAPI or cmi5**, or **Any other LMS (SCORM)**.
## 2. Review SCORM defaults
1. Select a SCORM platform to open **Packages for your LMS**.
2. Review whether SCORM is enabled for the workspace.
3. Read **SCORM tenants**: each tenant isolates its launch session on a subdomain; a group can be bound for enrollment.
4. Under **Export defaults**, review the learner audience, SCORM version, completion policy, pass/fail status, and score reported to the LMS.
5. Review **Report time spent** and **Save resume position**.
Defaults prefill the course export dialog; each package can still be customized at download time. The page directs you to a course's manage screen and **Export → SCORM package** to create a package. Upload the resulting package through your LMS's package-import workflow, then test with a learner account.
A SCORM package loads the live course. Detailed learning analytics remain in Honen; completion and scores are reported through the LMS package. Disabling exports also blocks SCORM launches across the workspace, so treat it as an operational setting.
## 3. Prepare an LTI 1.3 connection
1. Return to **Your LMS** and choose the LTI platform.
2. Review the platform's displayed capabilities.
3. Under **LTI app branding**, choose the app name and logo learners should see.
4. Follow the platform-specific **Integration guide** displayed on the page.
5. Review **How learners open Honen** and **What learners land on** before connecting.
For Canvas, the displayed guide directs administrators to **Admin → Developer Keys → + Developer Key → + LTI Registration**, followed by the registration URL, enablement, and deployment availability. Use **Manual setup** if that registration option is unavailable. Keep the generated registration URL within the administrator setup process.
### Connect Canvas
Have a Canvas account administrator and a Honen workspace administrator complete these steps together.
1. In **Your LMS**, select **Canvas** and copy the **Dynamic registration URL**.
2. In Canvas, open **Admin → Developer Keys → + Developer Key → + LTI Registration**.
3. Paste the registration URL, choose **Continue**, review the registration, and enable it.
4. Open **Settings → Apps → Manage → Honen** and its installed deployment. Change availability from **Not Available** to **Available**, then save.
5. In a Canvas course, add Honen from an assignment or module and select the course or graded assignment to attach.
6. If you want Honen only inside courses, turn off **Global Navigation** in the Canvas app configuration.
If Canvas does not offer **LTI Registration**, use Honen’s **Manual setup** instructions with an LTI Key. The [LTI guide](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9) explains launch, roster, and grade services.
## 4. Validate with a test launch
After your LMS administrator completes registration or package import, launch the content as a learner, complete a sample activity, and check the intended score/completion result in the LMS. Test the embedded and new-tab behaviors required by your environment.
## Detailed guides
- [Connect Canvas](https://honen-academy.honen.com/docs/6ab38b403b82ff9f26dee8c8)
- [Connect Moodle](https://honen-academy.honen.com/docs/6ab38b393b82ff9f26dee8b5)
- [Register Skilljar, Blackboard, Brightspace, or another LMS manually](https://honen-academy.honen.com/docs/6ab38b423b82ff9f26dee8d0)
- [SCORM export and validation](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7)
- [LTI 1.3 registration and testing](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9)
- [xAPI and cmi5](https://honen-academy.honen.com/docs/6ab3767378ce9f1718279699)
- [Google Classroom](https://honen-academy.honen.com/docs/6ab3767578ce9f17182796a2)
## Tips for a smooth setup
Use LTI 1.3 setup instructions rather than a legacy XML/LTI 2 installation flow. For iframe or cookie restrictions, review the displayed **Open in new tab** option. Check the package's chosen score policy before expecting a numeric score in the LMS.
## Connect an LMS with LTI 1.3
Source: https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9
Use LTI 1.3 when your LMS supports a registered external learning tool. Honen supports launches, Deep Linking, Assignment and Grade Services (AGS), and Names and Role Provisioning Services (NRPS). The LMS must enable the services your workflow needs.
## 1. Choose the platform
1. Open **Organization → Integrations → Your LMS**.
2. Select Canvas, Moodle, Blackboard, Brightspace, Skilljar, or **Another LMS with LTI 1.3**.
3. Read the displayed integration guide. Canvas and Moodle have platform-specific paths; Blackboard and Brightspace use **Other LTI 1.3**. Skilljar is manual and launch-only: its setup does not offer Deep Linking, AGS grades, or NRPS roster sync.
4. Set the app branding and review how learners open Honen and what they land on.
Follow the dedicated guides for [Canvas](https://honen-academy.honen.com/docs/6ab38b403b82ff9f26dee8c8), [Moodle](https://honen-academy.honen.com/docs/6ab38b393b82ff9f26dee8b5), or [manual registration for Skilljar, Blackboard, Brightspace, and other LTI platforms](https://honen-academy.honen.com/docs/6ab38b423b82ff9f26dee8d0).
## 2. Register the tool
Use dynamic registration where the LMS supports it. Copy the setup URL from Honen into the LMS administrator's registration flow. Keep the generated setup token private.
For manual registration, use the values shown by the setup screen. The standard endpoints are:
| Setting | URL |
| --- | --- |
| Login initiation | `https://honen.com/api/lti/login` |
| Launch and redirect URI | `https://honen.com/api/lti/launch` |
| Tool public keys | `https://honen.com/api/lti/jwks` |
Complete the LMS's enablement and deployment steps and enter its required issuer, client, and deployment information in the connection. Register the tool using LTI 1.3.
## 3. Place content and test
1. For a connection with Deep Linking enabled, open the LMS's external-tool content picker as an instructor.
2. Select the Honen content to place in the course. For a launch-only connection such as Skilljar, configure the tool placement using its manual setup guide instead.
3. Launch the placement as a test learner and verify the intended course or assignment opens.
4. If using NRPS, sync the LMS context roster and check the mapped Honen group.
5. If using AGS, complete a sample requirement and verify the expected grade in the LMS.
Enable and review roster sync and grade services separately, then check the instructor and learner experiences.
## 4. Choose the learner launch and landing page
Under **How learners open Honen**, choose:
- **Embedded:** open the learning experience inside the LMS window.
- **Open in new tab:** open a full browser tab from the LMS.
- **Always show button:** give the learner an **Open in Honen** handoff.
Under **What learners land on**, choose **Honen hub** for a class launcher or **Straight to content** for the linked content. For the hub experience, also choose **Open in place** or **Open in new tab** for course navigation.
Choose these options before copying the dynamic registration URL. On a saved connection, use **Edit settings** and **Save settings**.
## 5. Set the grade policy
Open **Advanced options → Grade passback default** for a platform with AGS. Choose a policy that matches the result your program needs to report:
| Policy | Reported result |
| --- | --- |
| **Completion** | 100% when the assignment is complete |
| **Progress %** | Milestones: 0% before starting, 50% after starting, and 100% on completion |
| **Pass/fail** | 1 when complete; 0 before completion |
Use **Completion** for completion credit or **Pass/fail** for a binary completion result. Use a **graded assignment** returned through Deep Linking for gradebook reporting. A plain course link is a navigation entry point.
## 6. Map roles and review the class group
Under **Role mapping**, review both the **Workspace** and **Group** role for each incoming LMS role. Defaults map Administrator to Admin, Instructor/TeachingAssistant/ContentDeveloper to Instructor, and Learner/Member to Member. Select the appropriate workspace or group role when your governance model needs a different mapping.
The LMS class context maps to a Honen group. When using NRPS, inspect the synced class membership as well as a fresh learner launch. [Create and manage groups](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860) explains the group tools used after provisioning.
## 7. Manage an existing connection
1. Find the platform under **Your LMS connections**.
2. Inspect the issuer, client ID, mapped group/link counts, launch mode, and passback policy.
3. Open **Edit settings**, make the intended change, and choose **Save settings**.
4. Review the secure launch-domain status. Use **Re-check** when checking provisioning progress.
5. Test the affected instructor and learner journeys.
Use the connection switch to manage its enabled state. Plan a replacement route for live learner placements before choosing **Disconnect**. Branding saved for a new Honen registration should be coordinated with the installed app's branding in the LMS.
## Check your setup
Check the exact issuer, client ID, deployment ID, redirect URI, and keys against the LMS registration. Review the selected grade policy and available LMS scopes when grades do not appear. Use the displayed new-tab option where the embedded experience cannot establish a session.
Work with your LMS administrator to complete registration and a learner launch. For platform-specific setup, follow [Connect Canvas](https://honen-academy.honen.com/docs/6ab38b403b82ff9f26dee8c8) or [Connect Moodle](https://honen-academy.honen.com/docs/6ab38b393b82ff9f26dee8b5).
If the LMS accepts packages instead of an external-tool registration, use [SCORM](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7) or [cmi5](https://honen-academy.honen.com/docs/6ab3767378ce9f1718279699). Google Classroom uses its own [add-on workflow](https://honen-academy.honen.com/docs/6ab3767578ce9f17182796a2).
## Connect Canvas to Honen
Source: https://honen-academy.honen.com/docs/6ab38b403b82ff9f26dee8c8
Bring Honen courses and graded assignments into Canvas through LTI 1.3. Have a Canvas account administrator and a Honen workspace administrator complete the registration together.
## 1. Prepare the Honen connection
1. In the intended team workspace, open **Organization → Integrations → Your LMS → Canvas**.
2. Under **LTI app branding**, choose the app name and logo for the new installation. Choose **Save branding** after a change.
3. Choose **How learners open Honen**: **Embedded**, **Open in new tab**, or **Always show button**.
4. Choose **What learners land on**: the **Honen hub** or **Straight to content**. For the hub, choose whether courses open in place or a new tab.
5. Open **Advanced options** to review the grade policy and role mappings.
6. Copy the **Dynamic registration URL** after selecting the intended options.
Keep the registration URL within your administrator setup process. For the available options and their effects, see [LTI settings and reporting](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9).
## 2. Register in Canvas
1. Open **Admin → Developer Keys → + Developer Key → + LTI Registration**.
2. Paste Honen's registration URL and select **Continue**.
3. Review the registration and enable it.
4. Open **Settings → Apps → Manage → Honen** and the installed deployment.
5. Change availability from **Not Available** to **Available** and save.
6. Return to Honen and confirm the connection appears under **Your LMS connections**.
For Canvas installations using a manually configured LTI Key, follow [Manual LTI registration](https://honen-academy.honen.com/docs/6ab38b423b82ff9f26dee8d0) with the values supplied by Canvas.
## 3. Place learning inside a course
1. As an instructor, open the intended Canvas course.
2. From an assignment or module, add the Honen external tool.
3. In Honen's content picker, choose the course or graded assignment.
4. Complete the placement in Canvas.
5. For gradebook reporting, use a **graded assignment** placement and confirm its points and selected passback policy.
A course placement gives learners an entry point; a graded assignment placement adds the assessment/reporting relationship. Choose the one that matches your teaching goal.
## 4. Verify the learner experience
Launch the placement with a test learner. Confirm the correct course and class context, complete the selected requirement, and inspect the Canvas gradebook when using a graded placement. If roster sync is part of your rollout, check the mapped Honen group and its members too.
Repeat the launch with an instructor to verify the class-management experience and role mapping. Use [group management](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860) and [LTI settings](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9) to review the Honen side.
## Manage the installation
Use **Your LMS connections → Edit settings** in Honen to change launch behavior, landing experience, role mappings, or grade defaults. Select **Save settings**, then test the affected flow.
To keep Honen inside Canvas courses only, use **Admin → Apps → Honen → Configuration → Edit** in Canvas and turn off **Global Navigation**. Manage the installed app's displayed name and logo in Canvas when updating an existing deployment.
Return to [LMS Integrations](https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392) to compare delivery options, or use [LTI Advantage](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9) to review registration, learner launch, and grade reporting.
## Connect Moodle to Honen
Source: https://honen-academy.honen.com/docs/6ab38b393b82ff9f26dee8b5
Add Honen as an LTI Advantage external tool so instructors can choose courses and graded assignments from Moodle. Use Moodle 3.10 or later with the LTI Advantage services needed for your rollout enabled.
You need a Moodle site administrator and a Honen administrator with permission to manage integrations.
## 1. Configure the Honen launch
1. Open **Organization → Integrations → Your LMS → Moodle**.
2. Review **LTI app branding**, save any name/logo change, and choose the learner launch and landing options.
3. Open **Advanced options**. Choose the default grade policy and confirm workspace/group role mappings.
4. Copy the **Dynamic registration URL** with those options selected.
Use [LTI settings and reporting](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9) to choose between embedded, new-tab, and hub experiences.
## 2. Register in Moodle
1. Open **Site administration → Plugins → External tool → Manage tools**.
2. Paste the Honen registration URL into **Tool URL**.
3. Choose **Add LTI Advantage**.
4. Activate Honen and review the tool's enabled services.
5. Return to Honen and confirm the connection in **Your LMS connections**.
For a manually managed registration, use [Manual LTI registration](https://honen-academy.honen.com/docs/6ab38b423b82ff9f26dee8d0) and the platform values from Moodle.
## 3. Add content to a Moodle course
1. Open the intended Moodle course as an instructor.
2. Add an **External tool** activity and select Honen.
3. Use **Deep Linking** to choose a course or graded assignment in Honen.
4. Save the activity in Moodle.
5. For a graded assignment, confirm the Moodle grade settings and the Honen passback policy.
## 4. Verify launch, roster, and grades
Open the activity as a test learner. Confirm the intended content and class context, then complete the selected requirement. Inspect the grade in Moodle when using a graded assignment and AGS. If using NRPS roster sync, check the corresponding Honen group and learner membership.
Also launch as an instructor so you can check the management experience. Test the actual browser and embedded/new-tab mode your learners will use.
## Keep the connection aligned
In Honen, open the saved connection's **Edit settings** to review its launch, landing, grade, and role choices. Choose **Save settings** and test any change before wider rollout. Use the displayed secure launch-domain status and **Re-check** when provisioning needs another check.
Continue with [LTI 1.3 settings](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9), [Groups](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860), or [SCORM export](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7) for a package delivery path.
## Register an LMS manually with LTI 1.3
Source: https://honen-academy.honen.com/docs/6ab38b423b82ff9f26dee8d0
Use manual registration when your LMS asks you to exchange platform and tool settings directly. This guide covers the Honen fields shared by compatible LTI 1.3 platforms, including the generic setup used for Blackboard and D2L Brightspace, and Skilljar's lesson-launch setup.
## 1. Select the platform
1. Open **Organization → Integrations → Your LMS**.
2. Select **Blackboard**, **D2L Brightspace**, **Another LMS with LTI 1.3**, or **Skilljar** as appropriate.
3. For Blackboard, Brightspace, or another general LTI platform, use **Manual setup** when you are configuring the connection by hand.
4. Review **LTI app branding** and the launch and landing options before registering the tool.
## 2. Copy Honen's tool settings into the LMS
Use the exact URLs in the Honen **Manual LMS fields** panel:
| LMS tool setting | Honen value on the production host |
| --- | --- |
| Login / OIDC initiation URL | `https://honen.com/api/lti/login` |
| Launch / redirect URL | `https://honen.com/api/lti/launch` |
| JWKS / public keyset URL | `https://honen.com/api/lti/jwks` |
| Redirect URI | `https://honen.com/api/lti/launch` |
Create an LTI 1.3 tool/deployment in the LMS using its administrator workflow. Enable the services you intend to use, then obtain the platform values for the next step.
## 3. Enter the LMS values in Honen
| Honen field | Supply from your LMS |
| --- | --- |
| **Platform ID** | The platform issuer identifier |
| **LTI client ID** | The registered application's client identifier |
| **Deployment ID** | The installed deployment identifier |
| **Authentication login URL** | The platform authorization endpoint |
| **Authentication token URL** | The service-token endpoint |
| **JWKS URL** | The platform's public keyset endpoint |
Choose **Save manual configuration**. Confirm the new entry in **Your LMS connections**, then use **Edit settings** when updating the learner experience.
## Blackboard and D2L Brightspace
Use the **LTI 1.3** setup shown by Honen for these platforms. Complete the tool registration, deployment, and placement in the LMS administration area. Enable Deep Linking for the instructor content picker, AGS for graded assignment passback, and NRPS for roster synchronization when those services are part of your deployment.
Create an instructor placement, select the intended Honen content, and test with both an instructor and learner. Confirm the LMS gradebook and mapped Honen group for the services you enabled.
## Skilljar
1. In Skilljar, create an **LTI 1.3 lesson** under **Course Management**.
2. Copy Honen's manual tool values into Skilljar, then enter the supplied platform values back in Honen.
3. Choose a full-browser-window launch. Honen's **Always show button** option provides the **Open in Honen** handoff.
4. Save the configuration and add the lesson to the intended course.
5. Launch it with a test learner and confirm the intended Honen destination.
The Skilljar workflow is a lesson launch. Use the [SCORM guide](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7) when your delivery plan calls for package-based completion and score reporting, and confirm the chosen standard with your LMS administrator.
## Validate and maintain
Check the exact issuer, client, deployment, and URLs on both sides. For graded placements, inspect the selected [grade passback policy](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9) and the grade produced by a test completion. Test roster sync separately when enabled.
Use **Edit settings → Save settings** for supported connection changes. Review a planned disconnect with the course owner so live learner placements have a replacement route.
## Deliver through Google Classroom
Source: https://honen-academy.honen.com/docs/6ab3767578ce9f17182796a2
Honen's Google Classroom integration uses a Classroom add-on, separate from LTI. Your institution must make the add-on available and authorize the relevant Google account.
## Install the add-on
1. Open **Organization → Integrations → Your LMS** and choose **Google Classroom**.
2. Choose **Install add-on** to open Honen’s Google Workspace Marketplace listing.
3. For an institution-wide rollout, use your Google Workspace super administrator account and choose **Admin install**.
4. Select the organization, organizational units, or groups that should receive the add-on. Review the requested access and complete Google’s installation flow.
5. Ask a teacher in that audience to open Classroom and confirm Honen appears in **Add-ons**.
## Attach Honen content
1. As a teacher, open the class and choose **Classwork → Create → Assignment**.
2. In the attachment area, open **Add-ons → Honen**.
3. Sign in with the intended account when requested. Choose a complete course or a supported graded activity from a course.
4. Attach the content, set points and a due date as needed, then choose **Assign**.
5. Open the assignment as a test student and confirm the attached content launches.
Use the installed add-on to create an attachment with the Classroom launch and grade-reporting flow. Its availability follows your Google Workspace setup and add-on installation.
## Validate grades
For a graded activity, configure a positive point value in Classroom. Complete the Honen activity as a test student, then inspect the submission's draft points in Classroom. Honen updates draft points; the teacher is responsible for publishing the grade.
Use Classroom’s student-work review to inspect the attachment and draft grade before returning work to students.
## Copies and account changes
When copying assignments, verify the copied attachment and student submission in the destination class. Reconnect if authorization expires or the connected account changes. Use a dedicated test class when preparing your rollout.
Prepare an installed add-on and a Classroom test class so you can verify the complete teacher and learner experience before rollout.
Start at [LMS Integrations](https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392) to compare this add-on with [LTI](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9) and [SCORM](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7).
## Export and validate a SCORM package
Source: https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7
Use SCORM when your LMS imports course packages. Honen supports SCORM 1.2 and 2004. A package connects learners to the live Honen course, keeping course content current from one place.
## 1. Review workspace defaults
1. Open **Organization → Integrations → Your LMS** and select the SCORM path.
2. Review **Export defaults**: learner audience, version, completion trigger, pass/fail status, and score source.
3. Check **Report time spent** and **Save resume position**.
4. Review the tenant and group intended for this LMS.
The default is SCORM 1.2; choose the version accepted by your target LMS. Internal delivery provisions workspace members. External delivery requires selecting a Site in the same workspace and uses its external-learner provisioning; the export does not require that Site to be published.
## Choose reporting for your program
| Setting | Choices and purpose |
| --- | --- |
| Mark complete when | **Course is completed**, **Progress reaches threshold**, or **Learner launches** |
| Pass or fail status | Use **Pass on completion** to report success when the selected completion rule is met, or **Don't report** for completion-only reporting |
| Score reported | Use **Progress %** for the course progress percentage, **Pass/fail** for 1 out of 1 on completion, or **No score** |
| Report time spent | Send the learning session duration to the LMS |
| Save resume position | Let the LMS retain the learner's position between launches |
Choose a completion trigger that reflects the required work. Use **Pass on completion** when finishing that work should count as success, and review quiz and test results in Honen Analytics. Use **Learner launches** for material where opening the resource is the intended completion event.
## Organize LMS tenants
A tenant gives an LMS its own launch subdomain and optional group enrollment. This keeps launch sessions distinct and helps you report on each audience.
1. In the SCORM integration settings, find the tenant controls and choose to add a tenant.
2. Enter its **Name** and **Subdomain label**. The label uses lowercase letters, numbers, and hyphens, with a maximum of 31 characters.
3. Optionally choose **Auto-enroll into groups** for that LMS audience.
4. Choose **Create tenant** and check its domain status. Use **Recheck domain status** when confirming the domain is ready.
5. Select the tenant when exporting a course. The selector appears when there is more than the default tenant to choose from.
[Create your groups](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860) before assigning tenant enrollment. A default tenant can also be provisioned by the first package export.
## 2. Export from the course
1. In an organization workspace, open the manage screen of a course you can edit.
2. Open **Export** and choose **SCORM package**.
3. Confirm the package audience, tenant, reporting options, and version.
4. Download the ZIP and keep it intact.
5. In your LMS, import the ZIP as a SCORM course or activity using that LMS's import workflow.
A default tenant can be created as part of the first export. Its isolated launch subdomain keeps the LMS learner session separate from your Honen administration session.
## 3. Validate as a learner
1. Launch the imported activity from the LMS using a test learner.
2. Confirm the intended course and learner identity.
3. Complete enough work to trigger the reporting policy you selected.
4. Exit through the LMS player, then check its gradebook and completion status.
5. Relaunch and check the saved position when resume reporting is enabled.
SCORM reports through the browser's LMS API. Review the completion and grade in your LMS after the learner finishes. Choose **Progress %** to report the course progress percentage, or **Pass/fail** to report a score of 1 out of 1 on completion. **No score** reports without a numeric grade. For pass/fail status, choose the course-completion policy when completion should count as a pass.
## Update or revoke
The course is loaded live, so ordinary content updates do not require distributing a new ZIP. Re-export when the package's audience, group, reporting settings, or secret change.
In the integration's package list:
- Use **Download** to retrieve the current package again.
- Use the package's enable switch to pause or resume that package's launches.
- Use **Revoke existing downloads** to rotate its launch secret. Download the replacement package and update it in your LMS so learners use the new version.
- Use **Delete** when retiring the package entirely, after removing its LMS activity from the learner rollout.
Use the workspace SCORM switch when you intend to pause SCORM delivery for the whole workspace. Individual package controls let you manage one program at a time.
Use [LMS Integrations](https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392) to compare SCORM with other delivery options, or [Export a cmi5 package](https://honen-academy.honen.com/docs/6ab38b4d3b82ff9f26dee8ed) for a compatible LMS that uses xAPI learning records.
Export from an organization workspace with SCORM enabled.
## Export a course as a cmi5 package
Source: https://honen-academy.honen.com/docs/6ab38b4d3b82ff9f26dee8ed
Deliver a live Honen course through a cmi5-compatible LMS and carry detailed learning records into its Learning Record Store (LRS). The package connects your LMS to the course, so your team can keep improving the learning experience in Honen.
You need an organization workspace, permission to edit the course, and an LMS with cmi5 launch and LRS support. For a package-based LMS that uses SCORM, follow [Export a SCORM package](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7).
## 1. Prepare the course and audience
1. [Build and review the course](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca37c), including the activities and assessments learners need to finish.
2. Decide whether the learners are internal members of your team or an external audience.
3. For internal learners, optionally [create a group](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860) to organize their reporting.
4. For external learners, [create a Site](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397) in the same workspace. You will select it as the learner community during export.
5. Confirm xAPI is enabled under **Organization → Integrations → Your LMS → Learning records and cmi5**. A workspace's first cmi5 export can initialize this configuration; keep it enabled for your cmi5 program.
## 2. Choose the package settings
1. Open the course's manage screen and choose **Export → cmi5 package**.
2. Under **Who is taking this?**, choose internal members or external learners.
3. For internal delivery, use **Add to group** if you want automatic group enrollment. For external delivery, select the intended Site.
4. If your workspace has multiple launch tenants, select the tenant for the receiving LMS.
5. Choose **Counts as finished when** to define what your LMS must receive before the unit is satisfied.
| Counts as finished when | cmi5 policy | Use it for |
| --- | --- | --- |
| The learner finishes the course | `Completed` | Completion-based training |
| The learner passes | `Passed` | An outcome demonstrated through a passing result |
| The learner finishes and passes | `CompletedAndPassed` | Programs requiring both completion and success |
| The learner finishes or passes | `CompletedOrPassed` | Either qualifying result; the default |
| As soon as the learner opens it | `NotApplicable` | Informational units with no completion or pass requirement |
## 3. Set completion and success reporting
1. Expand **LMS reporting**.
2. Set **Mark complete when** to course completion, a progress threshold, or learner launch. When choosing a threshold, enter the required percentage.
3. Set **Pass or fail status** to **Pass on completion** when meeting the completion rule should count as success, or choose **Don't report** for completion-only reporting.
4. Enter an optional **Mastery score** from 0 to 100 when the LMS should compare a finished attempt with that threshold. Honen reports course progress as the cmi5 score; the LMS launch can supply its own mastery threshold.
5. Select **Download package** and save the ZIP intact.
Choose reporting settings that supply the evidence required by your completion policy. For a unit that requires a pass, use **Pass on completion** or a mastery threshold aligned with the reported course progress. Review quiz and test performance in Honen Analytics.
## 4. Import and launch in your LMS
1. Use your LMS's cmi5 import workflow to upload the ZIP.
2. Add the imported unit to the intended course or learning program.
3. Launch it as a test learner in normal learning mode.
4. Confirm the learner sees the intended Honen course and joins the expected group or Site.
5. Complete the work required by your policy, then exit the activity normally.
6. In the LMS/LRS, confirm the learner's launch, completion or success, and session-end records. The usual sequence is `initialized` → learning → `completed` / `passed` / `failed` → `terminated`.
7. Relaunch to confirm the learner can continue with the expected identity and course access.
Browse and Review modes support inspection without awarding a new completion or pass. Validate your rollout using the LMS's normal learner launch mode.
## Keep delivery current
Edit and publish the course in Honen to update the live content. Create a new export when you need different audience or reporting settings. Keep the activity identifier stable for an existing package so your LMS continues to associate its records with the same learning unit.
Use [xAPI forwarding](https://honen-academy.honen.com/docs/6ab38b3b3b82ff9f26dee8bd) for a separate reporting destination, or [Honen as an LRS](https://honen-academy.honen.com/docs/6ab38b303b82ff9f26dee89f) for external clients that read or write learning records.
## Track learning with xAPI and cmi5
Source: https://honen-academy.honen.com/docs/6ab3767378ce9f1718279699
Use xAPI for detailed learning records and cmi5 when an LMS launches assignable units using that standard. These are separate from SCORM and the Connector API.
## Choose the workflow
| Goal | Use |
| --- | --- |
| Send Honen learning events to another learning record store | [Send learning records to an LRS](https://honen-academy.honen.com/docs/6ab38b3b3b82ff9f26dee8bd) |
| Let an approved external producer write records into Honen | [Use Honen as an LRS](https://honen-academy.honen.com/docs/6ab38b303b82ff9f26dee89f) |
| Import a live Honen learning unit into a cmi5-compatible LMS | [Export a cmi5 package](https://honen-academy.honen.com/docs/6ab38b4d3b82ff9f26dee8ed) |
Follow the linked walkthrough for the complete setup, screenshots, and validation steps.
## Configure xAPI
1. Open **Organization → Integrations → Your LMS** and choose the xAPI/cmi5 path.
2. Review whether xAPI is enabled for the workspace. It is off until configured; the first cmi5 export can also enable it.
3. For forwarding, open **Send to an LRS → Add destination**. Enter a name, HTTPS endpoint, xAPI version, **Basic auth key**, and **Basic auth secret** from your LRS. Use **Test** after saving.
4. For external access to Honen's LRS, open **Honen as an LRS → New credentials**. Name the connection and choose **Read only** for reporting, or **Read and write** when the external system must submit records. Choose **Create credentials** and copy the one-time secret.
5. Under **What Honen records**, select the event types you need. Review whether to include learner email. Keep the identifier prefix stable so new records retain the same activity identities.
6. Complete a test activity. Inspect the records in the destination LRS or query Honen's LRS with your xAPI client. Check **Recent delivery problems** for forwarding errors.
When xAPI is enabled, Honen stores your selected learning events and can forward them to configured destinations. Use **Test** to check the destination connection, then complete a learning activity and inspect its record in the LRS.
## Export cmi5
1. In an organization workspace, open the manage screen of a course you can edit and select **Export → cmi5 package**.
2. Choose the audience and completion/pass requirements, including the `moveOn` policy.
3. Download the ZIP and import it into a compatible LMS.
4. Launch as a test learner, complete the required work, and check the LMS/LRS for the expected initialized, completion or success, and terminated records.
cmi5 packages load live content. Exporting the first package can enable the workspace's xAPI configuration; an explicitly disabled xAPI configuration blocks the export. cmi5 needs an LRS reporting channel.
## Interpret completion
`Completed`, `Passed`, `CompletedAndPassed`, and `CompletedOrPassed` wait for different evidence. `NotApplicable` is informational. Check the LMS's mastery score and launch mode: Browse and Review launches should not award a new completion or pass.
## Use the right connection credentials
Honen's LRS uses HTTP Basic xAPI credentials and the `X-Experience-API-Version` header. Use dedicated xAPI credentials for your LRS client. Honen exports cmi5 packages for LMS delivery and produces xAPI records for learning analysis.
Follow [Honen as an LRS](https://honen-academy.honen.com/docs/6ab38b303b82ff9f26dee89f) for client authentication and record verification, or [Export a cmi5 package](https://honen-academy.honen.com/docs/6ab38b4d3b82ff9f26dee8ed) for LMS launch and reporting setup. Use a test learner in your target LMS/LRS to confirm the launch and reporting flow.
For package delivery without detailed xAPI records, see [SCORM packages](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7). For registered external-tool launches, see [LTI 1.3](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9).
## Send learning records to an LRS
Source: https://honen-academy.honen.com/docs/6ab38b3b3b82ff9f26dee8bd
Bring Honen learning activity into the reporting tools your organization already uses. With xAPI forwarding, Honen records selected learning events and sends a copy to each configured Learning Record Store (LRS).
You need **Manage integrations** permission and an LRS administrator who can supply an HTTPS xAPI endpoint and its Basic authentication credentials.
## 1. Choose the records you need
1. Open **Organization → Integrations → Your LMS → Learning records and cmi5**.
2. Turn on **Enable xAPI for this workspace**.
3. Under **What Honen records**, choose the event families for your program.
| Event selection | Reporting purpose |
| --- | --- |
| Course completions | Track completion of the full learning program |
| Topic completions | Understand progress within a course |
| Activity completions | Analyze the individual learning experiences people complete |
| Test and project results | Connect assessments and practical work to outcomes |
1. Decide whether to **Include members' email in statements** according to your reporting and identity policy.
2. Review **Identifier prefix** before your rollout. Keep it stable so activity identities remain consistent across records.
## 2. Add your LRS destination
1. Under **Send to an LRS**, choose **Add destination**.
2. Enter a recognizable **Name**, such as the reporting environment or learning program.
3. Select the **xAPI version** accepted by your LRS.
4. Paste the LRS's HTTPS **Endpoint**. Use its xAPI base endpoint, as supplied by the LRS administrator.
5. Enter the **Basic auth key** and **Basic auth secret** for that destination.
6. Choose **Add destination** to save it.
7. Use **Test** on the saved destination to check connectivity and authentication.
The connection test checks the destination without creating a learning statement. Next, complete a real test activity to verify the full reporting path.
## 3. Verify learning records
1. Give a test learner access to a course containing the event types you selected.
2. Complete an activity, topic, assessment, or course as appropriate.
3. Open your destination LRS and locate that learner's new statements.
4. Check the activity identity, event, timestamp, result, and duration where relevant.
5. Compare the records with the learner's progress in [Honen Analytics](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e).
Honen stores its learning events locally before forwarding and retries temporary delivery failures. **Recent delivery problems** lists unsuccessful forwarding attempts when present. Use the destination's endpoint and authentication settings to investigate, then test the connection again.
## Manage destinations
Add separate destinations when more than one approved reporting system needs the records. Each destination has its own connection and enable switch. Pause an individual destination when maintaining that reporting system; use the workspace xAPI switch when changing the recording policy for the entire workspace.
For an external client that should query or contribute records to Honen itself, use [Honen as an LRS](https://honen-academy.honen.com/docs/6ab38b303b82ff9f26dee89f). For a cmi5 LMS launch, follow [Export a cmi5 package](https://honen-academy.honen.com/docs/6ab38b4d3b82ff9f26dee8ed).
## Use Honen as a Learning Record Store
Source: https://honen-academy.honen.com/docs/6ab38b303b82ff9f26dee89f
Connect reporting pipelines and approved learning tools to Honen's workspace-scoped Learning Record Store (LRS). Use read-only access to analyze records, or read-and-write access when an external learning system should contribute them.
You need **Manage integrations** permission in the organization workspace and an xAPI-compatible client.
## 1. Create credentials for the client
1. Open **Organization → Integrations → Your LMS → Learning records and cmi5**.
2. Enable xAPI for the workspace.
3. Under **Honen as an LRS**, choose **New credentials**.
4. Enter a **Name** identifying the client, such as “Learning reporting pipeline.”
5. Choose **Read only** for reporting or **Read and write** for a learning system that submits statements and uses state or profile documents.
6. Choose **Create credentials**.
7. Copy the key and one-time secret into the client's protected configuration, then choose **Done**.
Use a separate credential pair for each client so its access can be managed independently. The client sees records from the workspace that issued its credentials.
## 2. Configure the xAPI client
| Setting | Value |
| --- | --- |
| LRS base endpoint | `https://honen.com/xAPI` |
| Authentication | HTTP Basic using the generated key and secret |
| xAPI version | Send `X-Experience-API-Version: 1.0.3` |
| Statement resource | `/xAPI/statements` |
Use the LRS credential pair for this connection. The [Honen Connector API](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e) uses a separate authentication workflow.
For a read-only verification from a protected terminal environment:
```bash
curl --user "$HONEN_XAPI_KEY:$HONEN_XAPI_SECRET" \
-H 'X-Experience-API-Version: 1.0.3' \
'https://honen.com/xAPI/statements?limit=10'
```
Set these environment variables from your secret manager or secure local configuration. Keep actual credentials out of shared scripts and documentation.
## 3. Validate the client workflow
1. Complete a learning activity in Honen with the matching event type enabled under **What Honen records**.
2. Query the statements resource with the reporting client.
3. Confirm the expected learner, activity, result, and timestamp.
4. For a read-and-write integration, submit a test statement from the external learning tool and retrieve it again.
5. If the tool uses saved state or profiles, verify those operations with the same credential pair.
The LRS also exposes activity state, activity profiles, agent profiles, activity information, agent information, and an `about` resource. Configure your xAPI client to use the base endpoint, version header, and workspace credentials above.
## Manage access
The credential list shows the key, scopes, request count, and active state. Use its enable switch to pause a client and its revoke action when retiring that credential. Keep a replacement client configured and verified before completing a planned credential transition.
For outbound reporting, follow [Send learning records to an LRS](https://honen-academy.honen.com/docs/6ab38b3b3b82ff9f26dee8bd). To launch a Honen course from a cmi5 LMS, use [Export a cmi5 package](https://honen-academy.honen.com/docs/6ab38b4d3b82ff9f26dee8ed).
## Governance
Source: https://honen-academy.honen.com/docs/6ab38b5e3b82ff9f26dee911
Give authors the freedom to create while keeping your organization's teaching approach, source material, visual identity, and publishing decisions consistent. Honen separates these responsibilities so the right people can own each part.
## Choose the right control
| You want to… | Use | Start here |
| --- | --- | --- |
| Give creators a repeatable starting point | Templates | [Create and manage templates](https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923) |
| Apply a standing instruction during authoring or generation | Rules | [Create and manage Rules](https://honen-academy.honen.com/docs/6ab38b6b3b82ff9f26dee938) |
| Reuse a task prompt when someone needs it | Skills | [Create and use Skills](https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a) |
| Choose who can invoke a Skill | Skill sharing | [Share Skills](https://honen-academy.honen.com/docs/6ab38b703b82ff9f26dee941) |
| Keep generated visuals consistent | Brand | [Set brand standards](https://honen-academy.honen.com/docs/6ab38b5f3b82ff9f26dee916) |
| Set the tutor's coaching boundaries | Guardrails | [Configure tutor guardrails](https://honen-academy.honen.com/docs/6ab38b7b3b82ff9f26dee95f) |
| Approve course releases for a particular audience | Publishing reviews | [Configure publishing approvals](https://honen-academy.honen.com/docs/6ab38b673b82ff9f26dee92d) |
| Keep the facts current and assign responsibility | Knowledge Base ownership | [Manage source ownership](https://honen-academy.honen.com/docs/6ab38b793b82ff9f26dee957) |
## Set up a repeatable workflow
1. Give subject-matter experts ownership of the relevant Knowledge Base folders. For example, Product maintains product instructions while Customer Success maintains onboarding procedures.
2. Have your learning team create a template for each repeatable format, such as a first-week course or a short product update.
3. Put standing writing requirements in Rules. Save optional review, coaching, or drafting tasks as Skills.
4. Set the workspace Brand and the tutor Guardrails appropriate to your audience.
5. Configure destination catalogs and the reviewers who approve their releases.
6. Test the complete path with a small course: choose the template, add sources, approve the outline, build, preview, and submit for review.
## Delegate the work
In **Organization → Roles & Permissions**, management of AI Rules, AI Skills, course templates, and catalogs can be delegated separately. An author does not need to administer the whole workspace to maintain one of these areas. Workspace Brand changes require an administrator.
Skill sharing controls who can use a saved prompt. Knowledge Base sharing controls source-document access. Catalog access controls the learning audience. Set each for its purpose.
See [Access and security](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353) for roles and [Single sign-on and identity](https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870) for connecting your identity provider.
## Manage source ownership
Source: https://honen-academy.honen.com/docs/6ab38b793b82ff9f26dee957
Keep learning accurate by giving the people closest to the work responsibility for its source material. A practical model is for subject-matter experts to own the facts and the learning team to own templates, teaching standards, and release quality.
## 1. Give each knowledge area a home
1. Open **Knowledge Base**.
2. Create folders for your teams or topics, such as Product, Customer Success, Legal, and Security.
3. Add focused subfolders for the material people maintain together.
4. Keep reusable learning instructions in a separate folder, such as Learning & Development.
5. Add tags that help people find related material across folders.
Use department folders when ownership follows your organization. Use shared-topic folders when several teams contribute to the same subject. See [Organize and use source material](https://honen-academy.honen.com/docs/6ab35ef9da8e0901468ca3d9) for the folder and document walkthrough.
## 2. Set access to match the work
1. Open the folder or document's sharing controls.
2. Choose the workspace, groups, or named people who need access.
3. Set the appropriate role: **Viewer**, **Editor**, **Maintainer**, or **Admin**.
4. Save the sharing changes and confirm the intended audience.
Use Viewer for people who need to consult the source, Editor for contributors who update content, and the higher roles for the people maintaining and administering the knowledge area. Keep responsibility clear in the folder's documentation: name the team that reviews factual changes and who handles access decisions.
Source ownership, Skill sharing, course editing, and catalog access are separate controls. Give authors the sources they need and give learners the published experience intended for them.
## 3. Maintain the authoritative version
For Honen-authored documents, update the document and wait for **Saved**. Review **Version history** to compare revisions. For connected documents, maintain the original system and refresh the connection so the Knowledge Base reflects it.
Choose the appropriate connection for your library: [GitHub](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc), [Notion and Confluence](https://honen-academy.honen.com/docs/6ab38b913b82ff9f26dee989), [cloud files](https://honen-academy.honen.com/docs/6ab38b923b82ff9f26dee991), or [Document360](https://honen-academy.honen.com/docs/6ab38b943b82ff9f26dee999).
## 4. Carry changes into learning
1. Update the source document and confirm its new content.
2. Open a course that uses it and inspect the source material status.
3. When **Source doc updated** appears, select **Refresh from KB** to update the course's material snapshot.
4. Ask the course editor to revise the affected lessons, questions, or activities using the refreshed source.
5. Preview the changes and submit the new course revision through [publishing approvals](https://honen-academy.honen.com/docs/6ab38b673b82ff9f26dee92d).
Refreshing a source snapshot and revising the course are separate steps. This gives authors a chance to assess how a factual change should affect the learning experience.
## 5. Make maintenance repeatable
Agree on a review cadence with each source-owning team. Use an [Automation](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331) to ask an Agent to inspect selected sources and identify affected courses. The Knowledge base drift starter suggests updates; configure proposal access and explicit instructions when the Agent should prepare course changes for human review.
Keep the work scoped to the Agent's allowed folders and courses. Use [Rules](https://honen-academy.honen.com/docs/6ab38b6b3b82ff9f26dee938) for standing authoring requirements, [Skills](https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a) for repeatable review tasks, and [Templates](https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923) for the format in which the team teaches the material.
## Set brand standards
Source: https://honen-academy.honen.com/docs/6ab38b5f3b82ff9f26dee916
Give generated illustrations, lecture slides, and interactive artifacts a consistent visual identity. Workspace Brand brings together your palette, logo, reference images, design instructions, and reusable icons.
A workspace administrator manages Brand in **Organization → Brand**.
## 1. Choose a starting point
Choose one of three options:
- **From your website:** enter the website address and select **Continue** to extract its visual style.
- **Upload brand guidelines:** select a PDF, PNG, JPG, WebP, Markdown, or text file. PDF guidelines can be up to 5 GB. Keep the page open until uploading finishes; document processing can then continue in the background.
- **From scratch:** select **Start designing** and enter your own brand details.
All three paths lead to an editable draft so you can review the result before saving.
## 2. Define the visual style
1. Enter **Brand name**.
2. Add a **Logo**, or use **Replace** to change an existing one.
3. Set **Primary**, **Accent**, **Background**, and **Text** colors with the color picker or hex fields. Leave a color unset to use its default.
4. Turn on **Use my brand style** when your guidelines and references should define generated images and lecture slides.
5. Write **Design instructions** covering layout, typography, icon style, and how reference images should be used.
6. Add up to six **Reference images** in PNG, JPEG, or WebP format, up to 2 MB each.
Use specific instructions such as “forest green headings, warm ivory backgrounds, small gold highlights, and generous spacing.” Explain what each reference contributes: illustration style, a slide layout, or an icon treatment.
## 3. Preview and save
1. Select **Generate preview**.
2. Review both **Reading illustration** and **Lecture slide**.
3. Adjust the draft if needed and select **Regenerate**.
4. Select **Save brand** to keep the reviewed settings and previews.
When settings change after a preview was generated, regenerate to see the revised appearance before saving. Brand settings guide future generation; update existing course visuals through their editing controls when you want them to adopt the new style.
## 4. Add reusable artifact icons
1. Find **Artifact icons** on the Brand page.
2. Select **Add icons** to upload PNG, JPEG, WebP, or SVG files. Each icon can be up to 2 MB; the library supports up to 512 icons.
3. Give each icon a meaningful name so generated HTML artifacts can use it for the right concept.
4. For a collection, select **Import ZIP or CSV**. ZIP archives can contain icons in folders. CSV files use `name,url` columns with public HTTPS image links; **Example CSV** shows the format. Import files can be up to 4 MB.
5. Use the search and **Preview surface** controls to check icons on light or dark backgrounds.
6. Select **Save brand** to retain the imported icons.
## 5. Require the workspace Brand
After saving a brand, turn on **Use this brand on every course** when authors should use the organization's identity across courses. Members cannot set a different brand on their own courses while this is required.
With enforcement off, course-level brand settings remain available. The workspace's generated-media Brand and a Site's logo, theme, and layout have different purposes; configure your academy appearance in the [Site editor](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397).
Related: [Templates](https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923), [Create and edit media](https://honen-academy.honen.com/docs/6ab3766a78ce9f1718279665), [Governance](https://honen-academy.honen.com/docs/6ab38b5e3b82ff9f26dee911).
## Create and manage templates
Source: https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923
Package your team's preferred course format into a reusable starting point. Templates combine instructions, setup questions, activity choices, Skills, and Knowledge Base folders so authors spend their time on the subject they are teaching.
You need a team workspace and **Manage course templates** permission. The example uses a fictional Northstar Academy onboarding template.
## 1. Create a template
1. Open **Organization → Rules, Skills & Templates → Templates**.
2. Select **New template**.
3. Enter a **Name** authors will recognize and a **Short description** explaining when to use it.
4. Choose **Content type**: Course, Atom, or Assessment.
5. Write **Agent instructions** describing the learning goal, tone, structure, and expected result.
6. Add a **Background prompt** for guidance applied behind the scenes. It does not fill the author's message box.
## 2. Make the opening prompt easy to complete
Use **Input starter** to combine ordinary text with fields authors fill in.
1. Write the fixed parts of the brief, such as “Create onboarding for…”.
2. Select **Add blank** for an open answer such as the team's name.
3. Select **Add dropdown** for a defined choice such as the audience or experience level.
4. Give every field a clear label. Each dropdown needs at least two distinct options.
A starter supports up to eight fields. Keep background instructions in their own field so the visible starter stays focused on decisions the author needs to make.
## 3. Define setup questions and structure
1. Add up to three **Custom setup questions**. Use the optional guidance to explain how each answer should affect the result.
2. Leave custom questions empty when you want the assistant's usual setup questions for missing decisions.
3. For a **Course**, optionally set **Number of units** and **Topics per unit**.
4. Choose **Activity types**, or leave them open for setup. Courses support reading, flashcards, quiz, game, lecture, podcast, Jam session, comic, and video choices. An Atom can select up to three activity types. An Assessment uses tests or projects instead of these learning activities.
5. Put requirements such as “reading-only; no unit tests” in **Agent instructions**, then check the proposed outline when using the template.
## 4. Add reusable guidance and source folders
1. Select up to eight enabled **Skills** that apply to **Course Creator** and whose instructions should accompany the template.
2. Select up to eight **Knowledge Base folders** containing the relevant source material.
3. Upload a cover or generate one using your workspace Brand.
4. Leave **Enabled** off while the template is being prepared.
5. Select **Save template** and reopen the saved item to check it.
Authors need access to the selected Skills and source folders. A template selection does not grant access to those resources.
## 5. Offer the template to creators
1. Open the saved template, turn on **Enabled**, and save.
2. In the Templates list, turn on **Replace course suggestions with templates** to offer enabled templates as suggestions on the creation page.
3. Open **Create**, choose the relevant content type, and select the template.
4. Complete the starter fields, add the subject and sources, then send the brief.
5. Answer setup questions and review the proposed outline before approving the build.
Selecting a template sets its content type. Clear the selection to change the type or return to your own prompt. Authors can still write a brief without a template.
## Edit, pause, or retire a template
Open a template from the list, change its fields, and select **Save template**. Turn **Enabled** off to keep a draft while removing it from the offered choices. Use the template's delete control when retiring it permanently, then confirm the named item.
A course keeps the template instructions saved with it even if the original template is later removed or unavailable. Changes to the template are therefore a starting point for future use, rather than an automatic rewrite of existing courses.
## Apply a template to an existing course
1. Open the course editor and **Settings → General → Course template**.
2. Attach or change the template.
3. Ask the editor assistant for the changes you want to make.
4. Preview the result and publish through the course's normal review process.
The selected template guides future editing; choosing it keeps the existing course content.
Continue with [Create your first course](https://honen-academy.honen.com/docs/6ab35ee5da8e0901468ca374), [Skills](https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a), or [Brand standards](https://honen-academy.honen.com/docs/6ab38b5f3b82ff9f26dee916).
## Create and manage Rules
Source: https://honen-academy.honen.com/docs/6ab38b6b3b82ff9f26dee938
Rules keep recurring authoring requirements in one place. An enabled Rule is applied on the AI surfaces you choose, so authors do not have to repeat the same tone, terminology, or formatting instructions in every request.
You need **Manage AI rules** permission in a team workspace. For tutor behavior with learners, use [Guardrails](https://honen-academy.honen.com/docs/6ab38b7b3b82ff9f26dee95f).
## 1. Write a Rule
1. Open **Organization → Rules, Skills & Templates → Rules**.
2. Select **New rule**.
3. Enter a **Title** and an optional **Short description**.
4. Keep **Write content** selected and enter the standing instruction in **Content**.
For example: “Use plain language and numbered steps. Name the relevant product control and finish each task with a concrete success check.” Make each Rule about a specific requirement so it is easy to review later.
## 2. Choose where it applies
1. In **Applies to**, select the relevant surfaces.
2. Use **Workspace Assistant**, **Course Creator**, or **Course Editor** for their respective conversations.
3. Choose generation surfaces for requirements that belong in generated content: **Topics and outlines**, **Reading generation**, **Flashcard generation**, **Quizzes and tests**, **Lecture generation**, **Podcast generation**, **Discussion generation**, **Song generation**, **Game generation**, **Video generation**, or **Comic generation**.
4. Select **Apply everywhere** when the same instruction should apply across all listed surfaces.
At least one surface is required. Selecting Course Editor and selecting Reading generation serve different purposes; choose both when the instruction should guide the conversation and generated readings.
## 3. Save and activate
1. Leave **Enabled** off to save a Rule for review without applying it.
2. Select **Create**.
3. Reopen the Rule and check its content and selected surfaces.
4. Turn on **Enabled** and select **Save changes** when it is ready.
5. Start a request on a selected surface and review the result against the Rule.
## Use a Knowledge Base document as the Rule
1. Create or maintain an instruction document in the Knowledge Base.
2. In the Rule editor, choose **From Knowledge Base**.
3. Select the source document, set the title and surfaces, and save.
4. Maintain the instruction in its source document. Honen uses its current indexed text when resolving the Rule.
The document becomes reusable AI guidance for the Rule's audience. Choose content intended for that audience, even when some recipients do not have direct access to the source document. Keep long reference libraries as course materials; a Rule's instruction content is limited to 12,000 characters.
## Maintain the Rule library
Use the list's search to find a Rule by name or description. Select **Edit** to change it, use the up/down controls to organize its order, or switch it off to pause it. Delete a retired Rule using its named delete control and confirmation.
Keep instructions compatible with each other. Ordering makes the library easier to manage; clear, consistent instructions make the expected behavior easier to assess.
Related: [Templates](https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923), [Skills](https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a), [Source ownership](https://honen-academy.honen.com/docs/6ab38b793b82ff9f26dee957).
## Create and use Skills
Source: https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a
Turn a useful prompt into a repeatable action. Skills help authors run a familiar review, draft a checklist, or apply a teaching approach without rebuilding the instructions each time.
You need **Manage AI skills** permission to create or edit Skills. People who receive a Skill can invoke it on its selected surfaces without receiving editing rights.
## 1. Create the Skill
1. Open **Organization → Rules, Skills & Templates → Skills**.
2. Select **New skill**.
3. Enter a **Title** that describes the task and a **Short description** explaining the result.
4. Choose **Write content** and enter the prompt in **Content**.
5. Select one or more **Applies to** options: **Workspace Assistant**, **Course Creator**, and **Course Editor**.
6. Keep **Enabled** on when it is ready to use, or turn it off to prepare it first.
7. Select **Create**.
The demo Skill asks for three onboarding tasks, a success check for each, and a Friday check-in agenda. It asks for the result in the conversation, making the desired outcome clear.
## 2. Choose who can use it
New Skills start **Restricted**. The sharing dialog opens after creation. Workspace administrators and Skill managers can use, edit, and share Skills; choose the intended people, groups, or workspace audience before rolling one out. See [Share Skills](https://honen-academy.honen.com/docs/6ab38b703b82ff9f26dee941).
## 3. Invoke the Skill
1. Open one of the Skill's selected surfaces, such as **Assistant**.
2. Type `/` in the message box and choose the Skill from **Workspace skills**. You can also open **Attach → Skills**.
3. Confirm that the Skill appears as a chip in your message.
4. Add any context the prompt needs, such as the target topic or audience.
5. Send the message and review the result.
A Skill runs when you invoke it; it is not an always-on Rule. Its instructions guide the request within the permissions available to the person using it.
## Use a source document for the prompt
Choose **From Knowledge Base** in the Skill editor and select an instruction document you can read. Honen uses the document's current indexed text as the prompt. Update the document to maintain that instruction centrally, or change back to **Write content** to store the prompt directly in the Skill.
The Skill's sharing audience determines who can invoke those instructions. Sharing the Skill makes its prompt usable by that audience; it does not give them permission to browse or edit the source document.
## Use a Skill in a template
Enable the Skill for **Course Creator**, then open a [course template](https://honen-academy.honen.com/docs/6ab38b653b82ff9f26dee923), select it in **Skills**, and save. Up to eight Skills can accompany a template. Make the selected Skills available to the authors who will use it.
## Edit or pause a Skill
1. Find it in the Skills list using search.
2. Select **Edit**, update the prompt or surfaces, and select **Save changes**.
3. Use the enabled switch to pause or reactivate it.
4. Use the up/down controls to organize the list.
5. To retire it, use its delete control and confirm the named Skill.
If a colleague cannot find a Skill, check its **Enabled** state, **Applies to** surfaces, and [sharing audience](https://honen-academy.honen.com/docs/6ab38b703b82ff9f26dee941).
## Share Skills with your team
Source: https://honen-academy.honen.com/docs/6ab38b703b82ff9f26dee941
Make a reusable prompt available to the people who need it while keeping management with the team responsible for the instructions. Skill sharing controls use; workspace roles control editing and sharing.
## Share with selected people or groups
1. Open **Organization → Rules, Skills & Templates → Skills**.
2. Find the Skill and select its **Share** control.
3. Keep **General access** set to **Restricted**.
4. In **Add people or groups**, search for an existing workspace member or group and select it.
5. Check the entries under **People with access**. Added recipients receive **Can use** access.
6. Select **Save changes**.
Group sharing includes members of active descendant groups. Recipients must remain members of the workspace. This picker selects existing members and groups; use your organization's normal membership process when someone needs to join first.
## Make a Skill available across the workspace
1. Open the Skill's sharing dialog.
2. Change **General access** from **Restricted** to the workspace option.
3. Review the audience description and select **Save changes**.
4. Keep the Skill enabled on the intended surfaces so members can find it in the Skill menu.
## Change or remove access
1. Reopen **Share**.
2. Remove the relevant person or group from the access list, or return **General access** to **Restricted**.
3. Select **Save changes**.
Removing one grant does not remove another: a person may still have access through a group, workspace-wide sharing, or a management role. Access is checked when the Skill is used.
## Share the prompt and its sources deliberately
For a Knowledge Base-backed Skill, authorized recipients can invoke the source document's instructions even if they cannot open the document itself. Sharing the Skill does not change that document's sharing settings. Review the instruction text for the intended audience before making the Skill broadly available.
If the task also requires reading other documents or editing a course, those resources keep their own access controls.
Related: [Create and use Skills](https://honen-academy.honen.com/docs/6ab38b753b82ff9f26dee94a), [Source ownership](https://honen-academy.honen.com/docs/6ab38b793b82ff9f26dee957), [Access and security](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353).
## Configure tutor guardrails
Source: https://honen-academy.honen.com/docs/6ab38b7b3b82ff9f26dee95f
Set a consistent coaching approach for the AI tutor. Guardrails describe the boundaries the tutor should hold and what it should do instead, such as prompting a learner to attempt a task before offering the next hint.
Manage workspace Guardrails in **Organization → Guardrails** with **Manage AI rules** permission. These settings address learner-facing tutor behavior; [Rules](https://honen-academy.honen.com/docs/6ab38b6b3b82ff9f26dee938) address authoring and generation.
## 1. Start from the library or write your own
1. Open **Organization → Guardrails**.
2. Select **Library** to browse ready-made options, then **Add** the one you want to adapt. Open it to review and edit its instructions.
3. To write one from scratch, select **New guardrail**.
4. Enter a **Name**, a one-line **Description**, and the **Rules** the tutor should follow.
5. Optionally choose a **Written for** audience, such as Workforce or Higher ed.
## 2. Choose its scope
1. Leave **Apply to every course** off when authors should choose the guardrail in individual course settings.
2. Turn it on when every course in the workspace should inherit it.
3. Use **Enabled** to activate it, or leave it off while preparing the guidance.
4. Select **Create**, or **Save changes** when editing.
The audience label describes who the guidance was written for. Course selection and **Apply to every course** determine where it is used.
## 3. Select optional guardrails on a course
1. Open the course editor's **Settings → Guardrails**.
2. Review the guardrails inherited from the organization. Required workspace guardrails appear locked on.
3. Select any optional guardrails appropriate to this course.
4. Open the learner preview and try a short tutor conversation that exercises the intended coaching behavior.
The course's guardrail switch controls its optional selections. Required workspace guardrails remain in force. Guardrails follow the course's authoring organization when the course is shared elsewhere.
## Maintain the guidance
Open a guardrail's edit control to update its rules. Use the enabled switch to pause it, or **More actions → Move up / Move down** to organize the list. Deleting a guardrail stops it applying to courses that use it; turn it off when you want a reversible pause.
Keep guidance concise and concrete: name the boundary, describe the helpful alternative, and test a representative conversation. See [Configure course settings](https://honen-academy.honen.com/docs/6ab3613ceffafe59361d22e7) for tutor settings and [AI tutor](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432) for the learner experience.
## Configure publishing approvals
Source: https://honen-academy.honen.com/docs/6ab38b673b82ff9f26dee92d
Give reviewers a clear checkpoint before a course release reaches its audience. Publishing reviews hold the submitted course revision steady, so reviewers can assess a specific version while the author continues working.
Publishing approvals are available in team workspaces. Managing catalogs and review policy requires **Manage catalogs** permission.
## 1. Enable the workspace review workflow
1. Open **Organization → Publishing**.
2. Select **Publishing settings**.
3. Turn on **Enable publishing approvals**.
4. Close the dialog to return to your catalogs.
Each catalog has its own review policy. Catalogs without review remain available for publication according to their settings.
## 2. Set a catalog's reviewers
1. Open a catalog, or select **New catalog** and complete its name and description.
2. Open **Publishing**.
3. Keep **Catalog available** on when authors should be able to publish to it.
4. Turn on **Review required**.
5. Select the **Reviewers** and set **Required approvals** to a number those reviewers can meet.
6. Select **Save changes**.
Use **Access** to define who can open the catalog. Reviewers approve changes; viewing access is a separate choice. See [Catalogs, publishing, and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) for the broader publishing flow.
## 3. Submit a course revision
1. Finish the course draft and preview its learner experience.
2. Open **Publish** in the course editor.
3. Select the destination catalogs. Each catalog shows its own publication and review status.
4. Select **Submit for review** where approval is required.
5. Check that the destination is **In review**.
The request contains the submitted revision. Later draft edits do not change that review. When updating a published course, the current release stays live while the new revision is reviewed.
## 4. Review and decide
1. Open **Publishing reviews** from the dashboard or open the request from **Inbox**.
2. Search or filter the queue, then select the request.
3. Check the target catalog, audience, operation, revision, and approval progress.
4. Use **Changes** to compare lessons, questions, media, and settings. Use **Course preview** to inspect the submitted learner experience.
5. Add comments to the changed content or select a passage to start a feedback thread.
6. Choose **Approve** when the revision is ready, or **Send back** with the changes the author should make.
Approval is recorded for that target and operation. Once all required approvals are received, the submitted revision is published to the selected catalog. Check the resulting publication status to confirm delivery.
## 5. Revise and resubmit
1. Read the review comments and requested changes.
2. Update the working draft and preview the affected content.
3. Submit the revised version to the destination catalog.
4. Have reviewers assess the new request.
Comments remain associated with the reviewed revision. If the course was already live, sending an update back leaves that publication unchanged.
## Review removals and Agent proposals
Removing a course from a review-enabled catalog follows that catalog's review process. The current release remains available until the removal is approved; other catalogs are unaffected.
An [Agent](https://honen-academy.honen.com/docs/6ab35edbda8e0901468ca336) with proposal access can prepare changes for review. Course-editor proposals can be accepted into the draft using **Accept changes**, then published through the usual workflow. A catalog proposal follows the catalog's approval policy. Set the Agent's allowed courses, sources, and actions to match its job.
Before turning workspace approvals off, finish or send back pending review requests. For recurring source checks, see [Automations](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331).
## People, Groups and Workspaces
Source: https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca360
Use **Organization** to manage your team, and **My groups** to work with a particular cohort. These examples use the fictional **Northstar Academy · Demo** workspace.
## 1. Create a group
1. Open **Organization → Manage Groups**.
2. Choose **Create Group**.
3. Enter a descriptive name, such as **Product Onboarding · Documentation Demo**.
4. Add an optional description explaining who belongs in the group.
5. Choose **Create**. The group appears in the list; open its name to continue.
The group creator is added automatically, ready to organize the cohort.
## 2. Organize the group's learning
1. Open the group and use **Home** to arrange its learning home page.
2. Use **Courses** for course access and **Assignments** for work with a completion requirement.
3. Open **Curricula → Add curricula** to select a published learning path.
4. Search for the curriculum and add the intended result.
5. Choose **Done** after reviewing the selected content.
Publish the curriculum before selecting it for a group. This keeps the group’s learning path focused on content ready for delivery.
For the complete workflow, including subgroups, membership changes, catalog access, home-page sections, and group settings, follow [Create and manage groups](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860).
## 3. Prepare a member invitation
1. Open **Organization → Manage Members**.
2. Choose **Add Member → Add one member**. **Add multiple members** opens the bulk invitation path.
3. Enter the person's email. First name, last name, title, and tags are optional.
4. Choose the appropriate **Role** and optional **Assign to Group**.
5. Review the email, group, role, and the seat-cost notice, then choose **Add & Send Invite** when ready.
**Add & Send Invite** emails the invitation immediately. The person appears under pending invitations until they accept. Review the displayed seat information before sending.
## Invite a cohort with a CSV
1. Open **Add Member → Add multiple members**.
2. Add a row for each person, or choose **Import CSV** to load your roster.
3. Review each imported email, name, role, and group before sending.
4. Choose **Send invites**. Track acceptance in the Members page’s pending invitations.
Choose **Member** for learners, **Instructor** for people creating and assigning learning, or **Admin** for workspace administration. Review your workspace’s role definitions when it uses custom roles.
You can also ask the Workspace Assistant to invite a person or cohort. Include the exact email addresses, role, and group, for example: “Invite jordan@example.com as a Member of the Product onboarding group.” Sending this request can send invitations, so use the recipients and role you intend.
## 4. Find and maintain members
The Members page provides a text search plus **All Roles**, **All Status**, and **All Groups** filters. Use **List** or **Tree** to change the arrangement and **Columns** to choose visible fields. Open a person's name for their detail page. Pending invitations remain distinct from active members.
For a group's name or description, open **Group settings**, edit the fields, and choose **Save Changes**. Workspace roles and group roles can have different scopes; see [Access, roles, and safe publishing](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353).
## Tips for a smooth setup
- **Workspace and role:** confirm the intended workspace and use a role with the management permissions you need.
- **Ready-to-deliver curricula:** publish the learning path in the intended workspace before adding it to a group.
- **Invitation follow-up:** review pending status and the invitation email before sending another invitation.
Build a [curriculum and certificate](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350) before adding a learning path, or create an [assignment](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) for a particular course.
## Create and manage groups
Source: https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860
Give each cohort a home for its courses, learning paths, assignments, and progress. Use groups for departments, customer cohorts, partner programs, or successive onboarding classes; use subgroups to organize a larger audience.
## Create your first group
1. Select the workspace that should own the cohort.
2. Open **Organization → Manage Groups**, or **My groups** when it appears in your navigation.
3. Choose **Create Group**.
4. Enter a **Name** and an optional **Description** that explains the audience.
5. Choose **Create**, then open the new group.
The creator joins automatically. Group management controls are available to people with the appropriate group or workspace permissions.
## Create a subgroup
1. Open the parent group.
2. Select **Subgroups → Create Subgroup**.
3. Enter the subgroup's name and description. For example, use a separate week-one cohort inside Product Onboarding.
4. Choose **Create** and open the result.
5. Use the group's navigation to return to its parent or another subgroup.
The group list supports search and expanding or collapsing the hierarchy. Select the intended parent before creating a subgroup so that the cohort appears in the right branch.
## Add and manage members
1. Open the group's **Members** page.
2. Open its membership manager and select the people to include. A top-level group draws from workspace members; a subgroup draws from the parent group's members.
3. Review the pending additions and removals, then choose **Save changes**; the button includes the number of changes.
4. Use **All Roles**, **All Status**, and **All Tags** to find a cohort segment. Use **Columns** to choose the details in the table.
5. Open a member's actions to **Edit role**, edit tags, or **Remove from group**, according to your permissions.
A group role applies within that group. Review [access and roles](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353) before choosing management permissions. To bring a new person into the workspace first, follow [member invitations](https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca360#3-prepare-a-member-invitation).
You can also open a person's group memberships to manage their place in the hierarchy. Adding them to a nested group includes the required parent memberships; removing them from a parent removes memberships in its subgroups. Review the affected groups before saving.
## Add courses, catalogs, and learning paths
1. Open **Home → Content library**, or use the dedicated **Courses** page.
2. In **Courses**, choose **Add courses**, search by title, and choose **Add** beside each intended course.
3. Choose **Done** when the selected list is correct.
4. In the content library's **Catalogs** tab, choose **Add a catalog**, select a catalog, and choose **Attach** to include its available content.
5. Use **Curricula → Add curricula** for published learning paths. Search, add the intended curriculum, and choose **Done**.
Prepare and publish learning content before presenting it to learners. Course access and an assignment serve different purposes: access makes learning available; an [assignment](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) adds recipients, requirements, and an optional due date.
To maintain the collection, use the item's remove action in Courses, Curricula, or Catalogs. Removing a catalog removes that source of access; a learner can still have access through another grant. Use **Undo** when offered after removing course or curriculum content.
## Build the group's home page
1. Open **Home** as a group manager.
2. Choose a section from **Add section**: **Category heading**, **Course row**, **Path**, **Vertical path**, **Highlight**, or **Trending**.
3. Edit the section title and choose its content. Use **Content library** first to prepare the courses and paths available to the group.
4. Use the section's reorder handle to arrange the page. Keyboard users can focus the handle and use the up and down arrows.
5. Use the section's show/hide control to prepare content before displaying it. Use its delete control to remove an unwanted section.
6. Choose **Preview** to review the learner's home page. Changes to the group home editor save as you work.
Arrange the first row around the learner's next action, such as “Start your product onboarding,” then place optional reference courses below it.
## Follow assignments and progress
1. Open **Assignments** to review required work for the cohort.
2. Open **Analytics** to review the group's members, courses, completion, scores, and learning modes.
3. Select a course or learner to investigate the relevant detail.
4. Use the [analytics question library](https://honen-academy.honen.com/docs/6ab38b073b82ff9f26dee845) to ask a focused follow-up about the group.
## Rename or retire a group
1. Open **Group settings**.
2. Edit **Name** or **Description**, then choose **Save Changes**.
3. To permanently remove a group, use **Delete Group** in the danger zone, read the confirmation, and enter the required group name.
Deletion includes the group's descendants. Review the hierarchy and any active assignments before confirming this permanent action.
Continue with [curricula and certificates](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350) or [analytics and reporting](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e).
## Access, roles, and safe publishing
Source: https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353
Give each team the access it needs to build, teach, and learn. Configure permissions at the workspace, group, course, Knowledge Base folder, or Agent level.
## 1. Inspect an existing role
1. Open **Organization → Roles & Permissions**.
2. Select a role in the **Roles** list.
3. Read its description and permission groups.
4. Use **Search permissions** to narrow the list to a capability such as `knowledge`.
**Admin** is a locked system role. Other roles expose their own configurable permissions. Read a permission's description before changing it; labels marked **cascades** apply to descendant scopes.
## 2. Prepare a custom role
1. Choose **New role**.
2. Enter a clear **Name** and **Description**.
3. Search for the relevant permission family.
4. Select only the capabilities the role needs.
5. Review **Limits & usage** if the role should have activity or usage caps.
6. Choose **Create role** when the definition is ready. Creating the definition and assigning it to people are separate tasks.
Use the permission search to build a role around a specific job, such as maintaining approved learning sources.
## 3. Choose the right Knowledge Base level
| Permission | Intended capability |
| --- | --- |
| Ask knowledge base (AI) | Ask about shared documents through an assistant or connected channel. |
| View knowledge base | Browse, search, and read accessible shared content. |
| Use knowledge base | Add, create, and edit accessible knowledge content. |
| Manage knowledge base | Administer shared folders, item permissions, and versions. |
Higher Knowledge Base tiers include lower ones: Manage includes Use, Use includes View, and View includes Ask. The role editor automatically selects implied permissions. A role does not replace a document's sharing policy. Verify both the user's capability and the folders shared with them.
## 4. Review public delivery separately
Before publishing a Site, select only the folders and catalogs intended for its audience. Keep private operations material outside the public documentation tree. In **Settings**, review visibility and the sign-in options; **Public only** removes registration from open documentation sites.
A repository can remain private while selected imported documentation is published. Referenced screenshots become part of that published content, so use fictional examples without credentials or private customer records.
## Tips for a smooth setup
Match each action to its permission at the intended scope, and confirm the workspace has the feature enabled. For a custom Agent, configure the selected content and permitted actions as well as its written instructions.
Use [People, Groups and Workspaces](https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca360) to prepare a member invitation. For public content, follow [Publish an academy](https://honen-academy.honen.com/docs/6ab35eebda8e0901468ca397).
## Plan single sign-on and learner identity
Source: https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870
Give people a familiar route into Honen with the identity system your organization already uses. Choose the sign-in flow, decide how new learners join, and test the experience before rollout.
## Choose a sign-in path
| Your starting point | Honen setup | Guide |
| --- | --- | --- |
| Google Workspace, Microsoft Entra ID, Okta, Auth0, Keycloak, or another OIDC provider | OpenID Connect | [Connect an identity provider](https://honen-academy.honen.com/docs/6ab38b0a3b82ff9f26dee84e) |
| Your own authenticated application or customer portal | A short-lived assertion signed by your backend | [Launch with Signed JWT](https://honen-academy.honen.com/docs/6ab38b0f3b82ff9f26dee857) |
| A learner launches training from an LMS | The LMS integration establishes the learning launch and identity | [LTI 1.3](https://honen-academy.honen.com/docs/6ab3767678ce9f17182796a9), [SCORM](https://honen-academy.honen.com/docs/6ab3767978ce9f17182796d7), [Google Classroom](https://honen-academy.honen.com/docs/6ab3767578ce9f17182796a2), or [cmi5](https://honen-academy.honen.com/docs/6ab3767378ce9f1718279699) |
Open **Organization → Integrations → Identity & SSO** in the intended team workspace. Administrators need **Manage integrations** permission to configure the connection. Agree the provider-side application and rollout audience with your identity administrator.
## Plan for a SAML-based identity environment
Many organizations use one identity provider for both SAML and OpenID Connect applications. For Honen, have your identity administrator configure an **OIDC confidential web application** in that provider and use the Honen callback URL. The OIDC guide includes the provider choices and exact connection fields.
If your organization's requirements specify SAML assertions or SAML-only application registration, agree the integration approach with the Honen team before rollout. Share the provider, intended audience, provisioning needs, and required application protocol so the setup can be planned precisely.
## Choose how people join
- **JIT provisioning on:** a new email can create a real Honen account and join the configured workspace during sign-in.
- **JIT provisioning off:** arrange the person's Honen account and workspace membership before the first sign-in.
- **Default member role:** choose **Member** for learners or **Instructor** for people who need the instructor role. Review your workspace's role permissions separately.
For planned cohorts, create the [group](https://honen-academy.honen.com/docs/6ab38b133b82ff9f26dee860), add the right members, and prepare [assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d). Identity, group membership, and assignment requirements are distinct parts of the rollout.
## Understand first-time account linking
For a person who already has a Honen account with the same email, the first SSO launch can ask them to sign in to that exact account and confirm the identity connection. Returning sign-ins use the established provider identity.
Ask a test user to finish the complete linking flow, return to the intended workspace, and open an assigned course. This checks the experience a real learner will encounter.
## Choose the session scope
The usual SSO session is scoped to the connected workspace. This gives learners a focused entry point for that organization's learning.
Use **Allow account-wide session requests** only when your rollout needs a broader account experience. An account-wide session requires the client to request it, the workspace setting to allow it, and the user to approve that identity. Keep the ordinary workspace scope for a dedicated workforce or customer-learning launch.
## Manage the connection over time
Assign an owner for provider configuration, credentials, and test accounts. Keep a record of the issuer, intended workspace, application owner, role choice, and first successful learner test. Rotate credentials using the connection's controls and retest the launch.
Use the connection's enabled state to control new sign-ins. When retiring a connection, plan account access and session revocation as part of the change: disabling new sign-ins and ending existing sessions are separate actions.
Continue with [OIDC setup](https://honen-academy.honen.com/docs/6ab38b0a3b82ff9f26dee84e), [Signed JWT setup](https://honen-academy.honen.com/docs/6ab38b0f3b82ff9f26dee857), and [Access and roles](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca353).
## Connect an identity provider with OIDC
Source: https://honen-academy.honen.com/docs/6ab38b0a3b82ff9f26dee84e
Connect your organization's identity provider so learners can enter Honen using their existing sign-in. Honen offers presets for Google Workspace, Microsoft Entra ID, Okta, Auth0, and Keycloak, plus **Generic OIDC**.
You need **Manage integrations** permission in a team workspace and someone who can register an application in the identity provider.
## 1. Register Honen with your provider
1. Open **Organization → Integrations → Identity & SSO**.
2. Under **OpenID Connect**, copy the **OIDC callback URL**.
3. In your provider, create a **confidential web application** using the authorization-code flow.
4. Register the copied callback as the application's redirect URI. Use the exact value shown in your workspace.
5. Include the `openid`, `profile`, and `email` scopes. Configure the provider to supply a verified email and a stable subject identifier.
6. Obtain the application's issuer URL, client ID, and client secret. Assign the intended test user or audience in the provider.
For the Honen production host, the callback is `https://honen.com/api/auth/sso/oidc/callback`. Copying it from the screen keeps your setup aligned with the environment you are using.
## 2. Add the connection in Honen
1. Choose **Add OIDC connection**.
2. Enter a **Connection name**, such as “Northstar workforce.”
3. Select the matching **Provider** preset.
4. Enter **Issuer URL**, **Client ID**, and **Client secret** from the provider application.
5. Review **Scopes**, which starts with `openid profile email`.
6. Choose **Default member role** and whether to use **JIT provisioning**.
7. Review **Allow account-wide session requests** according to your [identity rollout plan](https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870).
8. Choose **Add connection**.
The screenshot shows the setup fields before credentials are entered. Supply the values from your own provider application when configuring your connection.
## Provider issuer examples
| Provider | Issuer form |
| --- | --- |
| Google Workspace | `https://accounts.google.com` |
| Microsoft Entra ID | `https://login.microsoftonline.com/{tenant-id}/v2.0` |
| Okta | The exact issuer from the chosen Okta authorization server |
| Auth0 | The issuer for your Auth0 tenant or configured custom domain |
| Keycloak | `https://{host}/realms/{realm}` |
| Generic OIDC | Your provider's exact discovery issuer |
Use the exact issuer advertised by the provider. For Entra ID, use the organization's tenant-specific issuer. The provider's discovery document supplies the authorization, token, and public-key endpoints.
## 3. Test the complete learner sign-in
1. In the saved connection card, choose **Test sign-in**.
2. Sign in as the intended provider test user.
3. Complete Honen account linking if prompted for an existing account.
4. Confirm the intended Honen workspace and member role.
5. Open a course assigned to that learner and return to the workspace.
6. Check the connection's **Last login** information.
Test both a new learner and an existing Honen account when both will be part of your rollout. Coordinate this with your identity administrator so the provider's application assignment and Honen's access policy match.
## 4. Maintain the connection
- **Enable or pause sign-in:** use the switch on the connection card.
- **Rotate the client secret:** create the replacement in your provider, choose **Rotate secret** in Honen, enter **Replacement client secret**, and select **Save secret**. Test sign-in again before retiring the old provider secret.
- **Adjust account-wide requests:** use the connection's **Account-wide requests** setting according to the approved rollout scope.
- **Retire the connection:** plan the replacement sign-in route, then use **Delete** when that connection should be removed. Review active-session handling as part of your offboarding process.
Review [SSO and identity](https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870) to plan provisioning, account linking, and session scope. For a portal that signs its own launch assertions, use [Signed JWT](https://honen-academy.honen.com/docs/6ab38b0f3b82ff9f26dee857).
## Launch Honen from your portal with Signed JWT
Source: https://honen-academy.honen.com/docs/6ab38b0f3b82ff9f26dee857
Give learners a direct route from your authenticated application into Honen. Your backend signs a short-lived assertion; Honen validates it against the public keys registered for your workspace.
This setup is for your application engineers and a Honen administrator with **Manage integrations** permission. For an identity provider's standard login flow, use [OpenID Connect](https://honen-academy.honen.com/docs/6ab38b0a3b82ff9f26dee84e).
## 1. Prepare the signing contract
1. Choose a stable issuer identifier for your application.
2. Generate an RS256 or ES256 key pair on your backend.
3. Give each public key a unique key ID, or `kid`.
4. Export the public keys as a JWKS document: `{"keys":[...]}`.
5. Keep the private signing key in your backend's secret storage.
Honen receives the public key. Your backend creates a fresh signed assertion for each launch.
## 2. Create the connection
1. Open **Organization → Integrations → Identity & SSO**.
2. Find **Custom Signed JWT → Connect signed SSO**.
3. Enter **Expected issuer** and the **Public JWKS**.
4. Choose **Default member role** and **Just-in-time provisioning**.
5. Review **Allow account-wide session requests** for your intended learner experience.
6. Select **Create connection**.
7. Copy the generated **Audience** and **Redeem URL** into your backend's configuration.
The example shows the form before registering keys. Use **Setup guide for your engineers** on the same page for the signing examples and launch contract.
## 3. Create a fresh launch assertion
Include these values in the signed JWT:
| Value | What to send |
| --- | --- |
| `iss` | The exact expected issuer registered in Honen |
| `aud` | The audience generated by Honen |
| `sub` | A stable user ID from your system |
| `email`, `email_verified`, `name` | Current email, boolean `true`, and display name |
| `iat`, `nbf`, `exp` | Integer timestamps; expiration no more than 60 seconds after issue time |
| `jti` | A unique random identifier for this launch |
| `course_id` | Optional course to open, available in the connected workspace |
| `session_scope` | `workspace` for the usual focused launch; `account` when approved for that identity |
Use the registered `kid` and supported signing algorithm in the JWT header. Generate a new assertion for every launch, including retries.
## 4. Launch and verify
1. Have the browser submit an HTML form to the saved **Redeem URL**.
2. Use `POST` with `application/x-www-form-urlencoded` and an `assertion` field containing the signed JWT. HTML-escape the value when generating markup.
3. Let Honen redirect to the selected course or workspace home.
4. Complete account linking if the learner already has a matching Honen account and is prompted to confirm it.
5. Check the workspace, role, and intended course access with a test user.
6. Return to the integration and inspect **Last successful launch**.
Your portal authenticates the user before it signs an assertion. Review [SSO and identity](https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870) to align provisioning, account linking, and session scope with your rollout.
## 5. Rotate keys and manage access
1. Generate a new key pair and unique `kid`.
2. Add the new public key alongside the existing key in **Public JWKS**.
3. Choose **Save and rotate keys**.
4. Deploy your backend signer using the new key.
5. Verify a fresh launch, then remove the old public key after the maximum assertion lifetime and your planned transition window.
Use the connection switch to manage new launches. **Revoke all keys** disables the connection and clears its registered keys; existing sessions are managed separately.
For learning progress or reporting in your portal, configure a separate [Connector API](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e) integration. SSO establishes the learner's session, while the API provides the learning data your application is permitted to read.
## Analytics and Reporting
Source: https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e
Use **Analytics** to move from organization-wide activity to a group, course, or learner. The screenshots show the fictional Northstar demo workspace.
## 1. Review monthly learning activity
1. Open **Analytics** from the workspace navigation.
2. Locate **Monthly activity**.
3. Choose the **Reporting month**. The current month is labeled **Month to date**.
4. Compare **Started** and **Completed** for **Learner MAU** and **Courses**.
5. Use the information buttons beside a metric to read its definition before comparing numbers.
A month-to-date result covers the current month so far. Compare course counts with course counts and unique learner counts with unique learner counts.
## 2. Narrow the investigation
1. Review **Members**, **Course completions**, **Needs attention**, and **Time to complete**.
2. Use the **Groups** table to compare cohorts.
3. In **Courses**, choose **Most completed**, **Least completed**, **Highest score**, **Lowest score**, **Most enrolled**, or **Least enrolled**.
4. Review **Member-initiated learning** separately from assigned course performance.
5. In **Learning modes**, switch between **Time used** and **People used**.
To focus on a single cohort, open **My groups**, choose the group, and select **Analytics**. Its member table offers search, membership, sort, and score filters. Course completion should be interpreted alongside the content and completion rules assigned to that cohort.
## 3. Ask an analytics question
Open the **Workspace Assistant** from the page and describe the scope and period you need. For example: “Summarize monthly learning activity for this workspace and explain what each metric counts.” Review the sources and the returned scope before using the result.
Use the [analytics question library](https://honen-academy.honen.com/docs/6ab38b073b82ff9f26dee845) for ready-to-adapt questions covering progress, assignments, assessment answers, learning modes, projects, and retention. Name the intended cohort so the answer stays useful to the people managing that program.
## 4. Review creation activity
Find **Course creation** on the analytics page. Review monthly active creators and the **Started** and **First published** counts for Courses, Assessments, and Atoms. Opening or editing an existing course is different from a first publication.
## 5. Build a saved custom report
Keep the answers you use regularly on your dashboard. A custom report turns a plain-language question into a saved widget that can refresh as learning activity changes.
1. Return to **Dashboard** and find **Custom Reports**.
2. Choose **Add widget** to open **Add a custom report**.
3. Describe the audience, metrics, and presentation you want. For example: “Create Northstar learning activity. Show total members and a table of courses with enrolled learners, completed learners, and completion rate. Explain what each metric counts.”
4. Choose **Build it**. Review the generated widget and its metric definitions. The created widget is saved to the dashboard.
5. Open the widget’s options menu. Choose **Refresh now** to update the report, or **Edit with AI** to refine the question or presentation.
6. Review its refresh cadence. The example offers **Refresh every 30 minutes**; use the menu to manage the report’s update schedule.
7. Return to the dashboard to use the saved report alongside the standard course and member tables.
The example shows 25 members, 6 courses with activity, 112 enrollments, and 0 completions. Enrollments count learner–course relationships, so one person can contribute more than one enrollment.
## 6. Turn results into a next step
Compare **Needs attention** with the cohort’s [assignment requirements](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d). Ask the Workspace Assistant to focus on a course, group, or learner: “For this onboarding course, show the units and topics learners are struggling with, then summarize quiz and test performance.” Review the relevant activity or project submission before deciding whether learners need more practice, a clearer explanation, or a revised source.
For leadership or program reporting, specify the cohort and period in the report request. To combine learning records with approved business data, follow [Connect learning and business outcomes](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e#connect-learning-and-business-outcomes).
## Tips for a smooth setup
- **Compare loaded results:** let the report finish loading, then use its current values for your comparison.
- **Use the cohort’s completion criteria:** inspect its assignment requirements when interpreting completion.
- **Give reviewers the right access:** use a role with analytics access at the intended workspace or group scope.
For intake, employment, and government-format evidence, use [Funder and Compliance Reporting](https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca35b).
For the completion requirements behind a cohort's results, inspect its [assignments](https://honen-academy.honen.com/docs/6ab35ee9da8e0901468ca38d) and [curricula](https://honen-academy.honen.com/docs/6ab36166effafe59361d2350).
## Analytics question library
Source: https://honen-academy.honen.com/docs/6ab38b073b82ff9f26dee845
Turn learning activity into a useful next step. Open **Workspace Assistant** and ask a specific question about a workspace, group, course, learner, assignment, or assessment. Replace the example names with your own; the assistant uses the records your role can access.
## Start with a clear scope
1. Open the intended workspace and its **Analytics** page, or open a group and choose **Analytics**.
2. Open **Workspace Assistant**.
3. Name the course, group, learner, or assignment. Include the reporting month when asking for monthly activity.
4. Ask for the metric definitions alongside the answer, then follow the relevant course, learner, or assessment detail.
5. For an answer you want to revisit, [build a saved custom report](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e#5-build-a-saved-custom-report).
For example: “For the Product onboarding course in the Week one group, show unit completion, average test score, and tracked time. Identify the topics with the lowest completion and scores.”
## Workspace activity and creation
| Ask | What the answer measures |
| --- | --- |
| “Summarize our monthly activity for September 2026.” | Learners starting and completing learning, course activity, active creators, content starts, and first publications. |
| “How many members, courses, and completions do we have?” | Workspace headline counts. |
| “Compare performance across our courses.” | Per-course performance rows. |
| “Show assigned and completed course counts for each learner.” | Learner roster and completion counts. |
| “Who has assigned coursework but no completions?” | The needs-attention cohort. |
| “Who has the highest completion ratio?” | Learners ranked by completed versus assigned work. |
Monthly reporting uses calendar months in the America/New\_York timezone. The current month is month to date. Ask for a month in `YYYY-MM` form when you want an unambiguous period.
## Course, unit, and topic progress
| Ask | Scope and detail |
| --- | --- |
| “Summarize class performance in Product onboarding.” | A course-wide performance rollup. |
| “List every assigned learner's progress, scores, and status in Product onboarding.” | Course detail; optionally narrow to a group. |
| “Compare the units in Product onboarding by completion, test score, and time.” | Per-unit completion, average test score, and average tracked time; optionally a group. |
| “Which topics in the Getting started unit need attention?” | Topic completion, average quiz score, and tracked time; optionally a group. |
| “Rank the hardest topics in Product onboarding.” | Topics with low completion and low scores; optionally a group and a result limit. |
| “Show Jordan's unit, topic, and activity progress in Product onboarding.” | One learner's breakdown, including tracked time compared with the team average. |
| “Show Jordan's quiz and test scores and activity completion.” | Learner performance across courses, or within a named course. |
| “List course completion events for the Week one group.” | Completion records; can also filter by course or learner. Ask for all pages when exporting a complete list. |
## Assignments and timely support
| Ask | Scope and detail |
| --- | --- |
| “Summarize the Week one onboarding assignment.” | Assignees, completion, weak units, and struggling topics for one assignment. |
| “Who has not started Product onboarding, is behind, or has low test scores?” | Course risk groups, optionally narrowed to a group. You can specify progress and score thresholds. |
| “Which incomplete assignments are past their due date?” | Overdue assignments; optionally restrict by course or group. |
| “Who takes the most and least tracked time to finish?” | Average tracked completion time by learner, optionally within a group. |
| “How many learners were active each day over the last seven days?” | Daily training activity, optionally for a group. |
Tracked learning time measures recorded activity. Use it alongside completion and assessment results when planning support.
## Quizzes, tests, and individual answers
| Ask | What to name |
| --- | --- |
| “Show the score distribution for the Getting started unit test.” | A specific unit test. |
| “Show the score distribution for the Product basics quiz.” | A specific quiz activity. |
| “Which questions did this cohort miss most often?” | The quiz or test, and optionally the group. Results rank question-level wrong-answer rates. |
| “Show Jordan's answers on this test attempt.” | Learner, quiz or test, and optionally a particular attempt. |
Open the underlying question or attempt to pair aggregate scores with the learner's actual response.
## Practice modes and projects
| Ask | Scope and detail |
| --- | --- |
| “Which learning modes does this cohort use?” | Percentage of learners using each modality; optional course, learner, or group scope. |
| “How much time does this cohort spend in each learning mode?” | Recorded time by modality with the same scope options. |
| “Compare scenario completion, attempts, and best scores in Product onboarding.” | Scenario project results for a course, optionally a unit or group. |
| “Show Jordan's scenario evaluation and transcript.” | Learner and scenario project; optionally a particular attempt. |
| “Show Jordan's submitted project and rubric result.” | Learner and project; includes applicable form responses and submission details. |
| “Show the creator-review feedback and acknowledgment for this submission.” | Creator and video-review project, including the review conversation. |
## Explore retention and learner-initiated learning
Use the analytics page for additional visual views:
1. On workspace **Analytics**, review **Member-initiated learning** to understand learning learners started themselves.
2. Open a course's analytics and review its retention card when retention is enabled. Compare the completion baseline with later checks, answered/passed/skipped checks, and the goals most frequently missed.
3. Open a learner within a course to review goal mastery. The goal grid shows the latest evidence across quiz, test, refresher, and flashcard activity.
4. Use these patterns to choose a topic to reinforce or an activity to revise.
## Keep a recurring answer on the dashboard
Try this in **Dashboard → Custom Reports → Add widget**:
> Create a learning activity report with total members and a table of courses showing enrollments, completions, and completion rate. Explain each metric and keep learner-level details out of the summary.
Choose **Build it**, review the saved result, and use **Refresh now** or **Edit with AI** from its options. See [Analytics and Reporting](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e) for the complete walkthrough and refresh controls.
For approved business-data joins, follow [Connect learning and business outcomes](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e#connect-learning-and-business-outcomes).
## Funder and Compliance Reporting
Source: https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca35b
Turn training records into an evidence pack for your funder or reporting team. Funder Reporting brings learning activity together with imported intake and employment data, so you can review the required fields before submitting through your organization's filing process.
## 1. Choose the scope and format
1. Open **Organization → Funder Reporting**.
2. Stay on **Reports**.
3. Set **Report on** to the whole workspace or a particular group.
4. Select the report format you need.
The available formats include **WIOA Title I · PIRL (WIPS)**, **California ETP · evidence pack**, **WIOA Title II · NRS tables**, **Registered Apprenticeship · RAPIDS**, **Perkins V**, and **State ETPL**. Choose the format that matches your reporting task. Evidence packs organize records for review; filing formats should be checked against the destination's current requirements before submission.
## 2. Review readiness
After choosing a format, inspect **What \[report\] needs**. The screen separates **Honen fills automatically** from **You still need to provide**. Enrollment, completion, training time, and curriculum evidence come from delivery records. Intake demographics, employment, wages, or retention may need approved external records.
Use **Import the missing data** to complete the required fields, or inspect the linked learner list. Choose **Generate with blanks** for a working draft, then complete the required data before submission.
## 3. Prepare an import
1. Open **Imports**.
2. Download **Blank template** or **Filled example** to understand the input shape.
3. Prepare an authorized CSV. Learners are matched by email.
4. Choose **Drop a CSV or click to browse** to select the file.
5. Review the import result before generating another report.
Prepare the CSV from the provided template, using email to match learners. The importer filters SSN and TIN columns. Use **Member data** to review and maintain reporting records with the appropriate reporting permission.
## 4. Validate the output for its destination
Check the selected group, report period where applicable, missing fields, and the destination's current file layout. The PIRL and RAPIDS cards specifically call for reconciling the field order with the current layout. Keep evidence exports separate from the actual filing process your agency or funder requires.
## Tips for a smooth setup
Use approved intake and employment records to complete missing fields. Recheck the learner email match when reviewing imported records. Access to this area is controlled by **Manage funder reporting**, which includes sensitive learner reporting records.
Use [Analytics and Reporting](https://honen-academy.honen.com/docs/6ab35edfda8e0901468ca34e) for activity and course-performance investigation. Manage the reporting cohort through [People, Groups and Workspaces](https://honen-academy.honen.com/docs/6ab35ee1da8e0901468ca360).
## Agents
Source: https://honen-academy.honen.com/docs/6ab35edbda8e0901468ca336
An Agent is a custom AI assistant that belongs to a workspace. It has one prompt, one set of guardrail instructions, one access policy, and one or more channels where people can talk to it. Configure the Agent once, then set up the supported Slack, Microsoft Teams, iMessage, or website-embed deployments for your audience.
This is what turns a knowledge base from something people study into something that answers them at their desk.
## Try it step by step
Follow [Create a knowledge Agent](https://honen-academy.honen.com/docs/6ab35edcda8e0901468ca33e) to build a folder-scoped guide. Then use [Inspect Agent logs and analytics](https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a) to inspect execution evidence.
## Anatomy
| Part | What it controls |
| --- | --- |
| Prompt | The Agent's role, goals, tone and response style |
| Guardrails | Behavioral instructions for boundaries; access policy enforces capabilities |
| Connector | The maximum data and actions available to the Agent |
| Identity mode | Whether it acts as a service, as the person asking, or both |
| Channels | Slack, Microsoft Teams, iMessage, website embed |
| Status | Draft, active, disabled or archived |
## One Agent, separately configured channels
Channels are deployments of one Agent and share its prompt, guardrail instructions, model, and Connector policy. Each deployment has its own credentials, routing, identity mode, and conversation context. Choose and configure the channels your audience uses, then review their conversation and identity settings.
- **Slack.** Mention the Agent in a channel or send it a direct message. Replies stay in the thread.
- **Microsoft Teams.** Private chats and standard channel threads. Mention it once to start a thread and it keeps answering there.
- **iMessage.** Text a question and get an answer grounded in the current material. One active iMessage Agent per workspace.
- **Website embed.** Drop it into your own site as an iframe, public or authenticated.
## Permissions are separate from instructions
**Honen command access is checked against the Agent's Connector policy.** Prompts describe intended behavior; the policy sets the available Honen capabilities and resources and is enforced server-side.
Guardrails are stored separately and added to the system prompt as instructions that override conflicting requests. They guide model behavior; they are not a substitute for restricting private data and actions in the Connector policy.
Three quick profiles cover most cases:
| Profile | Access |
| --- | --- |
| Answer questions | Read approved knowledge and courses |
| Build courses | Read knowledge, create courses, edit course content |
| Run learning operations | Read people and analytics, manage assignments |
Beyond these, access is granular per capability: knowledge base (read, write or admin), courses, course creation with daily and lifetime caps, people, analytics, assignments, groups, monitors and alerts, workspace curation, workspace settings, and the integration audit log. Knowledge Base access can use document, folder, tag, and per-path rules; course access has its own course allowlist. These resource controls do not apply uniformly to every management capability. For overlapping Knowledge Base path rules, the most specific wins, allowing a read-only document inside a writable folder.
The recommended approach is the smallest policy that supports the Agent's job, adding capabilities only when a real workflow needs them.
## Identity
- **Service.** The same access for every sender, no workspace membership required. For public support and anonymous audiences.
- **Hybrid.** Links a sender to a workspace member where possible and falls back to the service identity otherwise.
- **Member gated.** The sender must resolve to a current workspace member. This is the mode for internal assistants touching private information, and membership is re-checked on every session.
The Connector remains the ceiling in every identity mode. Identity narrows access; it never widens it.
## Embedding on your own site
A public Agent takes three steps: enable public access, list the website origins allowed to embed it, and copy the generated iframe. For signed-in users, your server mints a short-lived Agent URL for the current person, so the assistant knows who it is helping without you managing another login. The handoff uses a short-lived, single-use ticket. Keep generated handoff links out of screenshots, logs, and public documents. The server key stays on your server.
## Lifecycle
Agents have draft, active, disabled, and archived states. Disabled pauses the Agent while retaining its configuration. Archived Agents cannot be restored. Archiving disables deployments, revokes embed sessions and keys, invalidates unused tickets, and releases eligible channel routing. An unshared Agent-managed Connector is revoked; an explicitly attached shared Connector is not automatically revoked. Conversation context is separated by Agent and channel/thread identity.
Permissions are enforced server-side. Stored provider credentials are sealed and omitted from ordinary configuration responses. Channel handlers validate provider requests, embed sessions check allowed origins, and member-gated embed sessions recheck current workspace membership.
## Suggested starting policies
| Agent | Policy |
| --- | --- |
| Internal knowledge assistant | Answer questions, member gated |
| Public support Agent | Answer questions, service, approved public knowledge only |
| Course creation Agent | Build courses, member gated |
| Operations Agent | Run learning operations, member gated |
## Boundaries
- Slack and Teams channels remain in draft until provider setup is complete. Selecting a channel is not the same as activating it.
- A custom Teams Agent requires an Entra application, an Azure Bot registration and a Teams app package, so it involves IT. Follow the setup guide for the selected channel; availability depends on provider configuration.
- Only one Agent can be the active iMessage responder per workspace at a time.
- A workspace-wide Slack or Teams installation is not automatically attached to every custom Agent. The default workspace assistant and a custom Agent are separate things.
- Agent-managed access policies cannot be shared between Agents; reusing one means attaching an existing Connector explicitly.
## Agent Runs
Use [Inspect Agent logs and analytics](https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a) to review recorded turns across supported channels and automations. Available details include the conversation, tool activity, model, tokens, and cost.
## Course update proposals and Automations
Agents can be granted permission to propose changes on selected courses. They prepare a draft for course editors or a catalog’s Publishing reviews queue, where a person can inspect the submitted version before approval. The access policy remains the ceiling, including for unattended runs.
[Automations](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331) run an Agent on a schedule, by webhook, or manually. Choose the Agent, write instructions, and set the trigger and time zone. Pause from the list, Run now, or open Runs for results and conversations. The automation inherits the Agent’s model and permissions.
Slack and Microsoft Teams work continues through long course-creation and editing tasks, with progress updates in the conversation and a final reply when the result is ready. Shared course links open the learner experience. Generated files and supported attachments stay part of the conversation.
Complete the setup guide for each selected channel, then open a conversation as a member of its intended audience.
## Create a knowledge Agent
Source: https://honen-academy.honen.com/docs/6ab35edcda8e0901468ca33e
Build an assistant that answers from a specific set of approved documents. This walkthrough uses **Northstar Onboarding Guide**, a fictional demo Agent, and the **Product onboarding** folder.
## 1. Name the Agent and describe its job
Open **Agents → Create agent**. In **Overview**, enter a name, a short description, and your **Instructions**. Tell it what to answer, which sources to use, and how to handle missing information.
> Answer onboarding questions using only approved demo documentation. Cite the source for factual answers. If the source does not answer a question, say what is missing. Do not change content or contact people.
The screenshot shows the example after creation, with **Status → Draft**. Expand **Guardrails** for additional limits and **Model** to review the selected model. Never put credentials into either instruction field.
## 2. Choose the access policy
Open **Access → Set access for this agent**. The presets provide starting points: **Answer questions**, **Build courses**, and **Run learning operations**. For a document-only guide, expand **Customize permissions** and keep **Knowledge Base → Read**.
Under **Folders / documents**, select the approved folder. Our example selects **Product onboarding**. A folder includes its children and future files added inside it. Selecting an individual document includes only that document.
**With no document, folder, group, tag, or path restrictions, enabled Knowledge Base access covers the workspace.** An empty folder selection alone is not a restriction. A name or instruction mentioning a folder does not restrict access by itself; select the folder in this control.
Turn off **Courses** and **Course Creator** if they are unnecessary. Review **People & learning** and **Workspace** too. In the example, People, Analytics, Assignments, Groups, Radar, Explore, Workspace settings, and Integration audit are off. **Workspace Assistant** is required for the Agent to run its approved tools.
## 3. Review channels
Open **Channels**. Honen offers Slack, Microsoft Teams, iMessage, and Website embed. Leave them unchecked while preparing an internal draft. Channel setup is completed after saving the selected channel.
## 4. Create and verify the draft
Choose **Create agent**. A confirmation page shows the Agent was created and whether channels need setup. Open **Edit agent settings**, set **Status → Draft**, and choose **Save changes** if you are still preparing it.
Reopen **Access** to verify the selected folder and read-only permission survived saving. The saved draft is ready for a controlled automation test. Configure a channel when you are ready to offer it to your audience.
## If something looks wrong
- **Answers mention unrelated material:** check the folder allowlist and any inherited connector; instructions alone are not the access policy.
- **A folder is missing:** confirm the workspace and your permission to that Knowledge Base item. Clear the picker search to browse available items.
- **The Agent cannot edit a course:** a read-only document guide intentionally lacks course editing access.
- **No chat channel is available:** creating the Agent does not finish a channel's separate connection and deployment setup.
Then run a small [automation test](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331) or inspect existing [Agent logs](https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a). For identity and channel differences, read [Agents](https://honen-academy.honen.com/docs/6ab35edbda8e0901468ca336).
## Inspect Agent logs and analytics
Source: https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a
Understand how your Agents help people and where their time goes. Use logs to follow an individual answer and analytics to review usage, performance, and cost over time.
## 1. Open the logs
Go to **Agents → Logs**. Each row represents a turn. Review its time, Agent, model, status, duration, tokens, and cost.
Select an Agent or status, choose a date range, or search the prompt, response, user, or error. The **Custom** range exposes start and end dates.
## 2. Narrow the investigation
Open **More filters** for **Channel**, **Model**, **User**, and **Error stage**. Clear unnecessary filters if you cannot find the turn.
## 3. Open the turn
Choose a row's trace link. The detail page shows a run summary, conversation, execution timeline, and expandable **Technical metadata**. Where available, **View run** opens the associated automation run.
For an automation, open **Runs**, select **Show test runs** when needed, and choose a run to read its answer and expand its tool activity. The example below summarizes an approved onboarding checklist and cites the source.
## 4. Review trends
Open **Agents → Analytics**. Filter by Agent, status, and date range. The cards summarize Runs, Unique users, Tokens, Cost, Success, and p95 latency. Use **Runs**, **Users**, **Tokens**, **Cost**, or **Failures** above the activity chart to change the measure.
Choose **View logs** to investigate individual turns behind the summary. A new draft Agent with no executions has no turns to inspect yet.
Use the conversation and tool activity to understand the result, then open the referenced document or course to continue your work. [Automations](https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331) explains test runs; [Agent access](https://honen-academy.honen.com/docs/6ab35edcda8e0901468ca33e) explains which actions a run can attempt.
## Automations
Source: https://honen-academy.honen.com/docs/6ab35edada8e0901468ca331
Give an Agent a repeatable task. An automation supplies the instructions and trigger; the selected Agent supplies its model, tools, and permissions.
The example uses **Northstar Onboarding Guide** to summarize an approved checklist and cite its source. Start with a manual task, review its answer, then choose the recurring schedule that fits your team.
## 1. Start from the Agent
Open your Agent's **Overview** and choose **Automations → Create new**. The Agent is preselected. You can also open **Agents → Automations → New automation** or choose a starter such as **Knowledge base drift**.
## 2. Write one clear task
Give the automation a name. In **Instructions**, describe the input, work, output, and limits. Use `@` to reference a Knowledge Base document or folder the Agent can access.
> Read the Customer onboarding checklist in Product onboarding. Summarize the first three tasks and cite the source. Keep this task read-only.
Select **Northstar Onboarding Guide** in **Agent**. For this example, its Knowledge Base access is **Read**, limited to **Product onboarding**; its other content and management permissions and all channels are off. See [Create a knowledge Agent](https://honen-academy.honen.com/docs/6ab35edcda8e0901468ca33e) to set up the example Agent.
## 3. Choose a trigger
For a task you will start yourself, select **Manual**. The editor explains that it runs only when you start it and displays **Run now**. Keep **Active** off while preparing the task.
For recurring work, select **Scheduled**, then choose **Frequency**, **Time**, and **Time zone**. Review **Next runs** to confirm the schedule is what you intend.
**Webhook** is the third trigger option. Its editor says to save the automation to obtain its URL and signing secret. This is an incoming automation trigger, separate from outbound webhooks under **Developers**.
## 4. Save the automation
Choose **Create**. The saved automation page gives you its settings, test action, and run history.
The saved page has **Settings** and **Runs** tabs and a **Save** button. Confirm the Agent, instructions, **Manual** trigger, and **Active** switch are still correct.
## 5. Test and check the answer
Review the instructions and Agent access, then choose **Test** once. Test saves the current form, executes the Agent’s tools, and opens the run. Automatic result notifications are skipped for test runs. This example only reads the checklist.
Wait for **Succeeded**, then read the result. Our test returned the three **Before the welcome call** tasks: confirm the customer's learning goal, gather approved product guides, and prepare a short course and review its learner preview. Its source is **Customer onboarding checklist** in **Northstar Academy › Product onboarding**.
Open the named document in **Knowledge Base** and compare the answer with the source. Expand **Used 1 tool** or **Used 2 tools**, then **Show details**, to inspect what the Agent actually did. In this example, it searched the Knowledge Base, fetched the checklist, and read the returned text.
## 6. Find the test again
Choose **Back**, open **Runs**, and check **Show test runs**. Select the successful test to reopen its transcript. Tests are hidden from this list until you select that option.
Return to **Settings** to confirm **Active** is still off. Start a manual automation with **Run now** whenever you need its result. Activate a recurring task only after reviewing its output and intended effects.
## Keep recurring work useful
Review **Runs** to see the task’s status, summary, and conversation. Adjust instructions as your process changes, and turn **Active** off to pause scheduled triggering.
Choose **Knowledge base drift** for a report of changed sources and affected courses, **Nudge overdue learners** for a follow-up task, or **Sales calls to courses** for course-building work. Adapt the starter instructions and give the selected Agent the required access.
For course maintenance, select the relevant sources and grant permission to propose changes on the intended courses. Ask the Agent to prepare a proposal for the course editor or catalog’s publishing review queue. Your reviewers inspect and approve the changes through the normal [publishing workflow](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381).
For recorded execution details, use [Inspect Agent logs and analytics](https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a). Keep the [Agent access policy](https://honen-academy.honen.com/docs/6ab35edcda8e0901468ca33e) limited to the resources and actions the task needs; test instructions do not disable write tools.
## Integrations and MCP
Source: https://honen-academy.honen.com/docs/6ab35ededa8e0901468ca347
Honen has separate connections for importing source material, letting its assistant call external tools, and letting another AI client work with Honen. Choose the connection for the direction you need.
| Connection | Purpose | Direction |
| --- | --- | --- |
| Content source | Import selected documents and refresh their Knowledge Base copies | Source system into Honen |
| External MCP server | Give the Honen assistant tools from another system | Honen into external tools |
| Honen MCP or Connector API | Let an approved client use Honen commands | External client into Honen |
| Agent channel | Deliver a configured Honen Agent through chat or an embed | Honen and the channel audience |
Start with [Import files and web links](https://honen-academy.honen.com/docs/6ab36192effafe59361d23d7), [GitHub sync](https://honen-academy.honen.com/docs/6ab35ef6da8e0901468ca3cc), or [Connect an AI client](https://honen-academy.honen.com/docs/6ab360ffeffafe59361d2244).
## 1. Bring content into the Knowledge Base
Connect Google Drive, OneDrive, SharePoint, Notion, Confluence, Document360, GitHub Documentation, or Granola, or import website pages and YouTube transcripts. Availability depends on workspace configuration and provider setup. Each adapter supports its own content types and scope; a selected folder imports supported descendants subject to crawl and processing limits.
Use **Content sources** to connect an account or enter the credential the provider requires. Return to the Knowledge Base add menu to select content. Websites and YouTube use URLs; Granola uses an API key. Follow the import status to see when the selected content is ready.
Manual Knowledge Base imports accept supported PDF, Word and PowerPoint documents, images, and video up to 5 GB per file. Markdown and plain-text imports accept up to 5 MB of text. This is the Knowledge Base import limit; other upload surfaces have their own limits. Supported screen recordings can be processed into visual walkthroughs. Review the generated steps and screenshots before using them.
### Refresh timing and deletions
Connected sources refresh on their supported schedules. Timing depends on the provider and the amount of content being processed; website sources have a six-hour minimum scheduled refresh interval. Choose **Refresh** when you want to check for a recent change, then open the updated document.
Refresh uses the credential stored with the source connection. Personal connections use the linked owner's account; workspace-scoped connections use the shared workspace credential. The provider must still allow that credential to read the source. Honen's own sharing controls determine who can read the imported copy.
A complete folder refresh also reconciles documents removed from the source. Directly linked documents retain their last imported copy when source access changes. Manage the Honen copy and its sharing settings when retiring material.
Source imports are one-way: editing the Knowledge Base copy does not push that edit to the connected source, and a later source update can replace local edits. This is separate from external MCP tools, which may be authorized to write to the original system.
### Images and scanned material
Honen copies supported referenced images into workspace storage during sync. Use accessible source assets and open the imported document to review the images alongside their text.
Supported scanned documents go through text extraction. Check the extracted text, especially tables and image-heavy pages, before using it as course material.
### Course materials are snapshots
Attaching a Knowledge Base document to a course captures a version snapshot. The materials panel can flag a newer source version and offer **Refresh from KB**. That refresh replaces the attached material; it does not automatically rewrite or publish existing lessons and questions. Review source changes and revise the course separately. See [Organize and use source material](https://honen-academy.honen.com/docs/6ab35ef9da8e0901468ca3d9).
## 2. Let Honen call external tools
The MCP catalog includes Linear, Notion, Granola, HubSpot, Slack, Google Calendar, Google Chat, Google Drive, Gmail, and Google Contacts. These connections add tools to the assistant; choose a native content source when you want a synced Knowledge Base collection. Available operations depend on the provider, your authorization, and the selected connection.
You can also configure a custom MCP server using a supported remote transport and authentication flow. Complete its authentication flow, inspect the available tools, and try the operation you want to use.
Before using an external tool in an automation, confirm the connection is active and that the Agent can access the required operation. Review the run result to see the returned data and completed work.
## 3. Connect an outside AI client to Honen
- **Personal sign-in:** the client uses the signed-in person's Honen permissions, further limited by its granted OAuth scopes and the tool's access checks.
- **Scoped Connector:** an administrator configures permitted capabilities and resources, such as read access to a specific folder. An enabled Knowledge Base capability with no resource restrictions can cover the whole workspace.
The OAuth-protected Streamable HTTP endpoint is `https://honen.com/api/mcp/mcp`. Discovery is available at `https://honen.com/.well-known/mcp`, and the Server Card at `https://honen.com/.well-known/mcp/server-card.json` describes the supported surface. Clients supporting Honen's MCP App can display its interactive course preview; other clients may only expose the tools and returned links.
Follow [Connect an AI client](https://honen-academy.honen.com/docs/6ab360ffeffafe59361d2244) for the setup screens or [API and OpenAPI](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e) for HTTP commands. Both require the relevant permissions; an API credential is not an LMS or xAPI credential.
## 4. Deliver an Agent through a channel
An [Agent](https://honen-academy.honen.com/docs/6ab35edbda8e0901468ca336) shares its instructions and Connector policy across its configured Slack, Microsoft Teams, iMessage, and website-embed deployments. Provider credentials, identity modes, and routing are configured per deployment. Follow the selected channel’s installation guide to activate the deployment.
## Review access and execution evidence
Knowledge Base path rules can narrow access, including a read-only document inside a writable folder. With rules configured, unmatched items are denied; with the flat policy, empty resource allowlists mean no resource restriction. Review the saved policy rather than relying on the Agent's written instructions.
Imported content follows Knowledge Base sharing permissions. Connecting a source does not by itself publish it, but importing into a shared folder can make that copy available to the folder's audience. Check the destination before importing private content.
Use integration audit records, document version history, and [Agent logs](https://honen-academy.honen.com/docs/6ab3610aeffafe59361d225a) to follow changes and review recorded conversations and tool activity.
Disable or revoke credentials you no longer need and review provider-specific revocation behavior. Credential lifetimes differ: a Connector can be created without an expiry, while short-lived delegated tokens have their own limits. Set an expiry where offered and keep ownership of each credential clear.
## Identity and LMS delivery
Use OIDC or Signed JWT to connect supported identity flows. For district identity or rostering requirements, confirm the supported setup with your administrator before planning a rollout. Follow [Single sign-on and identity](https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870) to choose and configure the learner sign-in flow.
For learning delivery, use [LMS Integrations](https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392). LTI launches, Deep Linking, roster sync, and grade passback depend on the selected platform's capabilities and configuration. SCORM, Google Classroom, and xAPI/cmi5 have separate setup and verification workflows.
## Keep sources connected
Review connection and sync status when the source account, ownership, or permissions change. Reconnect the authorized account when prompted, choose **Refresh**, and open an updated document to confirm the current source and images.
For workforce sign-in, start with [Single sign-on and identity](https://honen-academy.honen.com/docs/6ab38b1a3b82ff9f26dee870), then follow [OIDC setup](https://honen-academy.honen.com/docs/6ab38b0a3b82ff9f26dee84e) or [Signed JWT setup](https://honen-academy.honen.com/docs/6ab38b0f3b82ff9f26dee857). Use [Governance](https://honen-academy.honen.com/docs/6ab38b5e3b82ff9f26dee911) to align templates, Rules, Skills, and publishing approvals with your team's responsibilities.
## Connect an AI client to Honen
Source: https://honen-academy.honen.com/docs/6ab360ffeffafe59361d2244
Honen's **Connect MCP** page provides the endpoint and client-specific setup instructions. A personal sign-in connection uses your existing permissions. A scoped Connector is for access to a narrower set of content.
## 1. Open the setup guide
From **Dashboard → Quick Actions**, select **Connect MCP**. Review the explanation, then copy the **MCP endpoint**.
The endpoint is `https://honen.com/api/mcp/mcp`.
## 2. Select your client
Under **Pick your client**, choose **Cursor**, **Claude**, **Claude Code**, or **Other clients**. Follow the instructions shown for that client. The Cursor tab includes a copyable configuration block.
Add the endpoint in your client's MCP settings. When the Honen authorization window opens, review the requested access and account before allowing the connection. Return to the client and start with a read-only question about a document you can already open in Honen.
## 3. Use a scoped Connector when needed
Select **Open Connectors** from the setup page, then **New Connector**. Enter a descriptive name and expand **Customize permissions**. Select only the required capabilities and explicit folders or courses.
For a documentation reader, keep Knowledge Base access at **Read**, select the approved folder, and turn off unrelated capabilities. If there are no document, folder, group, tag, or path restrictions, the enabled Knowledge Base capability covers the workspace. Review all scope controls before creating anything.
Creating a Connector issues a credential; the form says its raw secret appears once. Store it securely and keep it out of documentation, screenshots, source repositories, and prompts.
## Confirm the connection
Ask the connected client to find a known document and cite it. Open the cited source and compare the answer. If the client cannot connect, check the endpoint, complete any pending sign-in, and confirm your current account can access the intended workspace. If connection succeeds but a document is unavailable, inspect permissions and connector scope.
For HTTP requests using the same Connector policy, see [API and OpenAPI](https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e). [Integrations and MCP](https://honen-academy.honen.com/docs/6ab35ededa8e0901468ca347) distinguishes incoming content sync from external tools the Honen assistant can call.
## Use the API and OpenAPI reference
Source: https://honen-academy.honen.com/docs/6ab3765c78ce9f171827961e
Honen's Connector API exposes workspace commands for courses, knowledge, learning, analytics, and other permitted resources. A Connector policy controls which commands and resources its credentials can access.
## Open or download the specification
- [Browse the academy API reference](https://honen.com/docs/docs/api-6ab3670c51fd2d748e6357ad).
- [Download the current OpenAPI JSON](https://honen.com/api/v1/openapi.json).
- [Connect an AI client to Honen](https://honen-academy.honen.com/docs/6ab360ffeffafe59361d2244).
The specification is generated from the live command registry. Import its URL into an OpenAPI-compatible client to inspect request schemas, authentication, and response shapes. The academy's imported reference is a snapshot; the JSON endpoint reflects the deployed API.
## Prepare a Connector
1. Open **Organization → Integrations** and the Connector/MCP controls.
2. Give the Connector a descriptive name and select the resources it needs.
3. Start with read access to the specific courses or Knowledge Base folders your integration will use.
4. Create and store the credential securely. Use its Bearer token from your server or trusted development environment.
The [AI client connection walkthrough](https://honen-academy.honen.com/docs/6ab360ffeffafe59361d2244) shows the related access setup. A Connector does not inherit unlimited workspace access.
## Make a request
Commands use `POST https://honen.com/api/v1/{domain}/{action}` with a JSON body. For example, a Connector with the corresponding analytics permission can request:
```bash
curl --request POST https://honen.com/api/v1/analytics/hero \
--header "Authorization: Bearer $HONEN_CONNECTOR_TOKEN" \
--header "Content-Type: application/json" \
--data '{}'
```
A successful response has `success: true` and a `data` value. Failures have `success: false` and an `error` object. Read each operation's schema rather than assuming every command accepts the same fields or pagination.
## Retry safely
Mutating commands support an `Idempotency-Key` header. Reuse the same key and body when retrying the same intended write. A conflicting or in-progress key can return 409; do not replace it with a new key until you understand whether the original action completed.
For asynchronous Knowledge Base imports, follow the returned job ID with `kb/import-status` until it reports `READY` or `FAILED`. For video walkthroughs, also inspect `walkthroughStatus` to follow visual processing separately from transcript extraction.
## Connect learning and business outcomes
Bring learning records into your reporting environment to compare training with approved operational measures, such as onboarding milestones or support readiness.
1. Define the learning cohort, reporting period, and business measure you want to compare.
2. Create a Connector with the required analytics access. Use `POST /api/v1/learning/completions` to retrieve completion events. Filter by `courseId`, `userId`, or `groupId` as needed.
3. Send `page` and `limit`, then advance pages until `pagination.page` reaches `pagination.totalPages`.
4. Keep the returned `userId`, `courseId`, `completedAt`, and `avgScore`. The response also includes learner name/email and course title for authorized reporting.
5. In your approved warehouse or BI workflow, map the Honen learner to the corresponding business-system record using a maintained identifier mapping. Align the reporting dates before comparing results.
6. Use `performance/student` for a learner’s course performance, or `learning/course-detail` for a course/group rollup, when you need more context than a completion event.
For example, join a fictional learner’s course completion date to their onboarding-milestone date to report time from training to that milestone. Keep the learning measure and business measure labeled separately so readers can interpret the relationship.
If you use an external CRM MCP connection, choose tools and scopes that expose the records needed for the analysis. [Integrations and MCP](https://honen-academy.honen.com/docs/6ab35ededa8e0901468ca347) explains external tool connections. The export-and-join workflow above works with your approved reporting system and its own data-access controls.
## Check your setup
| Status | Check |
| --- | --- |
| 400 | Valid JSON and the operation's expected body |
| 401 | The Bearer credential is present, valid, and enabled |
| 403 | The Connector's capability and resource allowlist |
| 404 | The command path in the current OpenAPI spec |
| 409 | The write's idempotency key and prior request |
| 422 | The returned field validation details |
The stable Connector contract is `/api/v1`. Dashboard session APIs, LMS launch endpoints, and xAPI use their own authentication and protocol contracts. They are not interchangeable with Connector commands. Use the [current OpenAPI specification](https://honen.com/api/v1/openapi.json) for each command’s authentication, request, and response contract.
For end-user learning delivery protocols, use [LMS Integrations](https://honen-academy.honen.com/docs/6ab35eeada8e0901468ca392). For source ingestion, see [Import files and web links](https://honen-academy.honen.com/docs/6ab36192effafe59361d23d7).
## Adaptive learning in Honen
Source: https://honen-academy.honen.com/docs/6ab4cde787d03e3c73dc8fba
## Why adaptive learning is part of Honen
Honen makes creating courses and learning content easy. But the people taking those courses bring different experiences, goals, and needs. Someone may be meeting a subject for the first time, while someone else is refreshing knowledge they already use at work. One learner is preparing for an exam; another wants to solve a specific problem or explore a new interest.
People also learn at different paces and need different support along the way. An example that makes a concept click for one person may need more context for another. Some learners need another explanation and a chance to practice. Others are ready to explore further. Those needs can change from topic to topic, even within the same course.
That is why Honen includes adaptive learning. You create the course and define its learning goals. Honen can then connect readings and projects to each learner’s context, offer help when they encounter difficulty, suggest optional topics for practice or exploration, and help them revisit what they have learned over time. The six capabilities below work together to support those different needs within a shared course.
| Capability | Purpose | Where to find it |
| --- | --- | --- |
| [Course personalization](https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2) | Learn about a learner’s goals and connect upcoming readings to their context. | **Settings → Course personalization** |
| [Project personalization](https://honen-academy.honen.com/docs/6ab611936a7421b1391978dc) | Ask what learners want to build, then tailor project instructions and steps to an idea that matters to them. | Project editor → **Personalize per student** |
| [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0) | Offer timely help, encouragement, or congratulations during learning. | **Settings → Proactive Tutor → Interventions** |
| [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf) | Add optional topics for remediation or curiosity, with the learner’s agreement. | **Settings → Proactive Tutor → Adaptive Courses** |
| [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045) | Revisit earlier course goals with in-course refreshers and scheduled follow-ups. Missed checks become due again sooner. | **Settings → Retention → Keep sharp** |
| [Spaced repetition in Study banks](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718) | Schedule recall practice for standardized-test preparation or ongoing review, using the learner’s recall ratings. | Learner’s **Lesson plan → Study banks → Flashcards → Spaced repetition** |
## Choose how your course adapts
The course you create provides the foundation. You choose which adaptations are available, and learners accept additional topics before they enter the lesson plan.
Course personalization, Proactive Tutor, and Adaptive Courses have independent creator controls. A course can use personalized readings without proactive messages, or allow remedial topics while keeping exploration beyond the course off. Keep sharp has its own retention settings for refresher stops and follow-up cadence. In Study banks, learners choose scheduled spaced repetition or free practice with the course’s flashcards and quiz questions.
Project personalization has its own control on each supported project. For a website or app project, a short conversation can help learners choose something they want to build for themselves, then adapt the task to that idea while preserving the learning goals and grading criteria.
## What the learner experiences
With these capabilities enabled, a learner’s journey might look like this:
1. **Share a goal.** The learner answers course-specific questions or uses the creator-selected conversation with Honen.
2. **Start the course.** Readings can use relevant examples while retaining the authored learning goals. The course header, tutor, and activities remain familiar.
3. **Practice.** Ordinary feedback handles individual mistakes. A pattern of difficulty may prompt a small help bubble.
4. **Work with the tutor.** The learner opens the bubble and discusses the concept. The tutor can explain, ask a diagnostic question, or suggest a short set of additional topics.
5. **Choose extra practice.** **Add & start** adds the accepted set to the lesson plan under **Just for you** and opens the first topic.
6. **Continue independently.** Learners use the same reading, flashcard, and quiz experience and can return to the authored course.
7. **Revisit earlier learning.** When Keep sharp is configured, refresher stops revisit earlier goals during the course, and scheduled check-ins bring learners back after a unit or the course. Missing a refresher keeps that check in the review schedule.
8. **Keep practicing.** Study banks bring course material together for spaced repetition and free practice, including preparation for a standardized test.
The screenshots in these guides show fictional circuits and heat-transfer courses. Generated messages and topic titles vary with the learner’s context.
## Why adapt a course
Learners bring different prior knowledge, interests, and time to think. Keep the course objectives and required work clear, then adapt the examples and support around them. A teacher may use a classroom demonstration while a technician uses a repair scenario to learn the same circuit concept.
Use ordinary feedback first, offer a focused hint or conversation when useful, and add practice when the learner accepts it. Allow room for careful reading and reflection; taking longer does not, by itself, mean a learner needs remediation.
Check the impact through independent work after support, later retention, and learner feedback. More messages or more generated topics are not, by themselves, evidence of learning.
## Enable the experience step by step
1. Start with [Course personalization](https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2): see the learner’s input screen and a reading comparison, then configure the questions and personalized content.
2. Set up [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0): see the bubbles and conversations, then choose when it may reach out.
3. Add [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf) if learners may accept new topics. Choose remediation and exploration independently.
4. Configure [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045) separately for course look-backs and follow-up checks. Direct learners to [Study banks](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718) for independent review.
5. Save and apply the course changes. Follow [Enable and review adaptive learning](https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2) to test the complete journey before rollout.
## Reinforce learning over time
Retention helps learners revisit material after their first encounter. Keep sharp places brief refreshers in the course and can schedule later check-ins. A missed refresher becomes due again sooner; successful checks advance through the configured schedule.
Current refresher placement uses configured earlier-course goals. It does not automatically create new refresher stops from a learner’s full history of mistakes. For a specific difficulty that needs new explanations or practice, Proactive Tutor and Adaptive Courses can offer targeted additional topics with the learner’s agreement. [See how retention works and how to enable it](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045).
## Read the guides
- [Enable and review adaptive learning](https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2): configure the independent controls and check the learner journey.
- [Personalize a course](https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2): choose questions or chat, and adapt readings.
- [Personalize a project](https://honen-academy.honen.com/docs/6ab611936a7421b1391978dc): ask what learners want to build and tailor a website or app project to their goals.
- [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0): understand bubbles, conversations, and learner controls.
- [Intervention reference](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fcb): see when each kind of check-in is eligible.
- [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf): add remediation and exploration topics.
- [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045): revisit earlier goals and schedule follow-up checks.
- [Spaced repetition and Study banks](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718): schedule recall reviews or practice freely for tests and ongoing learning.
## Adaptive Courses — Beta
Source: https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf
Adaptive Courses lets the tutor suggest one to three optional topics and add them to an individual learner’s lesson plan after acceptance. Use it to support an existing learning goal or explore a learner’s interests.
## What the learner sees
### 1. A timely offer to revisit a concept
Adaptive Courses can begin with the course reaching out. With **Proactive Tutor → Repeated mistakes** and **Adaptive Courses → Remediation** enabled, a pattern of incorrect answers can prompt a help bubble inviting the learner to revisit the concept before continuing. One mistake gets ordinary feedback; repeated difficulty can make a check-in eligible. The tutor uses the available context to decide whether to offer help, so a bubble is not guaranteed after a fixed number of errors.
In this live example, a learner answered two heat-transfer questions incorrectly. The tutor stayed closed and offered to work through **Heat Flows from Warmer to Cooler Objects** together. The learner could choose **Talk to tutor** or **Maybe later**.
Opening the bubble brings up the existing tutor with the learner’s current question and difficulty. The tutor can revisit the concept, offer a hint, and discuss what is unclear. If the gap persists or the learner asks for extra practice, it can propose targeted new topics.
Here, the conversation led to a set on **Temperature vs Transferred Energy**, **Direction of Net Heat Flow**, and **Thermal Equilibrium in the Lunchbox**. The inline proposal appears after the tutor’s explanation.
The learner accepts with **Add & start**. Only then are the topics added under **Just for you** and the first one opened. A help bubble does not automatically move the learner or add content, and **Maybe later** lets them continue their current activity.
### 2. Accept one set of new topics
1. The tutor discusses the learner’s question or difficulty.
2. When additional topics would help, it uses an inline tool call after its message. The tool lists a set of **one to three topics**.
3. The learner chooses **Add & start** to accept the whole set, or **Not now** to continue without adding it.
4. The action changes through its adding and added states. The lesson plan opens and the new topics animate into place.
5. The first topic opens. Its reading streams into the normal reading view as the model produces it.
The three topics are one proposed set, not three alternatives to choose between. Nothing is added merely because the tutor displayed a suggestion.
### 3. Find the additions in the lesson plan
Accepted topics appear together beneath one **Just for you** heading for the consecutive group, with a distinct background in the lesson plan. They use the same topic navigation and activity components as authored topics.
The circuits example below shows the same grouping in the lesson plan.
The Beta supports **readings, flashcards, and quizzes**. Opening another added topic starts preparing its content when needed. Generation takes time; text appears as it becomes available, and practice activities follow. If generation fails, the learner can retry.
These additions belong to that learner’s course experience. They do not edit the shared authored outline for everyone. They are optional practice and do not replace the course’s required assessments.
## Why use it
Use remediation when the next useful step is extra explanation or practice on an existing goal. Use exploration when a learner wants to apply an idea to a new interest. The intended benefit is a useful next step without requiring every learner to take the same detour.
Pair an explanation or worked example with a fresh problem so the learner can apply the concept. For exploration, check that the new application connects back to the course goal. These choices align with the [IES guidance on worked examples and practice](https://ies.ed.gov/ncee/wwc/practiceguide/1).
Judge an addition by whether it addresses the gap and helps the learner return to independent work. More generated topics are not evidence of better learning.
## Enable it step by step
1. Open the course editor and select **Settings → Proactive Tutor**.
2. Enable **Adaptive Courses — Beta**.
3. Enable **Remediation** for existing course content and necessary prerequisites.
4. Independently enable **Curiosity & exploration** if the tutor may propose topics beyond the authored scope. Leave it off for a remediation-only course.
5. To let a difficulty prompt an offer, also enable **Proactive Tutor** and the relevant **Interventions**, such as **Repeated mistakes**. Proactive messages are optional: a learner can ask for topics in an ordinary tutor conversation.
6. Save the settings and complete **Apply Changes** or **Save & Apply** when shown. Follow the course’s [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) process.
## Check the result
1. Use a test learner and ask the tutor for extra practice on an existing goal. Confirm that the proposal appears inline after the tutor’s explanation.
2. Select **Not now** once. No topics should be added.
3. Request a new proposal and select **Add & start**. Confirm the adding/added feedback, lesson-plan animation, one **Just for you** heading for the consecutive group, and navigation into the first topic.
4. Watch the reading appear as generation produces it. Open its flashcards and quiz, then open another added topic and check that its activities become usable.
5. Check explanations and answer keys against the course objectives. Try an independent aligned question to see whether the extra teaching helped.
6. With exploration off, ask for an unrelated extension. The tutor should keep additions within remediation scope.
## Personalization and additions are different actions
The reading personalization control adapts the presentation of an existing topic. It does not create a topic or apply the **Just for you** treatment. Adaptive Courses creates new topics after the learner accepts the tutor’s proposal.
## Keep revisiting the learning
Use [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045) alongside Adaptive Courses to revisit earlier goals during the course and schedule later refresher checks. Missed checks become due again sooner. Keep sharp uses configured refresher stops; additional topics address specific gaps or interests after the learner accepts the tutor’s proposal.
Start with [Enable and review adaptive learning](https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2), or read [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0) to see how a learning moment can lead into this conversation.
## Enable and review adaptive learning
Source: https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2
Configure the parts your course needs, then walk through the experience as a learner before releasing the settings.
## The experience you are setting up
A learner shares a goal, reads a relevant example, receives optional support when useful, and can accept extra topics into the normal lesson plan. Each capability has its own controls, so use the combination that serves your course.
| Outcome you want | Enable | Learner result |
| --- | --- | --- |
| Relevant reading examples | Course personalization and Personalized content | Existing readings can use the learner’s answers. |
| Timely help or encouragement | Proactive Tutor and selected interventions | Bubbles and permitted tutor conversations during learning. |
| Extra teaching on a gap | Adaptive Courses and Remediation | Learner-approved topics within the course goals. |
| Learning beyond the core scope | Adaptive Courses and Curiosity & exploration | Learner-approved additions tied to interests. |
| Revisit earlier course material | Retention → Keep sharp | Configured refresher stops and follow-up checks. |
## Before you enable it
Use an authored course with clear goals, useful readings, and correct assessment answers. Choose a concrete learner use case for review. Decide whether the course permits exploration beyond its scope and which interruptions are appropriate.
These features are intended to support relevance, timely assistance, and practice. Evaluate their usefulness through learner work and feedback; switching them on does not establish a learning benefit.
## 1. Set up course personalization
In the course editor, open **Settings → Course personalization**.
1. Choose whether to enable **Personalized content** for upcoming readings.
2. Select **Chat with Honen** or **Course-specific questions**.
3. For questions, write the prompts and add blanks or dropdowns.
4. Enable **Course-start questions** if learners should answer when entering the course.
5. Select **Save Changes** when available.
[Personalize a course](https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2) explains each control.
## 2. Set up Proactive Tutor
Open **Settings → Proactive Tutor**.
1. Enable **Proactive Tutor** if it should reach out during learning.
2. Review **Interventions**, starting with **Dynamic**. Scroll to see the rest of the list.
3. Enable the error, retry, project, pause, celebration, and encouragement moments appropriate for your course.
4. Choose separately whether **Open tutor automatically** is allowed.
5. Review the existing tutor mode and other tutor settings below these controls.
Enabling every intervention is not necessary. For example, a course with extended reading tasks may keep pause check-ins off while retaining support after repeated incorrect answers.
## 3. Choose whether topics can be added
On the same page, enable **Adaptive Courses — Beta** if learners may accept extra topics.
- Enable **Remediation** for help with existing content.
- Enable **Curiosity & exploration** to allow expansion beyond the authored course.
- For remediation only, keep the first on and the second off.
Save your settings. Complete the editor’s **Apply Changes** or **Save & Apply** step when shown, and follow your normal [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) process. Draft edits alone are not a substitute for applying the course revision used by learners.
## 4. Configure retention separately
Open **Settings → Retention → Keep sharp** if the course should revisit earlier goals. Configure in-course refreshers and follow-ups independently of adaptive topic additions. Follow [Retention and refreshers](https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045) for prerequisites, saving, and schedule checks.
[Study banks and spaced repetition](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718) are a separate learner practice flow. Their recall ratings and review queue are not the Keep sharp follow-up schedule.
## 5. Review as a learner
Use a test learner and a course with meaningful questions and clear answer keys.
| Check | Expected experience |
| --- | --- |
| Enter a course with start questions enabled. | The dedicated tailoring screen appears with the same course header and tutor. Completing or skipping continues into learning. |
| Open a reading after sharing a concrete goal. | A personalized example can connect to that goal while teaching the original concept. The authored reading is available while preparation runs. |
| Answer one quiz question incorrectly. | Normal answer feedback appears; a single mistake does not qualify as a repeated-mistake intervention. |
| Make repeated errors in the same topic. | When eligible and selected by the model, a contextual help bubble appears after feedback time. |
| Click the help bubble. | The existing tutor opens and can discuss the current concept using the learner’s text/audio settings. |
| Ask for practice within the course goals. | If allowed, an inline proposal appears after the tutor’s message. |
| Select Add & start. | The accepted set enters one Just for you group, the first topic opens, and its reading streams in as it is generated. |
| Open the new flashcards and quiz. | The ordinary activity interfaces display usable content and valid answers. |
| Ask for exploration with Curiosity & exploration disabled. | The tutor should keep additional topics within remediation scope. |
| Close a bubble. | Further proactive messages are snoozed for 15 minutes; manual tutoring stays available. |
Interventions are not guaranteed on every eligible event. Use the [reference](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fcb) to check the evidence, enabled switches, feedback grace period, and cooldown before treating silence as an error.
## 6. Review quality as well as mechanics
Read generated explanations and try the quizzes. Confirm that examples preserve the intended concept, correct answers are correct, and an added topic addresses the actual question. Check the same journey with voice if your learners use it.
After support, ask a new question aligned with the same goal and revisit it later to check retention. Look for independent application, alongside dismissals and unnecessary topic additions. A helpful system may say less as the learner becomes more independent.
## Personalize a course
Source: https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2
Course personalization uses a learner’s goals and interests to make upcoming readings more relevant. Creators choose how to collect that context and whether to adapt content from it.
## What the learner sees
### 1. Share a goal at the start
The learner enters the course on **Before we start, tailor your course**. In this example, they enter **teach my class** and choose **a classroom model**. They use **Start learning** to continue. **Skip for now** is available if they prefer to begin without answering.
### 2. Each reading is personalized to the learner
With **Personalized content** enabled, Honen uses the learner’s answers to personalize upcoming readings as they move through the course. Examples and presentation adapt to their goals while preserving the learning objectives.
Below are the opening paragraphs of **A complete loop**, captured from the same topic before and after personalization. The authored reading begins in a bicycle workshop. The learner wants to teach a class, so the personalized reading changes the setting to a classroom demonstration. The learner’s answers were saved before preparing this version.
| Authored: bicycle workshop | Personalized: teaching a class |
| --- | --- |
|  |  |
| Mina tests a lamp in a bicycle workshop. | The teacher sets up a lamp model for a classroom demonstration. |
Both versions explain that the path must go from one battery terminal, through the lamp, and back to the other terminal. The screenshots show the actual generated version; another learner’s wording may differ.
### 3. Continue in the normal course
The learner keeps the same topic, navigation, tutor, flashcards, and quizzes. The reading control lets them switch between standard and personalized content once a personalized version is available. This does not add a topic or apply a **Just for you** label.
## Why use it
A familiar application can help a learner connect an abstract idea to something they want to do. The intended benefit is a clearer route into the same learning goal. Relevance alone does not demonstrate understanding: check whether the learner can apply the concept in a new question.
The generator is instructed to preserve learning goals, definitions, factual meaning, and assessment meaning. Creators should review generated examples for subject accuracy.
## Enable it step by step
1. Open the course editor and select **Settings → Course personalization**.
2. Turn on **Personalized content** to use learner context when preparing readings. This control is independent of the method used to collect answers.
3. Select **Course-specific questions** for a structured form, or **Chat with Honen** for the existing conversation-based method. Both provide context for tutoring and reading personalization.
4. For questions, select **Add question**. Write the prompt and a sentence starter. Use **Add blank** for free text and **Add dropdown** for a defined set of choices.
5. Enable **Course-start questions** to show the dedicated tailoring screen when answers are needed.
6. Select **Save Changes** when shown. Complete **Apply Changes** or **Save & Apply** when the editor requires it, following your normal [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) process.
### Reproduce the classroom example
| Question | Sentence starter | Field |
| --- | --- | --- |
| What would you like to use this course for? | I want to use this course to … | Blank named **my goal** |
| Which context should examples use? | Use examples from … | Dropdown named **my context**, with **bicycle repair**, **a classroom model**, and **a camping light** |
Ask for context that will make an example useful. Avoid asking learners to label their ability or choose a supposed learning style. Up to eight questions are supported; a short set is easier to complete.
## Check the result
1. Enter the applied course as a test learner. Confirm that the start screen uses the normal course header and tutor.
2. Enter **teach my class**, choose **a classroom model**, and select **Start learning**.
3. Open the reading. The authored version remains available while preparation runs. Allow the personalized version to finish, then compare both versions with the reading control.
4. Check that the classroom demonstration replaces the workshop example and that the complete-path explanation stays correct. Try the flashcards and quiz to confirm that the same concept is assessed.
5. Test **Skip for now** with a learner who has not answered. They should be able to continue into the course.
Prepared readings are reused for the same base content, course revision, and learner context. Changes to the base reading or answers require a new version. A changed question set can require fresh answers; previously saved answers are used only when they match the current questions.
## Next steps
Use [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0) for timely help during learning, or [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf) for optional new topics. [Enable and review adaptive learning](https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2) connects the full setup and learner checks.
## Personalize a project
Source: https://honen-academy.honen.com/docs/6ab611936a7421b1391978dc
Project personalization helps learners practice a skill by building something that matters to them. Before they start, Honen asks a few questions about what they want to make, who it is for, and what it should do. Their answers shape the project's instructions and guided steps while preserving its learning goals and grading criteria.
For example, a course can teach everyone how to build a website with AI while letting each learner work on a useful idea of their own: a photography portfolio, a website for their local club, or a page for a small business.
## What the learner experiences
### 1. Choose to make the project personal
When the learner opens a project with personalization enabled, they see **Make this project yours**. They can select **Personalize project** or **Use the base project** to continue with the original task.
### 2. Share what they want to build
Honen starts a short conversation, usually asking two to four questions to gather enough context. The questions follow the project and the learner's answers; creators can provide guidance about what to ask.
For a **Build a website with AI** project, the conversation might cover:
| What Honen asks about | Example learner answer |
| --- | --- |
| What would you like to build, and who is it for? | “A photography portfolio for me, so local families can see my work.” |
| What should visitors be able to do? | “Browse my portraits, read about my sessions, and find out how to contact me.” |
| What should it look and feel like? | “Simple and warm, with large photos and very little clutter.” |
These are illustrative questions and answers, rather than a fixed questionnaire. The conversation can also help a learner describe an app they would find useful, such as a practice tracker for their hobby.
### 3. Work through a project that reflects their idea
Honen uses those answers to tailor the wording of the existing project. For the photography example, the same website-building steps can become:
| Original project step | Personalized direction |
| --- | --- |
| Describe the website's audience and purpose. | Describe the families you want to reach and what they should learn about your photography. |
| Build the first version with the Agent. | Ask the Agent to create a warm, uncluttered portfolio with a portrait gallery, session information, and contact details. |
| Review the result and refine it. | Check whether a visitor can browse your work and find how to contact you, then refine the layout and wording. |
The learner still does the work: giving the Agent instructions, reviewing the result, making changes, and submitting the project. Personalization makes that work relevant to their own goal.
## Set up the website or app project
1. In the course editor, add or open a **Use an Agent** project. Choose **HTML & Web** for a website project or **Full Stack App** for an application project.
2. Define the shared learning goal, steps, instructions, and rubric. For this example, learners should describe an audience and purpose, build a first version with AI, and evaluate and improve the result.
3. Turn on **Personalize per student** above the project editor. Your workspace's term for learners may appear in place of “student.”
4. Add **Personalization guidance** to steer the conversation. For example: “Ask what website or app the learner wants to build for themselves, who will use it, what it should help them do, and the style they want. Adapt the existing steps to that idea while keeping the learning goals and rubric.”
5. Save the project and publish or apply the course changes so learners receive the updated settings.
You can also ask the course editor assistant to prepare the project:
> Create a Use an Agent project called “Build a website that matters to you” using HTML & Web. Teach learners to describe an audience and purpose, build a first version with AI, and review and improve the result. Enable project personalization and ask what they want to build, who it is for, what it should do, and the style they want. Keep the same steps and grading criteria for everyone.
See [Create and edit projects](https://honen-academy.honen.com/docs/6ab3766c78ce9f1718279677) for the full project editor workflow. For **Full Stack App**, learners publish the application and complete its live check before submitting.
## What changes for each learner
For a Use an Agent project, personalization can adapt the instructions, the Agent's guidance, and the wording of the existing steps. It preserves the step structure, assets, rubric criteria, and grading weights. The learner's version applies to their project attempt; it does not rewrite the shared project for everyone else.
Project personalization is enabled separately on each supported project. [Course personalization](https://honen-academy.honen.com/docs/6ab4cded87d03e3c73dc8fe2) controls the context used for readings; enable project personalization when the hands-on task should also reflect what the learner wants to make.
## Review before sharing
Open the published course as a test learner and choose **Personalize project**. Give a concrete answer such as the photography portfolio above, then check that the resulting instructions and steps reflect it and still assess the intended skills. Also try **Use the base project** to confirm learners can complete the original task.
Return to [Adaptive learning in Honen](https://honen-academy.honen.com/docs/6ab4cde787d03e3c73dc8fba) to see how project personalization fits alongside personalized readings, tutoring, additional topics, and review.
## Proactive Tutor
Source: https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0
Proactive Tutor can reach out during learning without requiring the learner to ask first. It can offer help, acknowledge progress, encourage practice, or stay quiet. The creator chooses the allowed interventions.
## What the learner sees
### 1. Receive an optional check-in
A small animated thought bubble appears beside the tutor controls while the lesson stays in view. Its message is generated from the current learning context. A help message might ask whether the learner wants to work through the current concept together.
### 2. Choose whether to talk
Clicking the bubble or **Talk to tutor** opens the existing tutor pane. The tutor has the relevant course context and can begin with a focused question. It uses the learner’s existing microphone and audio controls: text-only learners can keep both muted, while learners using voice can continue by voice.
**Maybe later** or closing the bubble snoozes proactive messages for 15 minutes in that course. The learner can still open the tutor manually.
Here, the tutor asks the learner to reason about an open switch. The conversation can continue with an explanation or optional practice; opening help does not automatically add topics.
### Other possible responses
| Response | Learner experience |
| --- | --- |
| Stay quiet | Learning continues without a message. This is a normal outcome, even when an intervention is enabled. |
| Offer help | A bubble invites the learner to discuss the concept. |
| Congratulate | A brief message acknowledges a successful assessment, without an action button. |
| Encourage | A brief message recognizes continued practice, without an action button. |
| Open the tutor | With separate permission enabled, continued difficulty after an earlier offer can open the tutor pane. |
Congratulations and encouragement do not create topics or claim that the learner has mastered the subject. A learner can click a message bubble if they want to talk.
### Recognition during practice
Encouragement can appear while the learner reviews flashcards. It has no **Add & start**, **Talk to tutor**, or other visible action button; the whole bubble remains clickable if the learner wants a conversation.
A completed assessment can also receive a short message. In this example, the learner answered three questions correctly and the model chose encouragement. It may instead choose congratulations or stay quiet, within the enabled intervention rules.
Message-only encouragement and congratulations clear automatically after a short display. The screenshots capture those live, temporary states.
### A neutral invitation during a pause
After the configured focused pause on an unanswered question, the tutor can offer a neutral invitation. The learner has not submitted a wrong answer in this example. The bubble leaves the question in place and makes help optional.
## Why use it
One wrong answer receives the quiz’s ordinary feedback. A repeated pattern may justify help. The tutor should first clarify what the learner is thinking and offer an explanation, hint, or worked example. Additional topics are available when [Adaptive Courses](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf) permits them and the learner accepts them.
Ask the learner to explain their thinking before choosing the next hint. For example, ask them to trace the complete circuit path, then try a fresh question after the explanation. This follows the emphasis on subject-specific reflection in the [EEF metacognition guidance](https://educationendowmentfoundation.org.uk/education-evidence/guidance-reports/metacognition).
A pause can mean careful thought, note-taking, or an interruption. Use a neutral invitation and let the learner decide whether help is useful. Keep pause check-ins off for tasks where extended reading or reflection is expected.
## Enable it step by step
1. Open the course editor and select **Settings → Proactive Tutor**.
2. Turn on **Proactive Tutor**.
3. Under **Interventions**, review **Dynamic** first, then scroll through the list. Enable the individual moments that fit your course. The scrollbar and bottom fade indicate more controls below.
4. Decide separately whether to allow **Open tutor automatically**. Leave it off if all help should begin with a learner opening the bubble.
5. Review tutor mode and conversation settings. Learners continue to use the ordinary microphone, audio, and chat controls.
6. Save the settings and complete the editor’s **Apply Changes** or **Save & Apply** step when shown. Follow your normal [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) process.
**Open tutor automatically** is a separate permission. Ignoring a bubble alone does not cause the pane to open: an earlier help offer, time to respond, and new evidence of difficulty are required.
See the [Intervention reference](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fcb) for each control and the current timing rules. For the normal conversation controls, see [Ask the AI tutor for help](https://honen-academy.honen.com/docs/6ab361a8effafe59361d2432).
## Check the result
1. Use an applied test course with a quiz containing at least three automatically graded questions. Enable **Repeated mistakes** and leave **Dynamic** off to isolate that scenario.
2. Submit one wrong answer. Confirm that ordinary quiz feedback appears.
3. Submit another wrong answer in the same topic. Leave the feedback visible for at least eight seconds. Repeated mistakes requires at least half the graded answers to be incorrect; the model can still choose to stay quiet.
4. When a bubble appears, open it. Confirm that the existing tutor addresses the relevant concept. Check text and audio behavior using your learner’s preferred controls.
5. In a separate attempt, dismiss an offer. Proactive messages should be snoozed for 15 minutes, while manually opening the tutor remains available.
6. Review whether the help was timely and specific. Watch for unnecessary interruptions and whether the learner can solve a new question independently.
For the other scenarios, use the evidence and timing rules in the [Intervention reference](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fcb). A quiet tutor can be the expected result of a disabled switch, insufficient evidence, a cooldown, or the model’s decision.
## Proactive Tutor intervention reference
Source: https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fcb
Interventions define the situations in which Proactive Tutor may offer help or acknowledge progress. Creators select the allowed moments; learners keep the normal course experience and can decline a conversation.
## What the learner sees
After repeated incorrect answers, the learner may receive a small help bubble while quiz feedback stays visible. Opening it begins a tutor conversation. Encouragement and congratulations can be short messages without action buttons. Silence is also a valid response.
The intended benefit is support at a useful moment. Time and activity counts are signals to consider, rather than diagnoses of understanding or motivation.
## Choose interventions step by step
1. Open the course editor’s **Settings → Proactive Tutor** and enable the master switch.
2. Review **Dynamic** at the top of **Interventions**. It can permit an additional reflective offer; it cannot override a category you have disabled.
3. Scroll down and enable the individual moments in the table below. Start with the ones you can meaningfully review in your course.
4. Decide separately whether **Open tutor automatically** is appropriate. A pause alone cannot open the tutor automatically.
5. Save and apply the course settings through your normal [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) workflow.
Turning the master switch off stops proactive messages while retaining the individual selections. An enabled intervention gives permission to act; it does not force a message whenever a threshold is met. The model may choose silence and timing checks may defer a message.
## Available interventions
| Intervention | Current evidence used | What it permits |
| --- | --- | --- |
| **Dynamic** | Learner-reported low confidence or meaningful reading/flashcard activity, subject to the other policy checks. | An additional reflective help bubble. It cannot turn disabled intervention categories back on. |
| **Repeated mistakes** | At least two incorrect automatically graded answers in the current topic, with at least half of graded answers incorrect. | A targeted offer of help. One mistake or two errors among many correct answers does not qualify. |
| **Failed retries** | Two consecutive completed attempts below 60%, with current evidence of difficulty. Successful or ungraded attempts break the streak. | Help after another attempt still shows difficulty. This control is independent of Repeated mistakes. |
| **Project setbacks** | At least one graded project submission and a best recorded result below 60%. | An offer to review the task or feedback. Missing grades do not count as failure. |
| **Long pause on a question** | Two minutes of visible, focused time on the same unanswered question, followed by at least eight seconds without input. | A neutral help bubble. A pause alone cannot open the tutor automatically. |
| **Long pause while reading** | Five minutes of visible, focused time without meaningful scroll progress, followed by at least eight seconds without input. | A neutral help bubble. Moving at least two percentage points in either direction resets the pause timer. |
| **Celebrate progress** | A completed quiz with at least three automatically graded answers and at least 80% correct, or a project result of at least 80%. | Congratulations without an action button or claim of mastery. |
| **Encourage practice** | At least three flashcards viewed or three graded answers, without a current pattern of difficulty. | Brief recognition of practice without an action button. Viewing cards does not prove understanding. |
| **Open tutor automatically** | An earlier help bubble, at least 30 seconds to respond, and new difficulty meeting the stronger escalation rule, such as three errors or repeated failed submissions. | Opening the existing tutor pane. Ignoring the bubble by itself is insufficient. |
These thresholds are current product defaults, not creator-editable fields. They are initial design hypotheses, not research-established cutoffs for every subject or learner.
## Timing and learner control
- The learner gets at least eight seconds to read quiz feedback before an intervention.
- Hidden or unfocused tabs do not accumulate pause time.
- A response is discarded if the learner changes question, activity, answers, focus, or starts interacting again before it arrives.
- Closing a bubble snoozes proactive messages for 15 minutes for that learner in that course and workspace.
- After an intervention, a 15-minute cooldown prevents repeated offers from the same evidence. New difficulty can justify help or escalation.
## What the evidence can tell us
Automatically graded multiple-choice and true/false answers can show a pattern of incorrect responses. They do not, on their own, identify the learner’s exact misconception. Project support currently uses the recorded score, rather than a detailed model of each rubric concept.
Reading time, scrolling, and cards viewed describe activity. They do not establish comprehension, emotion, motivation, disability, or ability. A useful tutor asks a diagnostic question instead of treating a signal as a diagnosis.
For the learner-facing experience and guidance on choosing a useful response, see [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0).
## Check one scenario at a time
1. Enable the intervention you want to review. Leave Dynamic off when isolating a specific evidence rule.
2. Use a test learner and produce the evidence in that row, such as two incorrect automatically graded answers in a topic with at least half incorrect.
3. Allow the feedback grace period and inspect the course without switching tabs or interacting again. For a pause check, keep the question unanswered and the tab visible and focused.
4. Compare the observed response with **What it permits**. The exact message is generated and is not guaranteed.
5. Check dismiss and cooldown behavior before testing another scenario. Avoid treating a snoozed or stale response as a failed trigger.
6. Review relevance and interruptions alongside subsequent learner work. Use [Enable and review adaptive learning](https://honen-academy.honen.com/docs/6ab4cde887d03e3c73dc8fc2) for the full course checklist.
## Retention and refreshers
Source: https://honen-academy.honen.com/docs/6ab5627c0cb4c669dfed7045
Keep sharp brings earlier course learning back into the learner’s path. Creators can add in-course refresher stops and enable scheduled follow-up checks after a unit or course. A missed check becomes due again sooner so the learner has another opportunity to practice.
## What the learner experiences
A learner finishes an earlier goal, encounters a brief refresher during a later unit, and returns for scheduled checks when follow-ups are configured. For example, a circuit refresher can ask them to identify a complete conducting path before moving on.
| Moment | Result for the learner |
| --- | --- |
| Reach a configured in-course stop | Answer a short check on earlier learning goals. |
| Finish the unit or course used as the follow-up anchor | A configured check becomes due according to the retention schedule. |
| Submit an incorrect scheduled check | The same schedule step becomes due again sooner: one day later under the default retry policy. |
| Complete a successful scheduled check | Advance to the next configured interval. |
| Pause or snooze follow-ups | Retention scheduling respects the learner’s preference. |
This is an example of the configured workflow, not a claim that the system automatically inserts a stop for every mistake.
## Why use it
A correct answer immediately after a lesson is only one observation. Returning to earlier goals gives learners another opportunity to retrieve and apply them after time has passed. Review later performance to judge retention, rather than treating completed review counts as mastery.
## Enable it step by step
1. Open the course editor's **Settings → Retention**.
2. Enable **Keep sharp** to inspect the available settings.
3. Choose **In course** for checks drawn from earlier material. The interface requires at least three units for these look-backs.
4. Choose **Check in after** if learners should receive checks after finishing. Review its cadence before saving.
5. Choose **Mixed**, **Situations**, or **Checks**, then set **Questions per check**.
6. Select **Save retention settings** when the configuration is ready.
An assignment can use **Custom retention** to override its content's schedule. Learners can pause or snooze their own follow-up checks.
## How the schedule works
Keep sharp supports two kinds of reinforcement:
- **In-course refreshers** revisit earlier learning goals before the learner moves into later units. Creators choose the goals through the course outline; adding stops to an existing course prefers goals from recent earlier units.
- **Follow-up checks** bring learners back to configured refresher stops after completing a unit or course. Their timing follows the course or assignment’s retention schedule.
A refresher draws questions for its configured goals from the learner’s course revision, with authored refresher questions as a fallback. Question selection spreads practice across those goals. It does not currently rank questions by the learner’s past mistakes or automatically add new refresher stops wherever they struggle.
Performance does affect the follow-up schedule: an incorrect refresher result keeps the current schedule step and makes another attempt due one day later under the default retry policy. A successful check advances to the next configured interval. Skipping does not count as evidence of understanding. Reminder delivery also depends on the workspace’s alert settings and the learner’s pause or snooze preferences; a due check does not guarantee an immediate message.
Follow-ups need refresher stops to link to. When enabling **Check in after**, confirm the course has suitable stops and questions, including courses without in-course refreshers.
## Check the result
1. Use a test course with at least three units and questions for the goals selected by the refresher stops.
2. Enable and save **In course**, then inspect the course outline for the stops. Apply the course changes through the normal [publishing and review](https://honen-academy.honen.com/docs/6ab35ee7da8e0901468ca381) process.
3. Open a later unit as a learner and complete its refresher. Confirm that the questions address earlier goals and have correct answer keys.
4. If **Check in after** is enabled, finish the configured unit or course and inspect the due review schedule. Confirm that suitable refresher stops exist to receive the follow-up.
5. During a scheduled check, verify that an incorrect result retries at the current step and a successful result advances the cadence. Check reminder delivery separately from the due date: delivery depends on alert settings and learner preferences.
## Related support
For immediate help with repeated mistakes, [Proactive Tutor](https://honen-academy.honen.com/docs/6ab4cdea87d03e3c73dc8fd0) can offer a conversation. [Adaptive Courses — Beta](https://honen-academy.honen.com/docs/6ab4cde687d03e3c73dc8faf) can add accepted remedial topics when a gap needs extra teaching.
### Study banks have their own review flow
[Study banks and spaced repetition](https://honen-academy.honen.com/docs/6ab3768778ce9f1718279718) let learners open the course’s flashcards and quiz questions for self-directed practice. Recall ratings control those item-level review intervals. Keep sharp uses course refresher stops and the course or assignment’s follow-up schedule.
