Team library · free
A team knowledge base that's never out of date.
Write playbooks, interview kits and onboarding guides together. Nothing goes live until it's approved, every guide lives at one link that never goes stale, and you can see who has read the latest version.
How it works
From draft to the guide everyone uses, in four steps.
- 1
Make a library, bring your team
One per team or purpose: hiring, onboarding, support. Add people by email and give each a role. - 2
Write in a real editor
Headings, lists, images, video and code, in the same editor as Aqvil articles. Or bring in an article you've already written. - 3
Approve before it's live
Editors send drafts for approval. A second person approves it, or sends it back with a note. - 4
Share one link, for good
Members read it at one address that never changes. Candidates and guests get a read-only outside link.
Try it
Change the guide. Keep the link.
Take a guide through the approval flow and watch what readers see. This is a demo; nothing is saved.
The draft · editors
Joining your video interview
Live- Join from a laptop with the link in your invite.
- Allow camera and microphone when your browser asks.
- → Version 3 approved by a publisher
What readers see
Joining your video interview
- Join from a laptop with the link in your invite.
- Allow camera and microphone when your browser asks.
Roles and permissions
Everyone gets exactly the access they need.
Five roles, each adding to the one before. Reviewers can comment on a draft without being able to edit or publish it.
| Can… | Reader | Reviewer | Editor | Publisher | Owner |
|---|---|---|---|---|---|
| Read approved guides | Yes | Yes | Yes | Yes | Yes |
| Read drafts and leave feedback | No | Yes | Yes | Yes | Yes |
| Write drafts and send them for approval | No | No | Yes | Yes | Yes |
| Share a draft with a 7-day preview link | No | No | Yes | Yes | Yes |
| Approve and publish, or send back with a note | No | No | No | Yes | Yes |
| Make outside links for candidates and guests | No | No | No | Yes | Yes |
| See read reports and export the library | No | No | No | Yes | Yes |
| Manage members, the approval rule, webhooks and Chronika | No | No | No | No | Yes |
Red pen
Why not just a shared folder?
Copies of copies, saved on people's laptops
One approved version, at one link
Anyone with access can overwrite the file
Reviewers comment; only publishers publish
Every update means resending attachments
The link already in your templates shows the update
No idea who read the new version
See who has opened the latest version, and who hasn't
Feedback lost in email threads
Notes pinned to the draft they're about
Backups mean saving files one by one
The whole library in one download
What you get
Everything a team's guides need, and nothing public.
Approval before publishing
A second person approves every version by default. Drafts lock while they wait, so nobody approves text they haven't read.Version history
Every approved version is kept with who approved it and when. Copy any of them back into the draft.Links that never go stale
One address per guide, through every edit and rename. Outside links for candidates keep their address across approvals too.Read reports
Reads by date, folder, team and member. Guides nobody opened. Who hasn't seen the latest version. Download it as CSV.Feedback beside the draft
Reviewers leave notes on the draft itself, marked as on this draft or an earlier one, so nothing gets lost in email.Webhooks for your tools
Signed events when a guide goes live, changes its link or comes down, so your ATS, CRM or template tool stays in step.Only the alerts you want
Approval requests, decisions and feedback, in the bell and by email, with separate switches for approvals and feedback.One-click backup
The whole library as Markdown or JSON: drafts, every approved version, feedback and history.Private by default
Never in search, topics, feeds or profiles. Search engines are told not to index it. Outside links are yours to turn off.
Built for
For any team with guides that have to be right.
Hiring and interviews
Interview kits, scoring rubrics and panel training, approved before a single interviewer uses them.Candidate guides
How to join the interview, what to prepare, who they'll meet. One outside link in every invite, always current.Onboarding
First-week checklists and how-we-work guides, with a list of who hasn't opened the latest one.Support and operations
Standard procedures and runbooks that change often, with a record of what changed and who approved it.Sales enablement
Pitch notes, objection handling and product one-pagers your whole team reads from the same page.Policies
Internal policies with an approval trail, version history and a one-file export for audits.
Questions
Team knowledge base FAQ
What is a team knowledge base?
One shared place for the guides a team relies on, like playbooks, interview kits, onboarding notes and standard procedures, so everyone works from the same current version instead of copies saved on their own machines.
Is it private?
Yes. Only the people you add can open a library. Its guides never appear in Aqvil search, topics, feeds or anyone's profile, and its pages tell search engines not to index them. You decide if a guide is shared outside the team, one link at a time.
Can someone see a draft without being able to edit it?
Yes. Give them the Reviewer role: they read drafts and leave feedback, but can't change a word or publish. For someone outside the library, an editor can make a read-only preview link that works for seven days.
Can a guide go live by accident?
Not by default. Editors can only send a draft for approval, and a publisher who didn't make the last edit has to approve it. The draft is locked while it waits, so what gets approved is exactly what was read. Small teams can let publishers publish their own edits instead.
Can candidates or customers read a guide without an account?
Yes. A publisher can make an outside link for any approved guide. It's read-only, needs no account, shows only the approved version, and can last until you turn it off or for 30, 90 or 365 days.
Do links break when I update a guide?
No. Each guide keeps the same address through every edit, approval and rename, and always shows the latest approved version. Paste it into your templates once. If you ever need a fresh address, replacing the outside link turns the old one off at once.
Can I see who has read a guide?
Publishers see reads by date range, folder, team and member, which guides nobody opened, and for each guide which members have opened its latest version and who hasn't. Visits through outside links are counted without accounts or IP addresses. Reports download as a spreadsheet.
Does it work with our ATS or CRM?
Through signed webhooks. When a guide is published, unpublished, deleted or its outside link changes, Aqvil sends your endpoint the guide and its links, so a small script or an automation tool can update the templates that use them. There's no one-click connector for a specific ATS yet.
Can we bring in guides recorded with Chronika?
Yes. The library's owner connects a Chronika workspace from the Members tab. Each guide recorded there, one step per click with its screenshot, arrives as a draft in the folder you choose, sent for approval if you like. Chronika can update its drafts but never publish them: a publisher here still decides what readers see.
Can we export everything?
Yes. Any publisher can download the whole library in one file: Markdown to read, or JSON with every draft, every approved version, the feedback and the history. Handy for backups, audits and handovers.
Is it free, and how big can a library be?
It's free. A library holds up to 1,000 guides and 200 members, and each person can own up to 20 libraries. Everyone you add needs a free Aqvil account.
Can I use it on my own?
Yes. Switch the library to let publishers publish their own edits, and you get private guides with version history, stable links and read counts, without waiting for anyone.
Stop resending the latest version.
Create a free account, start a library and invite your team. Your first approved guide can be live today.
More on Aqvil
A pastebin with a pen →
Private notes and snippets you can mark up and share with a password.
LinkedIn posts, kept →
Turn the posts you've written into articles people can find later.
Case studies that get read →
A simple structure that turns a project into proof.
Explore Aqvil →
Articles, experts, businesses and case studies.