# Console: who read what, with a receipt | Niadra

> Where your team governs the memory: a log of every read, a simulation of what each agent sees, vendor cutoff, sample review, continuous export and erasure with a receipt.

URL: https://niadra.com/en/produtos/console

Console

# Someone will ask who read what. The Console answers on the spot.

The Console is where your team governs the memory. Every read is logged: which agent read, internal or from which vendor, for what purpose and at what time. You cut a vendor’s access without depending on that vendor, simulate what each agent sees before you grant access and erase a customer’s data in one go, with a receipt. The Console is not a support screen: whoever serves customers stays in the tool your company already uses.

[Talk to us](/en/enterprise)[Read the docs(opens docs.niadra.com)](https://docs.niadra.com/en/concepts/receipts)[Open the Console](/console)

## How it works

### Read log

example

TimeWho readPurposeResult

2:07 pmVoice agent · vendor Bsupportgot the voice context

2:06 pmBilling agent · internalbillinggot the customer’s bills and disputes

2:05 pmIn-app agent · your teamsupportgot the full context

2:02 pmWhatsApp agent · vendor Asupportgot the chat context

9:31 amBilling agent · internalbillingdenied: billing does not see technical open items

### Governance

-   Who read what, in a log chained by SHA-256
-   A simulation of what each agent sees, before access is granted
-   A vendor’s access cut off on the spot
-   A customer’s data erased, with a receipt
-   The read log in your SIEM
-   Mandatory MFA for everyone, with SSO through SAML 2.0 or OIDC

### Sample review

-   From 1% to 10% of conversations go to your team to check
-   Each extracted item gets a verdict: right, wrong or missing
-   The verdicts become tests for your environment and calibrate the measurement

### Continuous export

-   The memory flows every hour, or every day, into your company’s bucket
-   In Parquet, with a manifest and a SHA-256 checksum per file
-   Erased a customer? You get the list of what to erase in your copy

### Configuration assistant

-   Proposes the mapping for an event, the extraction schema and each agent’s policy
-   Works on masked samples, and a person approves every change
-   Writes no agent prompt and changes nothing without approval

## One memory, nine products

Connect

What goes into the memory

-   [SystemsThe events your systems already emit, tied to the right customer.](/en/produtos/sistemas)

SDK, API and MCP

Any agent connects to the memory with three calls, in Python, TypeScript, HTTP or MCP.

[See the documentation(opens docs.niadra.com)](https://docs.niadra.com/en)

Remember

What the memory knows

-   [MemoryWhat was said and done, with a date, a source and evidence.](/en/produtos/memoria)
-   [IdentityPeople, companies and partners, recognized on any channel.](/en/produtos/identidade)
-   [PatternsWhat repeats, with the proof behind each signal.](/en/produtos/padroes)

Deliver

What each agent receives

-   [ContextWhat each agent needs to know before it starts.](/en/produtos/contexto)
-   [HistoryEverything that ever happened, for the agent to search.](/en/produtos/historico)
-   [AlertsA signed webhook when one of your rules fires.](/en/produtos/avisos)

Govern

What your team controls

-   [MeasurementWhether each agent used the context it received.](/en/produtos/medicao)
-   ConsoleYou are hereWho read what, review, export and erasure.