# Wiki: The wiki for your team > Your company's wiki: pages and subpages in a tree for processes, onboarding and decisions. Every change is kept as a version, the full text is searchable, and images and comments sit on the page. The AI knows what is written here and names the page as its source. - Page: https://www.ciro-noise.de/funktionen/wiki - Deutsche Fassung: https://www.ciro-noise.de/funktionen/wiki.md The new colleague asks for the third time how quotes get approved, and the process exists in three versions of one document. In the CIRO NOISE company wiki you write down processes, onboarding and decisions once. Your team finds them through search or asks the AI, which answers with a link to the page. Every change is kept as a version. ## Your team's knowledge base The wiki is your company's page tree. Areas such as onboarding, processes, customers or tech form the roots. Below them sit pages and subpages, plus folder pages that only group other pages. You write as in any document, with headings, lists, tables, code and images, and you don't have to learn a syntax. You drop images straight into the text, comments sit below the page, and with an @-mention in the text or in a comment you pull in exactly the colleague who knows the answer. It is built for companies of three to fifty people where nobody documents full time. That is why the wiki start page shows you which areas people are writing in and what changed recently. Under “Due for review” you find the pages nobody has touched in 180 days. You notice that a page is going stale before someone acts on it. Whoever watches a page sees every change on their dashboard. The wiki is linked to the other features. A task on the board links to the wiki page with the description, and the page links back to the task. You save the solution of a support request as knowledge with one click, so nobody rewrites this morning's answer. When someone asks the AI “How do we book travel expenses?”, it answers from the wiki and names the page where it is written. The global search shows wiki pages, tasks and customers in one result list, wherever you are. You set per role who reads the wiki and who writes. You mark individual pages as confidential, say a draft contract. The AI and external AI access leave those pages out, unless the person asking explicitly holds the permission. In the wiki itself, everyone with read access sees them. Versions are kept indefinitely, and you can export the whole wiki and take it with you at any time. ## What your team writes down, it finds again Processes, onboarding and decisions in one place everyone knows. - **Build the structure as deep as you need**: Areas as roots, below them pages, subpages and folder pages, as many levels as needed. Every page has its place in the tree, and every person a way there without guessing. - **Change without losing the old version**: Every change is recorded as a version, with person and time. Edits within ten minutes count as one. You see what applied before and restore it with one click. - **Find the page with a single word**: Full-text search covers the title and text of every page and highlights the hit. In the global search the wiki page sits next to the task and the customer it belongs to. - **See what is going stale before someone reads it wrong**: “Due for review” lists the pages unchanged for 180 days. Next to it, the start page shows which area people are working in and what changed recently. So you see at a glance where a page needs care. - **Let the AI answer from it**: Ask the AI in the bar, and it answers from the wiki with a link to the page. It leaves confidential pages out and sees only what you are allowed to see yourself. ## Three days when your team looks things up instead of asking The new colleague's first day, a process change and a question in the middle of a customer call. ### Nele, day 1: one link instead of four chat messages Kira sends Nele the link to the “Onboarding” area. Nele reads up on accounts, contacts and the approval process, with screenshots right in the page. On the step she does not understand, she comments with @Pascal, and Pascal answers below the page, where the question is. Nele watches the page and hears when something changes. - Area with subpages - Images right in the page - Comment with @-mention - Watch the page ### The approval process changes, and everyone knows which version applies Lena adjusts the approval process because larger quotes are now checked by two people. The old version stays as a version with person and time, the new one is in search immediately. Whoever watches the page sees the change on their dashboard. Kira sees on the wiki start page that something happened in “Processes” without anyone announcing it. - Version with person and time - Restore with one click - The change on the dashboard of everyone watching - Activity per area ### “How did the reverse-charge note go again?” Ms. Sommer asks on the phone about the invoice to the subsidiary in Vienna. Lena types the question into the bar, and the AI answers from the wiki page “Invoices to other EU countries” with a link to it. The AI only shows Lena pages she is allowed to open herself. Lena reads Ms. Sommer the sentence written there and does not have to call back later. - The AI answers with the source - Search finds it in other words too - Confidential pages stay out ## The wiki in detail Page tree, versions, search and permissions at a glance. - **Page tree with subpages**: Areas as roots, below them pages, subpages and folder pages that only group. - **Editor with tables and mentions**: Headings, lists, tables, code and images. You bring in colleagues with an @-mention right in the text. - **Version history and restore**: Every change is recorded, edits within ten minutes count as one. View and restore, with person and time. - **Full-text search**: Searches the whole page text and highlights hits. Wiki pages also show up in the global search across all features. - **Permissions and confidential pages**: Read and write per role. Confidential pages are invisible to the AI and to external AI access, unless the permission is explicitly granted. - **Import from Notion and Confluence**: Bring existing pages over from a Notion or Confluence export file, with structure and tables. Images and permissions stay in the old tool. - **Images and comments**: You drop images right into the page, and comments with @-mention sit below it. - **Watching**: When a watched page changes, it shows up on your dashboard. - **Wiki start page**: Shows per area how many versions are created each week, what changed recently and, under “Due for review”, the pages unchanged for 180 days. - **Links**: Task and wiki page link to each other, and a finished task becomes a wiki page with a link back in one click. ## Tell Claude. CIRO NOISE records it. ### Ask the wiki > How do we actually handle a complaint, from the first report to the credit note? Sum it up from the wiki and tell me where pages contradict each other. Here's how a complaint works at your company: 1. Log the report in support 2. Review the case and find the invoice 3. Reply to the customer within 24 hours 4. From €250, the head of accounting approves 5. Create the credit note under Finance 6. Close the request The pages disagree on approval: “Complaint process” (Processes, as of March 2025) still says €500 and management. “Credit notes” (Finance, as of June 2026) says €250 and the head of accounting, and that's how both cases in June and August were approved. ### Add content > Bring the complaint process in line with the “Credit notes” page, add the partial credit notes from Tuesday's support meeting and link the reply template. The complaint process now says approval from €250 by the head of accounting and links the reply template “Credit note issued”. The new section “Partial credit notes” holds Tuesday's decision: only delivered items are credited, and the reason goes into the reply. Below it is the new page “Example: partial credit note” with the case from August. Lena presents the process at the support meeting on Oct 13 (SUP-12). You'll find the previous version under Versions. ### Clean up > Which pages under Processes hasn't anyone touched in over a year? Check whether they're still right and hand the questionable ones to the people responsible. 9 pages under Processes are older than a year. Six are still right, three are out of date and now sit with their owners: • “Vacation requests” still describes the paper form – ORG-40 for Sabine Kurz • “Travel expenses” lists the old flat rate – ORG-41 for Petra Lang • “Key handover” sends visitors to the old front desk – ORG-42 for Ömer Yıldız Each of the three pages now shows “Being revised” at the top, with its task. ## Frequently asked questions ### Does the wiki replace a separate knowledge base? Yes. The wiki is your company's knowledge base: processes, onboarding, customer know-how and decisions live as pages in a tree, with versions and full-text search. Because the wiki sits next to tasks, requests and customer records in CIRO NOISE, the AI also answers from those areas and links the right page. ### Can I move over from Notion or Confluence? Yes. Under Organization › Import you upload the export file: the page tree, text, headings, lists, tables and code come along, Notion databases as tables. Everything lands in its own folder that you sort at your own pace. Images and attachments you add again where needed. ### How does my team find what it's looking for? Full-text search covers every page and highlights the match, and the page tree nests as deep as you like. Whoever prefers to ask asks the AI: it answers from the wiki and links the page the answer came from. ### How does the wiki stay current without a full-time editor? The start page lists every page unchanged for 180 days under “Due for review.” Anyone watching a page hears about every change, and anyone who spots a gap comments right on the page. Your team maintains it along the way and skips the yearly cleanup. ### Can I share pages with a small circle only? Only through roles: they decide who reads the wiki and who writes, for all pages. You can mark individual pages as confidential, and then the AI and connected AI tools leave them out unless the person asking holds the permission for confidential knowledge. In the wiki itself, everyone with read access also sees the confidential pages. ### Can Claude write wiki pages for me? Yes. Claude connects to your organization and searches, reads, creates and updates wiki pages, with the permissions of the person who grants access. A how-to written in a conversation with Claude is then in the wiki for your whole team. ### Can I go back to an earlier version? Yes, with one click. Every page keeps its versions, you see the differences and jump back to any earlier state. The current state is saved first, so nothing is ever lost. ## CIRO NOISE at a glance - CIRO NOISE is a workspace for small businesses and teams of up to about 50 people: wiki, tasks, customer requests, finance with quotes and invoices, customers (CRM), meetings, knowledge with AI, social media, password vault, and time tracking behind one login. - Price: the first 2 seats are free, with every feature. Each additional seat costs €25 per month plus VAT. No credit card to start. - Privacy: servers and AI run in EU data centers, content never trains AI models, and permissions apply per person and feature. - AI connection: Claude and other AI assistants connect through MCP, the open standard for AI tools, with exactly the permissions of the person. - Provider: CIRO GmbH, Eching, Germany. Contact: hello@ciro.gmbh, phone +49 89 24 88 31 22.