Org Wiki

The Org Wiki is the place where your company writes down what it knows: firm standards, estimating rules, safety procedures, vendor notes, HR policies, price benchmarks and lessons from past projects. Each entry is an article with a short summary and a Markdown body, filed under a category such as Standards, Safety or Estimating.

Office admins and project managers use the wiki so everyone works from the same playbook. Cooper's AI agents use it too: they search and read wiki articles before they act, so what you write here shapes how agents estimate, buy and answer questions for your company. You can write articles yourself, import a web page and let AI turn it into an article, or have Cooper build benchmark articles from your own price, quote and project data.

Key conceptsCopy Anchor Link

Open the Org WikiCopy Anchor Link

1. In the sidebar, open Brain.
2. Click Org Wiki.

The wiki opens at /connect/org-wiki. When you open an article, the address changes to /connect/org-wiki?article=<slug>, so you can bookmark or share it.

You need the Org Wiki permission in the Brain section of your role to see the page. If your company's plan doesn't include the wiki, Cooper shows a plan-locked screen instead. See Permissions.

The page has two parts:

• The left panel: the Org Wiki title, four icon buttons (Search, Ingest URL, New article and Wiki settings), the article list by category, and two maintenance links at the bottom (Reindex categories and Refresh benchmarks).
• The main area: the wiki home, the open article, or Wiki settings.

Click the Org Wiki title at the top of the left panel at any time to go back to the wiki home.

Find your way around the wiki homeCopy Anchor Link

The wiki home opens when no article is selected. It is titled Organization Wiki, with the line "Firm standards, project lessons, benchmarks, and promoted knowledge in one place."

At the top you see three chips: what you are looking at (All knowledge, Search results, or a category), the number of articles in view, and the number of categories.

Filter the home viewCopy Anchor Link

• Type in Search articles, summaries, tags, or contributors to filter the cards as you type. It matches article titles, summaries, categories, tags and the name of the last person who changed the article. Click the clear button to empty it.
• Click a category chip under the search box to show only that category. Each chip shows its article count. Click All to show every category again.
• Click Reset view to clear both the search text and the category.

Choose a viewCopy Anchor Link

Each card shows the category, title, summary, up to three tags, and who last changed the article and when. Click a card to open it. Below the cards, Well-tagged references lists up to four more articles with the most tags and fullest summaries.

Use the side columnCopy Anchor Link

• Category pulse: up to seven categories with the most articles. Each card shows the article count, the last update date, the first three articles and the top three tags. Click the card header to filter the home view to that category, and click it again to clear the filter. Click an article name to open it.
• Topics: the 12 most-used tags. Click a tag to search for it.
• Contributors: the five people who created the most articles.

The home view shows published and draft articles you are allowed to see. Archived articles never appear on the home view. If there are no articles yet, you see "Published articles will appear here once the wiki has content."

Browse articles by categoryCopy Anchor Link

The left panel lists every article you can see, grouped by category.

1. Click All Articles to see the total count and collapse the categories.
2. Under Categories, click a category to expand it. Each category shows its label, a colored dot and an article count. Only one category is open at a time.
3. Click an article title to open it.

Draft articles show a yellow draft badge. Categories are listed in alphabetical order of their slug. If an article's category is no longer in Wiki settings, the category still appears in the list, shown by its slug.

If the wiki is empty, the panel shows "No articles yet".

Search the wikiCopy Anchor Link

Each result shows the title, a match score as a percentage, a source badge (wiki, project or estimate), a snippet of the matching text, the category and up to three tags. Above the results, a line such as "8 results · Keyword search" shows how many results came back and how Cooper searched. If nothing matches, you see "No results found".

Cooper picks the search method from your words:

Search returns up to 20 results and only finds published articles. Drafts and archived articles never appear in search.

Read an articleCopy Anchor Link

An open article shows:

• Breadcrumb: Org Wiki / category. Click Org Wiki to go back to the wiki home.
• Badges: the status (published, draft or archived), the category, default if the article is a default article, and confidence N% if an AI agent recorded how confident it is in the content.
• Title.
• Who changed it: the person who last updated the article, with "Updated · 3 hours ago" and the exact date and time. If an AI agent made the change for that person, you see both names, for example "Dana Lee and Estimator Agent", with both avatars. If a different person created the article, a second line shows who created it.
• Summary: in a shaded box above the content.
• Content: the article body. If the content is empty, you see "No content yet."
• Linked Resources: the Library folders attached to the article. See Open linked documents.
• Tags, Concepts, Backlinks and Entity References at the bottom, when the article has them.

In Backlinks, each linked article shows as [[slug]]. A red link with ✗ means the linked article doesn't exist yet.

If Cooper finds that a new article looks very similar to an existing published article, a yellow banner says "Possible near-duplicate detected: ..." and names the other article. The article is still saved. Review both articles and merge them if they cover the same thing. Click the close button to hide the banner.

Open linked documentsCopy Anchor Link

When an article has linked folders, a Linked Resources panel appears to the right of the article on wide screens, or below the content on smaller screens.

Each folder card shows the folder name, its description, the number of files and subfolders, a Confidential badge for confidential folders, up to three teams that can see the folder, and up to four Featured Documents from inside the folder.

• Click the folder name to open the folder viewer.
• Click a featured document to open the folder viewer on that document.

Confidential folders appear only to members of the teams allowed to see them, and to the workspace owner. Other readers don't see those folders on the article at all. See Teams.

Share an articleCopy Anchor Link

• Click Copy article link (the link icon) to copy the article's address. The tooltip changes to "Link copied!". Anyone with access to the Org Wiki can open the link.
• Click Copy content (the copy icon) to copy the article's Markdown content. The tooltip changes to "Copied!".

Create an articleCopy Anchor Link

If the title has no letters or numbers, you see "Title must produce a valid slug." If the title is empty, you see "Title is required."

Write article contentCopy Anchor Link

Article content is Markdown. The article view supports headings, paragraphs, lists, bold and italic text, links, quotes and code.

• Use ## headings to split the article into sections. Cooper stores each ## section separately, and AI agents can read a single section, for example "Approval limits", without reading the whole article.
• Link to other articles with double square brackets, for example [[procurement-approval-process]]. Use the other article's slug. The link appears under Backlinks on both articles. If the slug doesn't exist yet, the link shows in red with ✗.
• Don't repeat the title as the first heading. If the content starts with a # heading that matches the title, the article view hides it so the title isn't shown twice.
• Avoid Markdown tables. The article view shows Markdown tables as plain text with pipe characters. Use lists or ## sections instead.

Edit an articleCopy Anchor Link

In edit mode you can change the summary, content, linked folders and status. You can't change an article's title, category or tags on this page.

Cooper keeps the earlier content of an article each time it is saved, but the Org Wiki page has no way to view or restore earlier versions. Copy important content with Copy content before you make large changes.

Publish an article or move it back to draftCopy Anchor Link

1. Open the article and click Edit article.
2. Click the status button. It shows published in green or draft in yellow, and switches each time you click it.
3. Click Save.

Articles imported from a web page always start as drafts, so someone can review them before they go live.

Archive or restore an articleCopy Anchor Link

Archiving hides an article without deleting it.

1. Open the article.
2. Click Archive. Cooper archives the article straight away, with no confirmation, and it disappears from the left panel.

To restore an article:

1. Click Wiki settings, and under Archived article visibility click the button so it says Showing. Archived articles now appear in the left panel.
2. Open the archived article and click Restore. The article is published again.

There is no way to delete an article from the Org Wiki page.

Link Library folders to an articleCopy Anchor Link

You can attach Library folders to an article so readers can open the related drawings, specs and forms from the article.

1. In New Wiki Article, or in edit mode, go to Linked Resource Folders.
2. Type in Search folders... to find a folder, or click through the folder list. Use the breadcrumb (starting at Root) to move back up.
3. Select each folder you want. Selected folders appear as chips under the picker. You can select folders at different levels.
4. Create or save the article.

Readers see the folders in the article's Linked Resources panel. Confidential folders are shown only to members of the teams allowed to see them.

Import a web page (Ingest URL)Copy Anchor Link

Ingest URL turns a web page into a wiki article. Cooper fetches the page, strips ads and navigation, and saves the result as a draft for you to review.

Which pages can I import?Copy Anchor Link

• Ordinary web pages. If a page needs JavaScript to show its text, Cooper loads it in a browser and tries again.
• Posts on X (Twitter). Cooper also follows links inside the post.
• YouTube videos that have captions. Cooper imports the transcript.

Cooper refuses internal and private network addresses. Paywalled pages, and pages that block automated readers, may fail.

When a page was already importedCopy Anchor Link

If the same address was imported before, the window says URL Already Ingested and "This URL has already been ingested as ...". You can:

• Click Open Existing Article to go to it.
• Click Refresh Existing Article to import the page again and overwrite that article.
• Click Ingest Another to start over.

If a different address has the same content as an article already in the wiki, Cooper also skips the import and says "This content already exists in the wiki as ..., originally from ...".

To re-import a page you know is already in the wiki, tick Force refresh existing article before you click Ingest URL. Cooper then overwrites the article that came from that address instead of skipping it. This option isn't shown in Merge mode.

Add a web page to an existing articleCopy Anchor Link

Merge adds new information to an article you already have.

1. In Article Title, enter a title whose Slug matches the existing article's slug exactly. The slug decides which article Cooper merges into.
2. Choose Merge and click Ingest URL.

Cooper adds the new section to the end of the article, after a horizontal line, and keeps the article's summary. When Cooper merges, the article also takes the title, category and tags you entered, and its status changes to draft. Publish it again after you review it.

If no article has that slug, Merge creates a new draft article instead.

Promote a note from a project's knowledge graphCopy Anchor Link

You can also turn a Markdown note from a project's or estimate's knowledge graph into a wiki article, for example a lesson learned on one job that should become a company standard.

1. Open the note in the project's or estimate's knowledge graph.
2. Click Promote to org wiki. This button appears on Markdown notes only.
3. In Promote to Org Wiki, fill in Article Title, Slug and Category. All three are required.
4. Choose a Promotion Mode:
   • Generalize for org use: AI removes project-specific names and details and keeps the reusable guidance. Best for lessons learned.
   • Copy markdown as-is: copies the note largely unchanged.
   • Merge into existing slug: adds the note to the end of the wiki article with that slug. The article must already exist.
5. Choose a Status (Draft or Published), and optionally add Tags and Notes for AI.
6. Click Save Draft or Publish to Org Wiki.

Cooper adds the tag promoted-from-kg to promoted articles.

Refresh computed benchmark articlesCopy Anchor Link

Click Refresh benchmarks at the bottom of the left panel to build or update three articles from your live Cooper data. The link shows "Computing..." while Cooper works.

Each article is published right away and tagged auto-computed. If there is no data for one of them, Cooper skips it. The page doesn't show a message when the refresh finishes; open the articles to see the new figures.

Rebuild the category indexesCopy Anchor Link

Click Reindex categories at the bottom of the left panel. The link shows "Reindexing..." while Cooper works.

For each category in Wiki settings, Cooper asks AI to write a short overview of the category's published articles, with each article's slug and one sentence about it. AI agents read these overviews to decide which article to open. The overviews aren't shown on the Org Wiki page.

Cooper also rebuilds a category's overview on its own when an agent asks for it and the saved overview is more than a minute old, so you rarely need this. Use it after large changes, such as importing many articles. If AI isn't available, Cooper builds a plain list of article summaries instead.

Configure wiki settingsCopy Anchor Link

Click Wiki settings (the gear button) at the top of the left panel. The settings open in the main area, titled "Configure how the org wiki thinks and organizes itself".

Choose the AI providerCopy Anchor Link

Under AI Provider, click the provider the wiki should use when it needs AI: summarizing and merging imported pages, generalizing promoted notes, and writing category indexes. Reading, writing and searching articles don't use AI.

Each provider card shows its name (such as OpenAI, Anthropic, Google Gemini or xAI (Grok)), a Verified badge if the key was verified, the key's label or hint, and when it was last used ("Last used ..." or "Not used recently").

You can choose only a provider your organization has an API key for. Providers without one show No org key and can't be selected. If your organization has no keys at all, you see "No org API keys are configured yet. Add them in Organization Settings › Secrets / API Keys, then return here to choose which one the wiki should use." The wiki uses OpenAI until you choose another provider.

Set up categoriesCopy Anchor Link

Under Wiki Categories:

• Category preview shows every category as a chip with its label and slug, for example "Safety /safety".
• Click Add Category to add a row named "New Category".
• In each row, edit the Label (what people see) and the Slug (the short name stored on articles). When you change the label of a category whose slug still matches its label, the slug updates to match.
• Click Remove category (the trash icon) to remove a row. You can't remove the last category.

New workspaces start with these categories: Standards, HR, Accounting, Estimating, Procurement, Safety, Technology, Cost Data, Vendors, Project Management and General.

Removing or renaming a category's slug doesn't move its articles. They keep their old category and still appear in the left panel under the old slug.

The settings page advises keeping the list short and stable: use categories for knowledge areas such as standards, estimating, procurement or safety, not one category per team. Categories don't control who can see or edit articles.

Show archived articlesCopy Anchor Link

Under Archived article visibility, click the button to switch between Hidden and Showing. When it says Showing, archived articles appear in the left panel so you can review or restore them. This applies only to you, takes effect straight away without saving, and resets when you reload the page.

Save the settingsCopy Anchor Link

Click Save Settings. The footer explains: "Changes apply immediately to wiki creation flows, ingestion, and category navigation." Click Cancel or the close button to leave without saving.

How the wiki feeds Cooper's AICopy Anchor Link

Cooper's AI agents, and AI apps you connect to Cooper such as Claude or ChatGPT, use the Org Wiki as your company's reference library:

• Agents search and read articles before they act. For example, an agent pricing a job can search for cost benchmarks, and an agent answering an HR question can read your PTO policy. Agents see published articles only.
• Default articles are given to every agent session. The summaries of up to 20 published default articles are added to the first tool result of each agent session under the heading "Organization Standards". Only an AI agent can mark an article as default. The default badge shows which articles are. Editing a default article on this page keeps it default.
• Category indexes help agents choose which article to open. See Rebuild the category indexes.
• Agents can write to the wiki for you: create or update articles, import web pages, promote project notes and refresh benchmarks, within your permissions. When they do, the article's author line shows your name and the agent's name.
• GTM campaigns can use a wiki article as context. Pick Org Wiki Article as a source in GTM.

Keep summaries clear and specific. Agents often read only the summary to decide whether an article is relevant.

Fields referenceCopy Anchor Link

New Wiki ArticleCopy Anchor Link

Ingest URLCopy Anchor Link

PermissionsCopy Anchor Link

Access is set by an admin in Settings → Roles. The wiki's row is Org Wiki in the Brain section, with Read, Write and Delete.

People with Org Wiki Write but without Organization Details Write see the editing buttons, but Cooper rejects their changes with "Insufficient permissions to modify org wiki content". Give editors both permissions.

Without Write, the New article button is hidden, and Ingest URL, Wiki settings, Reindex categories and Refresh benchmarks are greyed out. Readers see only published articles. The workspace owner can do everything.

For AI agents and connected AI apps, the agent acts with the permissions of the person it works for. Reading and searching need Org Wiki Read. Writing, importing, promoting, reindexing and refreshing need Org Wiki Write.

Confidential Library folders linked to an article are shown only to members of the teams allowed to see them, and to the workspace owner.

Tips and best practicesCopy Anchor Link

• Write the summary for a busy reader. One or two sentences that say what the article covers and who it is for. Agents rely on it too.
• Break long articles into ## sections with clear headings, such as "Approval limits" or "Who to call". Agents can read one section at a time.
• Link related articles with [[slug]] so readers and agents can follow the trail.
• Start new material as a draft, have someone review it, then publish.
• Keep the category list short. A small, stable set of categories is easier to browse and search.
• Use Full Extract for standards and specifications, where every number matters, and Summarize for news and blog posts.
• Check imported drafts before publishing. AI summaries can miss details; compare them with the source address shown in the success window.
• Refresh benchmarks after big data changes, such as a new price list or a round of vendor quotes, and keep your own notes in separate articles.
• Archive instead of deleting. Archived articles can be restored at any time.

TroubleshootingCopy Anchor Link

For AI agentsCopy Anchor Link

Agents work with the Org Wiki through these CooperBuild MCP tools. Read tools need the user's Org Wiki permission at Read; write tools need Write. Point users to an article with /connect/org-wiki?article=<slug>.

Rules to follow:

• Search before you write. Call wiki_search or wiki_list first so you don't create a duplicate or overwrite an article by reusing its slug.
• wiki_write replaces the whole article. Fields you leave out are reset: content becomes empty, tags are cleared, articleStatus becomes draft and isDefault becomes false. To update an article, wiki_read it first and send every field back, including articleStatus: "published" and isDefault if they were set.
• Use draft for new or unreviewed content and tell the user where to review it. Publish only when the user confirms.
• Set isDefault: true only for critical company-wide standards. Default article summaries (up to 20 published ones) are added to every agent session as "Organization Standards".
• Use ## headings in content so others can use wiki_read_section, and [[slug]] to link related articles.
• wiki_write, wiki_ingest and wiki_promote accept only the 11 standard categories: standards, hr, accounting, estimating, procurement, safety, technology, cost-data, vendor, project-management, general. Custom categories added in Wiki settings can't be set through these tools.
• Treat wiki_ingest skips as information, not errors. When it returns skipped: true, tell the user the existing article (existingArticle) and offer the suggestions.
• Don't add notes to computed articles (cost-benchmarks/price-benchmarks, vendors/performance-summary, projects/portfolio-summary). wiki_compute overwrites them.

Common errors:

RelatedCopy Anchor Link

• Brain overview — all of Cooper's AI features in one place.
• Agents — the AI agents that read and write the wiki.
• Skills — teach agents how to do a task; use the wiki for what your company knows.
• Knowledge Graph — the company-wide graph Cooper builds from your data.
• AI Team — your team of agents and what they can do.
• GTM — use a wiki article as context for outreach campaigns.
• Teams — the teams that control who sees confidential folders linked to articles.
• Use the docs with AI — connect Claude or ChatGPT to Cooper so they can use the wiki.