For Universities & Colleges
A Knowledge Base Per Department, Without Per-Student Pricing
Your departments already write policies, handbooks and procedures in Notion. HelpKit publishes them as searchable sites on your own domain, priced per knowledge base rather than per reader, so serving thousands of students costs the same as serving ten.
The Best Companies Are Using HelpKit
Per-seat pricing does not survive contact with a campus
Knowledge base tools priced per user assume every reader has a login you pay for. No institution is buying seats for its entire student body, so those tools get used only by staff, and students keep emailing.
Every department runs its own island
The registrar, IT, the library and each faculty maintain separate documents in separate places. One shared platform with separate sites per department keeps ownership local and the experience consistent.
Policy PDFs nobody opens
Course handbooks and procedure documents live as PDFs on a page nobody can search. The information exists; it just cannot be found at the moment a student needs it.
What you get
Everything included, nothing to build
Priced per knowledge base, not per reader
Publish to an entire student body at the same cost as a small team. Budget stops scaling with enrolment.
Public, restricted and staff-only in one workspace
Student-facing guides stay open, staff SOPs sit behind password, approved email list, or JWT through your existing SSO.
A separate site per department
The registrar, IT and each faculty run their own knowledge base from one account, so nobody wades through another department's material.
Searchable instead of downloadable
Policies become searchable pages with AI answers on top, rather than PDFs that need opening to find one sentence.
Control exactly who gets in with protected access
Universities publish to several audiences at once: prospective students, enrolled students, faculty, and staff. Each set of documentation can carry its own access rule, from fully public to staff-only behind your existing single sign-on.
-
Password protection
- Protect your whole site with a single password. The simplest and most efficient access control, and you can rotate it whenever you need to.
-
Restricted email list
- Define exactly who can access your site with an approved email list. It lives in Notion, so it works with Zapier and Make out of the box.
-
Custom backend authentication
- Authenticate visitors with your own login system and fully control who gets in. Ideal for internal documentation and enterprise portals.
Powered by HelpKit AI
Students and staff ask, your handbook answers
Nobody reads a 90-page policy PDF. HelpKit AI is trained on your own documentation, so students and staff ask a plain-language question and get the answer with a link to the source page.
- ✓"When is the add/drop deadline?" answered in seconds, with the policy cited
- ✓Cuts repeat questions to registrar, IT and departmental admin inboxes
- ✓Works behind protected access, so staff-only material stays staff-only
Why your docs belong in Notion
The docs tool your team already knows how to use
Everyone can edit, today. Your team writes in Notion already, so there's no docs platform to learn, no markdown to teach, and no developer bottleneck between "we should update that article" and it being updated.
Docs stay current. Documentation goes stale when updating it is a chore. Editing a Notion page is not a chore, which is why Notion-based docs actually get maintained.
One source of truth. Your knowledge lives in one workspace instead of being copy-pasted into a separate docs system that drifts out of date the same week.
HelpKit adds the pro layer. Notion is the editor; HelpKit is the publishing engine: your domain, search, AI answers, analytics, and access control on top of the pages you already have.
How it works
Your help center, live in three steps
- 1
Write in Notion
Departments keep their handbooks, policies and procedures where staff already draft them.
- 2
Publish per department
Each gets its own branded site and access rules. About 15 minutes each.
- 3
Share one link
Students and staff search instead of emailing. Updates publish the moment a policy changes.
Education is the stickiest segment on HelpKit: these knowledge bases average well over two years in service, and one university runs three separate departmental sites from a single account.
Included on every plan
Everything a professional site needs
Fully branded
Your logo, colours and typography. No HelpKit badge on paid plans.
Your custom domain
Serve on help.yourdomain.com with SSL included, so SEO authority stays yours.
Multilingual
Run several languages from one workspace, without a duplicate system per market.
Instant search
Full-text search that returns answers as visitors type, across every article.
Insights that name gaps
See what people searched for and did not find, so you know which article to write next.
Protected access
Public, password, email allow-list or JWT via your own login. Set it per project.
Embeddable widget
Answers inside your product, without sending anyone out to a browser tab.
AI-readable by default
llms.txt and clean semantic markup, so assistants can quote your docs correctly.
Edits go live instantly
Publish from Notion. No rebuild, no release, no ticket to the web team.
With Helpkit we literally went from 0 to fully functional knowledge-base in 1 hour! The best thing about Helpkit is it allows my non-technical co-founder to do 95% of the work and manage our knowledge-base. We signed up because of how beautiful and well-designed the product is!
Testimonial from Dan Kelly
CEO at Adjust Square
Frequently asked questions
How does pricing work for a whole university? +
HelpKit is priced per knowledge base, not per reader. A department publishing to 30,000 students pays the same as one publishing to 30 staff. Institutions typically run one project per department rather than one giant site, which keeps ownership with the team that writes the content.
Can staff-only content sit alongside student-facing pages? +
Yes, as separate projects from the same Notion workspace. Student guides stay public and searchable; staff SOPs and internal procedures sit behind protected access, including JWT so your existing single sign-on decides who gets in.
Do students need an account to read it? +
No. A public knowledge base is a normal website on your domain: students search and read with no login. Only protected areas require authentication, and that runs through the identity system you already have.
Who maintains it once it is live? +
Whoever owns the policy. Because editing the knowledge base means editing a Notion page, departmental administrators update their own content without a ticket to IT or the web team, which is the main reason these sites stay current.
Can we run it in more than one language? +
Yes. Multilingual knowledge bases are supported, which matters for institutions with international student populations or bilingual requirements.
Ready to turn your Notion pages into a
professional
Join 1000+ happy customers reducing their support ticket load and getting customers to their answers quickly.