Mention Documentation¶
Mention is where your product story lives. It connects to the tools your team already uses — Notion, Confluence, Google Drive, Dropbox, Box, GitHub, Slack, Intercom, and Microsoft Teams — and turns what is scattered across them into the answers everyone in the company needs about what you are building.
That is alignment: one answer per question, held where everyone can find it, and honest about the questions nobody has written an answer to.
Every question your company keeps asking¶
The same questions follow your work around — in standups, in support tickets, in the sales call happening right now. Who is this for? How does it actually work? When will it be ready?
Mention records each one once, for the whole organization, in the words it was asked in, with a count of how often and by how many people. It answers what your material supports and files the answer under the topic it belongs to. It also seeds the questions a new audience will need answered, so the obvious ones are answered before anybody gets there.
A question your sources cannot answer is not a blank — it is a gap with a name on it, waiting on the audience that needs it and the owner who can settle it. See Topics and Questions.
Where you land¶
Sign in and you go straight to the work. Everyone lands on Chat in their first Audience — grounded questions in their own words, with the most-asked answered questions listed beside the conversation. Members get Lessons, Review, and the Exam once it opens in the sidebar. Org admins also get Conflicts there, which collects the contradictions only a person can settle: things somebody said that your sources contradict, and things your sources say that cannot both be true. When everything is clear it says "Nothing needs you."
Open questions — the ones your sources did not answer — live on each Audience's Gaps tab and nowhere else, with the owners who can settle them, because they are work rather than reading material. Everything settled reaches you where the work already is: served instantly when the question is asked again, surfaced with its ask count in the FAQ beside Chat, or as a definition opening on the term anywhere it is written.
Durable knowledge and the volatile kind¶
The two do not belong in the same place, so Mention keeps them apart.
- Articles carry what stays true — how the thing works, why the rule exists, what to do in the messy case. Mention writes each one from your activated sources, and composes a lesson from it so the material is something people know rather than something they once skimmed.
- Answers carry what moves — a ship date, a current status, a price. They are stored against the question they answer, they cite the facts behind them, and they go stale on their own when those facts change, so nobody quotes last quarter's date with confidence.
Who is Mention for?¶
Mention is built for organizations that need to:
- Keep everyone current on how the work is done — one answer per question, instead of six people guessing in six threads
- See what nobody has written down — the gaps, ranked by who is asking
- Onboard new employees quickly — reduce time-to-productivity by turning scattered docs into a short set of focused lessons
- Make institutional knowledge accessible — stop losing knowledge in documents nobody can find
- See what has landed — track what each member has actually been graded on, and whether they are still current
How it works¶
Mention operates in three phases:
- Ingest — Connect your content sources and select which documents matter. Mention ingests them automatically, and builds a glossary of your terms as it reads — the topics among them are what the questions it seeds for each audience are grounded in.
- Ask — An audience owner says what that readership needs answered. Mention searches your sources with those questions and proposes the audience's Contents: entries, each one a name and a prompt describing what the article should cover.
- Learn — Mention writes each entry into an article from your source material, and composes a lesson from it: a short sequence of exercises the member works through by attempting things. Finishing the lesson unlocks the article to read whenever they want.
Learn more in How Mention Works.
Two roles, two experiences¶
| Role | What you do |
|---|---|
| Admin | Connect content sources, create audiences, invite members, and administer every audience |
| Member | Work through your audience's lessons, read the articles behind them, ask questions, and flag anything that is wrong |
Curating an audience — writing its Contents, tuning the lessons composed from it, answering the questions owed to it, and seeing who knows what — is the job of that audience's owner. Owner is a per-audience role, not an org role: an org member can own an audience, and an org admin is not automatically its owner.
Get started¶
- Admins — Follow the Admin Quickstart to set up your organization and get your first articles written.
- Members — Follow the Member Quickstart to finish your first lesson.
Explore the docs¶
| Section | What you'll find |
|---|---|
| Core Concepts | Understand Sources, Assets, Audiences, Contents, articles, lessons, topics, questions, and how they fit together |
| Admin Guide | Step-by-step guides for every admin workflow |
| Member Guide | Everything members need to know about lessons and articles |
| Integrations | How to connect each supported content source |
| Billing | Plans, pricing, and how credits work |
| FAQ | Answers to common questions |