Org memory is the short list of facts every agent in your org can share: your opening hours, how you talk about a product, what a returning customer should hear. You write a fact once and each agent picks it up on its next turn. It is not a recording of your conversations. An agent does not remember everything a visitor said; it knows the facts on this page that it is allowed to read.
Your agents are voice-first and hands-free. They speak first, in NetShow's own voice, and a visitor's microphone opens only after the visitor taps. Typed chat sits in the small menu for people with no microphone or speaker. Whichever way the visitor answers, the facts come from here.
For the overview of every Harness door, read One face, many brains. This guide walks one page in full.
Open the page
Go to Org memory while signed in. The page heading reads Org memory. At the top right you may see a small Generation badge. Every change ticks it, and your agents compare it to know when to read the list again. That is how a fact you remove disappears from them.
If the page says the memory store could not be reached, nothing is lost. Your agents keep what they know. Try again in a moment.
Read one memory row
The Knowledge section lists every fact. The buttons above it filter by status: all, proposed, active, superseded, revoked and rejected, each with a count. Each row has four parts:
- Key: the short name of the fact, such as opening_hours, with a coloured tag for its kind (business facts, voice, product or operational). A small version number such as v1 sits under the key. A pin tag means the fact stays in the agent's context even when space is tight.
- Fact: the words your agents will use.
- Status: active facts are in use. Proposed facts are waiting for you. Superseded, revoked and rejected facts are kept for the record and never used.
- Trail: where the fact came from. It says "by You (owner)" when you taught it, or names the agent and its role, such as "by Agent 96241 (EMPLOYEE)", when an agent wrote it. A second line shows who approved it, and a third who revoked it.
If a fact carries a yellow flagged badge, its text looked like it was trying to give your agents instructions. Read it closely before you approve it.
Approve what your agents propose
Agents seated as an admin or a manager can add facts that go live straight away. Other agents can only propose. Their proposals wait under Waiting for you, and nothing there is in use yet. Press Approve and your agents pick it up on their next turn. Press Reject and it is kept in the record but never used.
While the page is open, it checks for news. If an agent writes something, a note says so and offers Refresh. It never reloads under you while you type.
See what one agent will be told
The What an agent receives section lists your agents by name. Click one to open Memory received by that agent. The page composes the same block that agent receives on its next turn, fresh each time. It holds only active facts, and only those your agent's seat or a grant lets it read, so two agents can see different lists. If there is nothing to show, the page says no memory block is available and gives the likely reasons. Use Back to org memory to return, and open it again after you revoke something to confirm the fact is gone.
Teach or correct a fact
Press Teach a fact. Choose a Class, type a Key and write the Fact the way you would want an agent to say it back. Tick Pin it for a fact that must never drop out. Press Teach it. It goes live at once, written as you.
There is no edit button. To correct a fact, teach it again with the same class and the same key. Your new words replace the old ones, the version number goes up, and the old version stays in the record as superseded.
Revoke a fact
Each active row has a Revoke button. Press it and every agent drops the fact at its next turn. A conversation already under way finishes on what it started with. The row stays on the page as revoked, with who revoked it. A revoke cannot be undone: no button brings that row back. If you revoked by mistake, teach the fact again under the same class and key.
Decide who can read what
Under Who can read it, each agent already reads the kinds of fact its role allows. Issue a grant adds kinds for one agent, with an optional end date. A live grant has its own Revoke button, and that agent loses those kinds at its next turn.