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

# Organization Memories

> Admin-curated knowledge shared with Dexter across every factory in your organization.

## Overview

Organization memories are a shared layer of knowledge that [Dexter](/product/ai-assistant) draws on across every [Factory](/getting-started/key-concepts) in your organization. They're authored as Markdown files, curated centrally by your organization's administrators, and read by Dexter in every conversation, alongside the per-factory [knowledge base](/product/dexter/memories).

Use them for anything that's true across the whole organization and shouldn't be re-taught in every factory:

* Corporate standards, naming conventions, and reporting formats
* Shared vocabulary and acronyms
* Cross-site conversion factors, costing conventions, and calendar rules
* How the organization wants Dexter to behave by default (tone, escalation, sign-off norms)
* References to systems and data sources used across sites (ERP, MES, PLM)

## How They Differ from Factory Memories

|                                       | Factory knowledge base                                                                                          | Organization memories                        |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| **Scope**                             | One factory                                                                                                     | Every factory in the organization            |
| **Who edits**                         | You — via Dexter or directly in the [Knowledge Base tab](/product/dexter/memories#viewing-and-editing-memories) | Organization administrators only             |
| **Where it lives**                    | Inside the active factory                                                                                       | Above the factory, shared across all of them |
| **Visible in the Knowledge Base tab** | Yes                                                                                                             | No                                           |
| **Read by Dexter each conversation**  | Yes                                                                                                             | Yes                                          |

Because organization memories are shared and centrally governed, they are **read-only** from the factory side: you can't edit them from a Dexter conversation, and they don't appear in the per-factory Knowledge Base views. If something in there is wrong or missing, ask your organization's administrator to update it.

<Note>
  Only organization administrators can add, edit, or remove organization memories — the curation surface sits at the organization level, outside any single factory.
</Note>

## How Dexter Uses Them

Dexter treats organization memories as background context, similar to the way the factory knowledge base's index and rules stay in view: it reads them at the start of a conversation and refers back to them when the task calls for it.

When an organization memory and a factory-level rule or fact appear to conflict, Dexter surfaces the conflict rather than silently picking a side, and asks you which one governs the work in front of you. Resolutions that need to stick land in one of two places:

* **Factory-specific exception** — Dexter records it in the factory [knowledge base](/product/dexter/memories).
* **The organization-level entry is wrong** — send the correction to your administrator.

<Tip>
  Repetition is the signal for promotion: if you find yourself teaching the same correction, convention, or acronym in more than one factory's knowledge base, ask your administrator to move it into organization memories once, for everyone.
</Tip>

## Limits and Caveats

* **Not browsable from a factory.** Organization memories don't show up in the Knowledge Base tab. To find out what's in there, ask your administrator — or ask Dexter what it's operating on for a given topic.
* **Read-only in conversation.** Dexter will not modify organization memories, even if you ask. Requests to change them get pointed at your administrator.
* **Tenant-wide by definition.** Don't put factory-specific detail in them — it bleeds into factories where it doesn't belong. Keep those entries in the factory knowledge base.
* **Changes apply on the next conversation.** Dexter reads organization memories at conversation start, so an admin edit shows up the next time you open a chat, not mid-session.

## When to Request an Organization-Memory Change

Ask your administrator to update organization memories when:

* The same correction keeps landing in more than one factory's knowledge base
* A standard, unit, or naming convention has changed organization-wide
* A shared system (ERP, MES, PLM) has been renamed, replaced, or restructured
* The organization wants Dexter to behave differently by default across all factories

For anything narrower than that, keep it in the factory [knowledge base](/product/dexter/memories).