Appearance
Knowledge Base
The Knowledge page puts your documentation in one place. Documents synced from IT Glue, Hudu, and OneNote sit next to procedures your team writes in Junto. Once a document written in Junto is approved, it joins the knowledge base the agent searches during ticket triage and in Explore. Junto can also draft documents from resolved tickets for your review, and it can send approved documents out to Hudu or IT Glue.
Availability and Access
Knowledge is available on Explorer, Operator, and Architect plans. Open Knowledge in the sidebar.
| Action | Minimum role |
|---|---|
| Browse and read documents | Technician |
| Write documents, save drafts, send them for review, start a new version | Technician |
| Approve and publish or Archive a document | Operator |
| Approve or Dismiss drafts in the review queue | Operator |
| Turn syncing to Hudu or IT Glue on or off | Admin |
| Publish, update, or archive articles from Explore | Operator by default (see Using Knowledge from Explore) |
If your organization restricts which companies a person can see, the page shows only documents for those companies, plus documents that apply to every client.
How It Works
- Bring in your documentation. Connect IT Glue, Hudu, or OneNote. Their documents appear on the Documentation tab after each sync.
- Write what's missing. Write a procedure or fix in Junto, or let Junto draft one from resolved tickets.
- Approve it. An Operator or above approves the document. Within a few minutes it's published to the knowledge base, and the agent can find it with semantic search.
- Sync it out (optional). If Hudu or IT Glue is connected, an Admin can have approved documents copied there automatically.
Browsing Documentation
Scope
The left rail sets the scope for the whole page:
- Global (all clients), at the top, shows every document you can see.
- Clients lists each client that has documents, with its document count. Use the filter box to find a client quickly. Documents that aren't tied to one client have their own Global entry in this list.
Selecting a client narrows all three tabs to that client.
Tabs
| Tab | What it shows |
|---|---|
| Documentation | Every document in the knowledge base: synced documents and approved documents written in Junto. |
| Written in Junto | Documents your team writes on this page, from draft to approved. See Writing Documents. |
| Review queue | Documents Junto drafted from resolved tickets, waiting for a decision. See Auto-Drafted Documents. |
Finding a Document
- Source chips (All, IT Glue, Hudu, OneNote) filter the list by where documents came from. A chip appears only while its integration is connected.
- Search by title or folder matches document titles and folder names, not the text inside documents. To search document contents, ask the agent in Explore.
- The table shows each document's title, client and folder, Source, Publishing status, and when it was last Updated. Results are shown 50 at a time; use Previous and Next to page through them.
Documents written in Junto show Junto as their source.
Reading a Document
Click a row to open it. Use the up and down arrows to step through the list without going back. The Details panel shows where the document came from, when it last synced, and related documents from the same list.
Synced documents are read-only here. Edit them in IT Glue, Hudu, or OneNote, and the change arrives with the next sync. For a document written in Junto, the pencil icon opens it in the editor. If someone is already working on a new version, the pencil opens that version.
Writing Documents
- Click New document in the top bar.
- Enter a Title. Use the words a technician would search for, such as "Reset MFA for a Microsoft 365 user".
- Under Applies to, choose One client and select the client, or choose All clients. If a client is selected in the rail, the new document starts under that client.
- Write the Document in Markdown. Switch between Write and Preview to check formatting. Leave out passwords, keys, and other secrets.
- Click Save draft.
What happens next depends on your role:
- Technicians click Send for review. An Operator or above can then approve it.
- Operators and above click Approve and publish. You can approve documents you wrote yourself.
Both buttons save any unsaved changes first.
Document Status
The Written in Junto tab lists drafts, documents in review, and approved documents with their Status, Version, and when they were last Updated. Click a row to open it in the editor.
| Status | What it means |
|---|---|
| Draft | Being written. Anyone who can write documents can edit it. |
| In review | Sent for approval. Editing it returns it to Draft. |
| Approved | Published to the knowledge base. It can't be edited in place. |
| Replaced | An earlier version that a newer approved version superseded. |
| Archived | Retired. The agent no longer uses it. |
Replaced and archived versions don't appear in the Written in Junto list.
After Approval
An approved document is published to the knowledge base within a few minutes. It appears on the Documentation tab with Junto as its source, and the agent can use it in triage and Explore. If sync to Hudu or IT Glue is on, the document is copied there too. Approvals and archives are recorded in the audit log.
Editing an Approved Document
Approved documents are never changed in place. To revise one:
- Open it from Written in Junto, or click the pencil icon in the reader.
- Click Edit as a new version. Junto creates a draft of the next version.
- Edit, then send it for review or approve it as usual.
The approved version stays live until the new version is approved. The older version then becomes Replaced. A document can have only one version in progress at a time.
Archiving a Document
Operators and above can click Archive in the editor and confirm. The agent stops using the document a few minutes later. If the document was sent to Hudu or IT Glue, it's archived there too. Archiving can't be undone; to bring the content back, write it as a new document.
When a client company is deleted in Junto, its documents are archived.
Auto-Drafted Documents
When Advisor finds a knowledge gap in resolved tickets, it recommends a Draft KB Article. Junto writes a draft document for those recommendations in the background, grounded in the tickets behind them, then checks and reviews each draft before anyone sees it. Drafts wait in the Review queue tab. Nothing becomes a knowledge document until an Operator or above approves it.
Auto-drafted documents come from Advisor recommendations, which are available on Operator and Architect plans.
Which Recommendations Get a Draft
Junto drafts pending Draft KB Article recommendations that are High or Medium priority, or that are backed by at least two tickets. It starts a limited number of new drafts each day, so a large backlog is drafted over several days.
- A draft that fails review is rewritten once. If the rewrite still raises issues, the draft is flagged Needs a look. A draft that repeats an existing document is flagged right away rather than rewritten.
- If two or more new tickets join a recommendation after its draft was written, the draft is rewritten to include them.
- Drafts for a client-scoped recommendation become documents for that client. Organization-wide recommendations become documents for all clients.
The Review Queue
When drafts are waiting, a Review queue button with a count appears in the top bar. Each card shows:
- The draft's title and a status chip. Ready means the draft passed the automatic review. Needs a look means the review raised issues. Hover over the chip to see the review summary and any issues.
- The client (or All clients), how many tickets it was drafted from, and when it was last updated.
- A short summary, and a warning if a document with the same title already exists or an existing document may already cover it.
- Read draft, which expands the full text and any Confirm before approving questions.
Drafts that passed review are listed first. If more drafts are being written, the tab says how many.
Approving or Dismissing a Draft
Operators and above see Approve and Dismiss on each card. Other roles can read drafts but not decide them.
- Approve adds the draft as an approved document right away. It's published and synced like any other approved document, and its Advisor recommendation is marked approved.
- Dismiss removes the draft and dismisses its Advisor recommendation.
Drafts can't be edited in the queue. If a draft needs changes, approve it and then use Edit as a new version, or dismiss it and write the document yourself.
A draft that appears to contain a password, key, or token can't be approved. Dismiss it instead.
If a recommendation is approved, rejected, or dismissed on the Advisor page, its draft leaves the queue.
Using Knowledge from Explore
The agent searches the knowledge base when it triages tickets and when you ask questions in Explore. That includes synced documents and approved documents written in Junto.
Publishing Articles from Chat
If your organization doesn't have Hudu or IT Glue connected, you can also ask Explore to publish and maintain articles:
| Tool | What it does |
|---|---|
| Publish knowledge article | Saves a new article as an approved document. |
| Update knowledge article | Publishes new text as the next version of an article written in Junto. The previous version is replaced, so no duplicate is left behind. The article keeps its client. |
| Archive knowledge article | Retires an article written in Junto. It can't be restored from chat; to bring it back, publish it again. |
Example requests:
- "Write up the fix from this conversation as a knowledge article for Acme Corp."
- "Update the VPN setup article with the new gateway address."
- "Archive the duplicate printer mapping article."
The agent shows you the full text before it asks to publish. If you don't name a client, the article applies to every client unless the conversation is tied to one client. A conversation tied to one client can only update or archive that client's articles. Update and archive work only on articles written in Junto, not on documents synced from IT Glue, Hudu, or OneNote. New and updated articles become searchable a few minutes after they're published.
Approval
By default, each of these tools has a Minimum role of Operator and an Approval setting of Always. The agent shows a confirmation card naming the client and title, for example "Publish knowledge article for Acme Corp: Reset MFA for a Microsoft 365 user". The client is fixed when the card is raised. The person who confirms the card is recorded as the document's approver. Admins can change these settings in Tool Policies.
Technicians don't see these tools at their default minimum role. They can write documents on the Knowledge page and send them for review instead.
When Hudu or IT Glue Is Connected
With Hudu or IT Glue connected, Explore doesn't offer these tools. The agent writes articles directly in your documentation platform with that integration's own tools. See Hudu and IT Glue. Documents written on the Knowledge page can still be sent to the platform with sync.
Syncing to Hudu or IT Glue
When Hudu or IT Glue is connected, the top bar shows Sync to Hudu or Sync to ITGlue. If both are connected, Junto syncs to Hudu.
Turning Sync On
- Click Sync to Hudu (or Sync to ITGlue).
- Turn on Send approved documents to Hudu (or ITGlue).
Sync is off until an Admin or Owner turns it on. Other roles can open the dialog to see the setting and status. The switch belongs to each platform, so if you connect a different platform later, its sync starts off.
How Sync Works
Sync is one-way, and Junto is the source:
- Only approved documents are sent. Drafts and documents in review stay in Junto.
- A new approved version replaces the copy in Hudu or IT Glue, including any edits made there. Make changes in Junto.
- Archiving a document in Junto archives its copy.
- Each copy ends with a note saying it's maintained in Junto, with a reference that ties it to its Junto document.
- Copies aren't imported back. The regular Hudu and IT Glue document sync skips articles Junto sent, so they don't appear twice in the knowledge base.
Where each document goes depends on the platform:
| Document | Hudu | IT Glue |
|---|---|---|
| One client | An article under the client's mapped Hudu company | A published document under the client's mapped IT Glue organization |
| All clients | A global knowledge base article | Not sent. Every IT Glue document belongs to an organization, so these stay in Junto. |
If a document moves to a different client, or a client's mapping changes, the old copy is archived and a new one is created in the right place.
Sync runs shortly after a document is approved or archived, when sync is turned on, and every hour to catch anything missed, such as a failed write or a client mapped later. Turning sync off stops further changes; copies already sent stay where they are.
Sync Status
While sync is on, the dialog shows how many approved documents are:
| Count | Meaning |
|---|---|
| In Hudu / In ITGlue | Copied and up to date |
| Waiting | Queued for the next sync |
| Client not mapped | The document's client has no company mapping, so it has nowhere to go |
| Failed | The last attempt failed; it's retried on the next sync |
Requirements
- Company mappings. Map each client in the integration's settings. See Hudu: Map Companies and IT Glue: Map Companies.
- Write access. The Hudu API key must be able to create and archive articles. IT Glue needs a full-access (read/write) API key.
Troubleshooting
| Issue | What to check |
|---|---|
| Knowledge shows a lock icon in the sidebar | Knowledge requires an Explorer, Operator, or Architect plan. Ask your organization's Owner to check the subscription. |
| "No documents yet" | Connect IT Glue, Hudu, or OneNote in Settings > Integrations and run its document sync. |
| "Nothing has synced for this client yet" | Check that the client is mapped in your documentation integration and that the mapping is active. |
| A source chip is missing | Chips appear only for connected integrations. |
| Search doesn't find a document | Search matches titles and folder names only. Clear the source chip, select Global (all clients), or ask Explore to search document contents. |
| Approve and publish is missing | Approving requires the Operator role or above. Technicians use Send for review. |
| An approved document can't be edited | Click Edit as a new version. |
| "This document already has a newer version in progress" | Open the version in progress from Written in Junto. |
| An approved document isn't on the Documentation tab yet | Publishing takes a few minutes. The tab refreshes on its own. |
| The review queue is empty | Drafts come from Advisor Draft KB Article recommendations. If drafts are being written, the tab says how many. |
| A draft can't be approved because it may contain a secret | Dismiss it. Drafts that look like they contain a password, key, or token can't be approved. |
| "This draft is no longer waiting for review" | Its recommendation was decided on the Advisor page, or changed after the draft was written. |
| Sync to Hudu or IT Glue isn't in the top bar | Connect Hudu or IT Glue under Settings > Integrations. |
| The sync switch is disabled | Only Admins and Owners can change it. |
| Documents show Client not mapped | Map the client in the Hudu or IT Glue settings. The next hourly sync sends them. |
| Documents show Failed | Check that the API key is valid and has write access. Failed documents are retried every hour. |
| An all-clients document isn't in IT Glue | Expected. IT Glue keeps every document under an organization. |
| Edits made in Hudu or IT Glue were overwritten | Junto is the source. Make changes in Junto and approve a new version. |
| Explore won't publish a knowledge article | With Hudu or IT Glue connected, Explore writes in that platform instead. Otherwise, the tool's minimum role may be above yours; see Tool Policies. |
| Explore won't update an article | If the article has a new version in progress on the Knowledge page, approve or archive that version first. |