|
| |
👻 No tricks, just integrations 🍬
New ways to connect KnowledgeOwl with Okta, Microsoft Entra ID, Freshservice and Help Scout, plus a peek at what's brewing. |
|
| |
This month, we've been busy stitching KnowledgeOwl together with the tools you already use: new author provisioning, contact form and import integrations, plus a few more apps waiting in the wings.
Integrations are a big focus for us this year, and it's been so fun to see them start rolling out. Our goal is simple: your knowledge base should show up wherever your team is already working, instead of being one more tab to remember. |
|
|
Author provisioning with Okta and Microsoft Entra ID |
|
|
|
Let your identity provider handle the author comings and goings
If your IT team manages everyone's access from one place, this may be just the treat they’ve been hoping for. With SCIM author provisioning, your identity provider (IdP) becomes the source of truth for who has an author account in KnowledgeOwl.
When someone joins, they get an author account automatically. When they change teams or leave, their access updates or disappears, no ghosts left haunting your author list.
We now have proper, dedicated integrations for two of the most popular IdPs: Okta: Add the KnowledgeOwl Author Provisioning with SCIM 2.0 app straight from the Okta Integration Network. It can create authors, update their profile details, deactivate them, and push Okta groups to KnowledgeOwl.
Microsoft Entra ID: Connect Entra ID to KnowledgeOwl to create, update and remove authors automatically.
With group provisioning profiles, you can give different groups different permissions. For example, your admins group can get full admin rights while your writers group gets a Writer role in a specific knowledge base.
Authors can either keep a KnowledgeOwl username and password, or log in through SAML SSO with their IdP password. You choose what works for your team.
Using a different identity provider? SCIM 2.0 is a standard, so you can still set up author provisioning with other IdPs using our generic instructions. Okta and Entra ID just get the extra-smooth, purpose-built setup.
|
|
| |
|
|
|
|
|
|
|
|
|
|
Contact form: now sending tickets to Freshservice |
|
|
|
Questions go straight to the right queue
Your KnowledgeOwl contact form (and the embedded contact widget) can now create tickets directly in Freshservice. Add your Freshservice domain and an agent's API key in Customize > Contact form, choose Freshservice as your send method, and you're set.
Each submission becomes one Freshservice ticket, with: The reader's name, email, subject and message Up to 10 attached files (40 MB total) A private note with helpful context, like the last page the reader visited and their browser and operating system
We also recommend adding a backup email, so if anything goes awry with the connection, submissions still land somewhere safe.
Using Freshdesk instead? Good news: the contact form has been able to create Freshdesk tickets for a while now. Both are ready when you are. |
|
| |
New resource: API guide for AI coding assistants |
|
|
|
Teach your AI assistant to speak owl
More and more of you are connecting AI assistants like Claude and ChatGPT to KnowledgeOwl through our API, and getting a lot done that way.
So we gathered what we've learned from those connections into one handy guide.
Give the guide's URL to your AI assistant, or paste it into its instructions file, before it starts working with the API. It covers: Which docs to start with What to include in every request Rate limits and caching Article status values (the important specifics) How to update articles safely Tips on uploading files
This is also a stepping stone toward our MCP server, which is still in progress. Scoped API keys were another piece of that puzzle.
|
|
| | Waiting in the wings: Three new apps |
|
|
|
Brewing in the cauldron, almost ready to serve
We've got a few apps that are built and waiting on marketplace approval (or very nearly ready to submit). We'll let you know the moment each one goes live. Microsoft Teams notifications Get a Teams message in the channel of your choice when things happen in your knowledge base: an article is created, updated, published, archived or deleted, a comment comes in, or a reader submits your contact form. You can limit notifications to specific knowledge bases, or even a single category. If you've used our Slack notifications, this is the same handy idea, for Teams. KnowledgeOwl Assist for Freshservice and Freshdesk
This one brings your knowledge base right into your Freshservice and Freshdesk tickets, so agents can find answers without leaving the ticket. KnowledgeOwl Assist: Suggests articles based on the ticket subject Lets agents search the knowledge base and read full articles inside the app Copies an article's link to drop into a reply Creates a new article from a ticket in a Problem and Solution format (a lovely way to capture answers while they're fresh)
Agents don't need a KnowledgeOwl author license, since the app connects with an API key. KnowledgeOwl Sync for Freshservice and Freshdesk
The Sync app will automatically keep your Freshservice and Freshdesk docs in sync with your KnowledgeOwl knowledge base, so you can write once and have it show up where you need it. |
|
| What happens after October? |
|
|
A sneak peek at what's next OAuth 2.0 and OpenID Connect (OIDC) SSO: Our developers are working on native OAuth 2.0 and OIDC single sign-on, giving you another way to log people in alongside SAML SSO. SOC 2: We're currently pursuing a SOC 2 audit. We'll share more once the report is complete.
|
|
| Nest practices: Meet your team where they’re at |
|
|
The best integration is the one your team will actually notice
Every team is a little different. Some live in Slack, some in Teams, some in their ticketing tool all day long. Before you connect anything, it helps to take a quick look at where your people already spend their time, then bring your knowledge base to them.
Step 1: Map where your team works Ask a few questions (a five-minute poll works wonders): Where do people ask each other questions? (Chat, email, tickets, hallway?) Where does support or IT work happen? (Help desk, service desk, CRM?) How do people log in to work tools? (An identity provider like Okta or Entra ID?) Where does content start life before it's in the knowledge base? (Docs, PDFs, another help center?)
Step 2: Pick what to connect |
|
|
| If your team works in... |
Try connecting... |
So that... |
| Slack or Microsoft Teams |
Slack notifications and the Webhooks Slack app, or Teams notifications Coming soon |
Authors see new comments, contact form submissions and article changes without checking the app |
| Zendesk |
Contact form ticketing and the KnowledgeOwl Zendesk app |
Questions become tickets, and agents can find, share and create articles right from the ticket |
| Freshservice or Freshdesk |
Contact form ticketing (Freshservice, Freshdesk), plus KnowledgeOwl Assist and Sync Coming soon |
Questions become tickets, and agents find answers inside the ticket |
| Another help desk |
The contact form, sent to your support inbox by email |
Reader questions land wherever your support team already works (we do this with Help Scout!) |
| Okta, Microsoft Entra ID or another identity provider |
SCIM author provisioning and SAML SSO |
Author access updates itself as people join, move or leave |
| Salesforce or Google |
Salesforce SSO or Google log in for readers |
Readers sign in with an account they already have |
| Your own website or app |
The contextual help widget |
Customers get help without leaving your product |
| Another knowledge base |
Importers for Help Scout, Zendesk, Freshdesk, Confluence, Notion, Document360, HubSpot and CSV |
Your content all lives in one well-organized place |
| PDFs, Word docs or Google Drive |
The PDF and Word importers in Pages (PDFs are converted with Owl Intelligence), or Google Drive embeds |
Extract files into editable articles, embed them, or turn them into shareable links |
| Zapier and other automation tools |
Our Zapier app and webhooks |
New articles, contact form submissions and more can trigger the workflows you already have |
| AI assistants |
Our API, plus the API guide for AI coding assistants |
Your assistant works with your knowledge base safely |
|
Step 3: Start small, then grow
Pick the one integration that removes the most daily friction, set it up, and check in with your team after a couple of weeks. Did it help? Is anything noisy? Tweak the settings (notifications especially), then add the next one. Not sure where to start? Reply to this email and tell us a bit about your tools. We love this kind of puzzle. |
|
| |
Catch up on October's sessions, and save your seat for the next one Our free, every-other-week learning sessions kept rolling through October. If you missed them, the recordings are ready for you whenever you are: Next session: November 11, 2026 at 11:00 Eastern, on Optimizing content for AI Writing for both humans and robots
All knowledge base authors are contending with a somewhat new audience: AI. We know it can be a minefield trying to figure out what you should do. Whether you're using our AI chatbot or you know your readers are using AI to access your knowledge base, this session will cover best practices to keep your content more accessible by AI tools.
In this session, we'll cover several tried and true best practices that will help your content remain accessible and useable by AI without compromising on the human reader experience.
What we'll cover In this Wisdom Wednesday session, we'll walk through several content best practices for writing for AI, including: Using a custom llms.txt to provide AI tools more guidance about your knowledge base Using a custom robots.txt file to allow or disallow certain AI tools or training models from accessing your knowledge base General content best practices for AI: what we follow and what we don't (and why) Content best practices for improving your AI chatbot's performance How Kate has changed some of our style guide standards in the age of AI
Who should attend This session is for you if: You're a KnowledgeOwl author or admin. You want to make sure your content is written in ways that the robots like (or at least don't hate enough to aggressively hallucinate bad answers from). You're using our AI chatbot and you want to make sure it performs well over time. You're lacking confidence that you're doing the right things to keep your knowledge base relevant in the age of AI.
Can't make it live? No sweat! Register anyway and we'll send you the recording. 💙 |
|
| | | In case you missed it: $500 for referrals |
|
| We recently launched a new customer referral program!
If you refer a friend or colleague to KnowledgeOwl, we will give you $500 USD to thank you for your help.
We get a remarkable amount of our new customers from existing or former customers, and we’d like to start rewarding folks for helping us out with these referrals.
To be clear: this thank you gift is to be paid to you, the individual; not to the company you’re working for. You can see details on the program here. |
|
| | | |
The Not-Boring Tech Writer: Audio description, collaboration and women in tech comm |
|
|
|
Scripting audio description for film, TV, and video games with Jenna JennissaryIn the October 1 episode (S3:E46), Kate talks with Jenna Jennissary, a producer at Descriptive Video Works who works mostly on video games and still writes and performs audio description herself. They dig into how audio description gets scripted for film, TV and games. Kate sounds off on collaborative workIn the October 15 episode (S3:E47), Kate shares her latest content updates progress and reflects on her takeaways from Jenna's interview (S3:E46), with a focus on collaborative work. Telling the stories of women in technical communication with Sharon BurtonIn the October 29 episode (S3:E48), Kate chats with Sharon Burton, a technical content strategist who has taught technical communication to engineering students at the University of California, about the stories of women in technical communication. |
|
| | | | Thank you from the team at KnowledgeOwl!
We’re so happy to have you with us!
Let us know what you think of the updates. We always love to hear from you! 💌 |
|
| |
|
|
|
|
|
|
|
|
|
| | | |
|
| |
|
|
|
|