Memory: what Twin remembers

Memory is what Twin keeps about your firm, your clients, you and a document type, so you do not have to repeat the same instruction in every application.

How a memory is written

Tell the assistant something worth keeping ("we always write in formal Dutch and address the reviewer as u") and it stores it. The conversation then shows a Memory updated card with a badge naming the level it applies to, the text it saved, and Undo. Click Undo and the card reads Change undone, and the memory returns to what it was.

A Memory updated card in the assistant, badged Organization, with an Undo action

The four levels

Each level has its own memory, edited in place on the page it belongs to.

Organization: how your firm writes. Organization in the user menu, then the Memory tab.
Client: what is true of one client. The client page, section Memory.
Account: your own preferences. Account in the user menu, then the Memory tab.
Document type: how one kind of application should be written, plus a separate card per section. Document types in the user menu, then the type.

A document has no memory of its own. To reach the memory that steers it, open the document, click Document actions and choose Document type memory.

A client page in Twin with the Memory section below General information

A document type page with its own memory and one memory card per section

Writing and editing a memory yourself

Open the page for the level you want. An empty card reads No memory; click Add memory.
Click a filled card, or its pencil, to edit the text.
Click Save. Cancel discards your edit.

Write it as an instruction, in whole sentences, the way you would brief a colleague. Keep it to things that stay true; anything that belongs to one application belongs in the project or in a source.

An organization memory open for editing, with Remove, Changes, Cancel and Save

Seeing what changed

Changes in the editor lists every version of that memory, newest first, with who wrote it: a person's name and Edited directly, or the assistant and the conversation it happened in. Click an entry to see it in full, with Before and After. A change that was undone is marked Undone and says when.

The list is a record, not a control: you undo a change with Undo on its card in the conversation, and you correct an older one by editing the memory.

The Changes history of a memory, showing the Before and After text of one change

Deleting a memory

Open the memory and click Remove. Twin names the memory in a Delete memory confirmation and warns that the action cannot be undone. The level keeps its empty card, so you can write a new memory whenever you want.

Who can see it

Organization, client and document type memories belong to the organization: everyone in it sees them, and everyone's applications are written with them. Treat them as shared instructions, and do not put anything in them you would not want a colleague to read. Account memory is yours alone.