The knowledge base in CIRO NOISE keeps your company's know-how in one place, so nobody has to answer the same question twice. You'll find it in the navigation under "Knowledge". There you search all sources at once and maintain your own entries.
The knowledge base draws on pages from the wiki, documents from your file storage and attachments, FAQ entries your team writes as question and answer, approved solutions from support requests, meetings with their summary, concept boards, tasks with a description and up to five websites. The AI assistant Isa checks the knowledge base first and links the source in every answer. Under the hood, this is a RAG system.
How the knowledge base works in CIRO NOISE
Wiki pages, documents, meetings, concept boards and tasks with a description are added automatically. For each wiki page you decide whether it’s searchable, confidential or excluded. Private meetings, which only their participants can read, are never added. The search index refreshes every five minutes, so a changed page is findable in its new form within a few minutes.
FAQ entries and support solutions are curated knowledge. Solutions that CIRO NOISE drafts from resolved requests wait under "To review" and only become searchable once approved, so nobody passes on an unchecked answer. Entries written by someone with write access apply immediately. Search finds an entry even with different words, in English and German.
An everyday example
For the third time this month, a customer asks support how to change their billing address. Jonas answers the request and then clicks "Save as knowledge". He checks the question and answer and saves. Next time, Mara finds the solution through search, and the AI suggests it with a link.
Permissions and confidential content
Roles decide who can read the knowledge base. Only people with write access to knowledge can create and approve entries. Entries, wiki pages and restricted meetings marked as confidential appear only for roles with the confidential knowledge permission, and they don't even count towards the totals for anyone else.
How it differs from the wiki
The wiki is where your team writes processes down in detail. The knowledge base is the search across it, plus short question-and-answer pairs from daily work. So a good wiki page never needs to be created twice.