> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization knowledge

> Define org-wide standards and conventions that Clark follows by default

Organization knowledge applies to every Clark conversation across your entire org. Use it to encode information that all builders should benefit from, so Clark builds consistently with your team's standards — things like design systems, coding conventions, domain terminology, and team-wide patterns.

## Adding org knowledge

Navigate to the **Knowledge** page and chat with Clark to describe what you want it to remember. Clark will create the right knowledge entry at the right scope for you, then present it for your review before saving. We recommend using Clark to write entries because it optimizes them for LLM retrieval — producing focused, well-structured instructions that Clark can look up effectively at build time.

<img src="https://mintcdn.com/superblocks/nJ3ep6kSq7I75bb2/images/building-with-clark/knowledge/knowledge-page.png?fit=max&auto=format&n=nJ3ep6kSq7I75bb2&q=85&s=2e98dea282f92b7d27724630de7910be" alt="Clark Knowledge page" style={{width: '100%'}} width="3798" height="1986" data-path="images/building-with-clark/knowledge/knowledge-page.png" />

For example, you might tell Clark:

* "Our design system uses primary (#0099FF), secondary (#6B7280), and danger (#EF4444). Never hardcode other colors for interactive elements."
* "All API error responses must be caught and displayed with a toast notification. Never silently swallow errors."
* "When referring to customers, use 'account' not 'client' or 'customer'. Our data model uses `account_id` as the primary identifier."

Clark will draft the entry, set the scope to **Organization**, and present it for your review before saving.

<img src="https://mintcdn.com/superblocks/nJ3ep6kSq7I75bb2/images/building-with-clark/knowledge/org-knowledge.png?fit=max&auto=format&n=nJ3ep6kSq7I75bb2&q=85&s=2eebdeda34ef0ae15c470f589c527123" alt="Clark creating an org knowledge entry" width="2744" height="1986" data-path="images/building-with-clark/knowledge/org-knowledge.png" />

You can also ask Clark to **explore your existing knowledge**, refine entries, or identify duplicates — for example, "Review my org knowledge and flag any entries that overlap or contradict each other."

## Permissions

Creating, updating, and deleting org knowledge requires Owner or Admin permissions. Once entries are saved, they are available to all builders in the org — you cannot restrict who benefits from org knowledge, because it's designed to apply everywhere.

<img src="https://mintcdn.com/superblocks/nJ3ep6kSq7I75bb2/images/building-with-clark/knowledge/org-knowledge-permissions.png?fit=max&auto=format&n=nJ3ep6kSq7I75bb2&q=85&s=8d3e8cd183f560f438367d0833b47574" alt="Organization knowledge permissions" style={{width: '80%'}} width="1024" height="663" data-path="images/building-with-clark/knowledge/org-knowledge-permissions.png" />

Individual entries can be enabled or disabled from the Knowledge page.

<Note>
  Enabling too many knowledge entries at once can reduce Clark's effectiveness. Keep entries focused and disable any that aren't actively needed.
</Note>

## Related

Organization knowledge is part of Clark's broader [Knowledge](/building-with-clark/knowledge) system. You can also define knowledge at the [integration](/integrations/knowledge), [user](/building-with-clark/knowledge/user-knowledge), and [app](/building-with-clark/knowledge/app-knowledge) levels.