Add sources
Add documents, web pages and notes to your knowledge base, label them, and choose who gets answers from each and which projects it’s for.
Sources are what your knowledge base knows: the documents, help pages and notes your team relies on. Once a source is added, your team can ask questions about it in Ask, AI workers can search it, and the customer-facing ones can become help articles. For each source you choose who gets answers from it, and which projects it’s for.
Open Knowledge › Sources in the sidebar. Every member of the workspace can add sources.
Add a source#
Choose Add source, then one of three tabs.
| Tab | What you give it | Limits |
|---|---|---|
| Upload a file | A PDF, Word (.docx), Markdown, text or HTML file | Up to 25 MB, one file at a time |
| Link a page | The address of a public web page | The page can be HTML, PDF or plain text, up to 5 MB |
| Paste text | A title and the text | Up to 2,000,000 characters |
Tick the Projects and Categories that apply, then choose Add source.
- Who can get answers from it appears for owners, admins and support agents. Tick Your team, Customers or both, as in Who a source is for. For anyone else, a new source is for your team only.
- Projects are optional, unless Customers is ticked: then tick at least one, because customers get answers in those projects’ support portals. With none ticked, the source is for the whole workspace. See Sources for some projects.
- A file’s Title is optional. Left empty, it’s taken from the document.
- A linked page can be fetched again Weekly or Daily, or Never. A page that hasn’t changed isn’t processed again.
- In pasted text, Markdown headings (
#,##) become the sections that answers cite.
A workspace can hold up to 1,000 sources.
From project documents#
A document already in a project doesn’t need uploading again. Owners and admins open it in the project’s Documents and turn on Use in knowledge base (Project documents). It shows here with From project documents under its title, which opens the document. It starts as for your team and that project only; you can change who it’s for here like any source. A new version of the document is read again by itself. Files uploaded here are checked for viruses, as documents are.
Processing#
A new source shows Processing while Projik reads it and splits it into passages. The list updates by itself. It then shows one of:
- Ready, with the number of passages. It can now be used in answers.
- Failed, with the reason. Depending on what went wrong, the row offers Try again (a page or service was down) or Paste the text instead (the content couldn’t be read).
Processing sources doesn’t use your AI allowance.
Who a source is for#
Owners, admins and support agents choose who a source is for when they add it. They can change it later, once it’s Ready.
- On the source’s row, choose Who it’s for.
Under Who can get answers from it, tick one or both:
- Your team: Ask, knowledge base search and AI workers in Projik.
- Customers: help articles in the support portals of the source’s projects.
- Under Projects, choose Whole workspace or Only these projects, and tick the projects. A source for customers needs at least one project.
- Choose Save.
The For column in the list shows Team only, Team and customers or Customers only, with the source’s projects, or Whole workspace.
Customers doesn’t mean customers can read the source. They never see a source itself. It means the source can be used to draft help articles for its projects, which customers see only after someone on your team publishes them.
A source for Customers only stays in your list, and you can still draft articles from it, but Ask, search and AI workers don’t answer from it. Use this for wording written for customers that your team shouldn’t take as internal guidance.
Sources for some projects#
A source for Only these projects is found only by people who can see one of them. Someone limited to some projects (see Project access):
- sees, in Knowledge › Sources, the sources for the whole workspace and those for their projects, and no others
- gets answers in Ask, and citations that open, only from those sources; the same goes for an AI worker limited to some projects
- adds sources for their own projects: with none ticked, a new source is for all of the projects they can see, never the whole workspace
If they’re an admin or support agent too, they can change who a source is for, but only for their own projects: projects they can’t see stay on the source, and only someone who sees every project can make a source Whole workspace or limit one that is. On a source that’s also for projects they can’t see, they can change its projects but not who can get answers from it.
People who see every project see every source, whatever its projects.
Sub-projects#
A source for a parent project is for its sub-projects too (see Sub-projects). If it’s for Customers, articles for a sub-project’s support portal can be drafted from it, and they’re shown there. A source for one sub-project is never used for another.
If a sub-project is later moved out of its parent, the articles on its portal that came from the parent’s sources stop being shown there straight away.
Changing your mind#
You can stop customers getting answers from a source, or take a project off it, at any time. If published articles cite the source for a project it would no longer cover, Projik names them first and asks you to confirm. Confirming unpublishes those articles at once and sends them back to review.
Categories#
Categories are labels for sorting sources and narrowing a question in Ask. Any member can change a source’s categories: open the ⋯ menu on its row and choose Categories….
The list of categories is managed in Settings › Knowledge by owners, admins and support agents. There you add, rename, describe, reorder and delete them, and choose who sees each one:
- Staff only: a label for your team. New categories start here.
- Customers: can also be put on help articles, and appears in the portal once it has published articles.
Making a category staff-only, or deleting it, takes it off the articles it was on. The articles stay published.
Find, refresh and remove#
Search by title, filter by category, or use the All, Team only and Customer-facing tabs. Customer-facing lists every source customers get answers from, whether or not your team does too.
In the ⋯ menu on a row:
- Fetch again (a linked page) or Process again (a file or pasted text) re-reads the source. The person who added it, or an owner, admin or support agent, can do this.
- Remove deletes the source. The person who added it, or an owner or admin, can do this.
When a source is updated, by a refresh or a scheduled fetch that finds changes, published articles that cite it stay live and are flagged Needs a look.
How internal content is kept from customers#
- Sources are for your team only until someone on the support desk says otherwise, project by project.
- Help articles are drafted only from sources that are customer-facing for the article’s project.
- Publishing an article re-checks every source it cites, and the portal checks again each time an article is read.
- Ask is for your team. It answers from the sources your team can get answers from, for the projects each person can see, and marks the ones customers don’t get. Customers can’t use it.
Plan#
The knowledge base is part of the Team plan and above. On a plan without it, your sources are kept, but you can’t add or refresh them or use Ask. See Plans and billing.