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

# Memory Parameters & Act As

> Configure what Pria remembers for users in your instance, and impersonate a user temporarily for support.

This page covers two related admin capabilities that touch user state:

<CardGroup cols={2}>
  <Card title="Memory Parameters" icon="brain">
    Inspect, add, edit and delete the named values Pria remembers for users in your instance.
  </Card>

  <Card title="Act As" icon="user-secret">
    Temporarily impersonate a user from your instance to reproduce a support issue.
  </Card>
</CardGroup>

## Memory Parameters

Memory parameters are named pieces of context Pria carries between conversations — preferences, project notes, recent decisions, "things to remember" the user (or Pria) decided are worth keeping. Each row has a **name**, a **value**, an optional **description**, an optional **namespace**, and a **scope**.

### Scopes — personal vs shared

There are three logical scopes:

| Scope                      | What it means                                   | Who can read it              |
| -------------------------- | ----------------------------------------------- | ---------------------------- |
| **Personal**               | The user's private vault. No instance attached. | Only the user                |
| **Per-instance private**   | Tied to an instance, but not shared.            | The user, in that instance   |
| **Shared instance memory** | Tied to an instance and marked **shared**.      | Every member of the instance |

Shared rows let your team agree on common context — a glossary, brand voice notes, the names of key clients — without each user having to re-enter it.

### Where to find it

<Tabs>
  <Tab title="One user at a time">
    **Admin → Users → edit a user → Memory tab.** You see every memory row visible to you for that user: their personal vault, their per-instance entries, and the shared rows of the instances you manage.
  </Tab>

  <Tab title="One instance at a time">
    **Admin → Digital Twin → edit an instance → Instance Memory tab.** You see only the **shared** rows for that instance, with the author of each row called out.
  </Tab>
</Tabs>

The panel is the same in both places, with filters for namespace, scope, and free-text search.

### Adding, editing, and deleting rows

<Steps>
  <Step title="Filter to the right scope">
    Use the search box, the namespace dropdown, and the scope dropdown to narrow the list. The instance picker (when present) lets you focus on one instance at a time.
  </Step>

  <Step title="Edit a row">
    Click the pencil icon. You can change **Value**, **Description**, and (where applicable) the **Shared** toggle. You cannot rename a parameter — to rename, delete and create a new row with the new name.
  </Step>

  <Step title="Delete one or many">
    The trash icon removes a single row. The **Delete filtered** button at the top removes every row currently matching your filters — a confirmation modal shows the exact list first.
  </Step>
</Steps>

<Warning>
  Deletes are permanent. A deleted memory row is gone — Pria will not remember it on the next conversation. There is no soft-delete.
</Warning>

### How memory shows up in conversations

When a user talks to Pria, the relevant memory rows are pulled into the conversation context automatically. Personal rows are always included for the user that owns them. Shared rows are included for every member of the instance. The footer of the Memory panel shows a live character and rough-token count so you can see how much context your memory is using.

<Tip>
  **Keep entries short and stable.** Memory works best for values that change slowly — preferences, names, facts. For fast-moving notes, use a conversation or an Assistant.
</Tip>

## Act As (impersonation)

"Act As" lets an admin sign in *as* one of their users for up to an hour to reproduce an issue, debug a flow, or confirm a fix. Everything Pria does during that session is recorded against the admin's audit trail.

### When to use it

* A user reports an error and you cannot reproduce it from your own account.
* You need to confirm an entitlements change actually applied to a specific user.
* You are walking a user through their own conversation history on a call.

### Authorization

To start an Act As session you must be an admin and hold the `users.edit` entitlement on at least one instance the target user belongs to. You cannot:

* Impersonate yourself.
* Start a new Act As session while another one is already active (no nested impersonation).
* Impersonate without supplying a written **reason** (required, max 500 characters).

<Note>
  If your role does not have impersonation permission on an instance you support, contact the Praxis AI team at [humans@praxis-ai.com](mailto:humans@praxis-ai.com) to request access.
</Note>

### Starting and stopping a session

<Steps>
  <Step title="Find the user">
    Go to **Admin → Users**, locate the user, and open **Act As**.
  </Step>

  <Step title="Provide a reason">
    Enter a short reason (for example, "Reproducing thumbnail upload error reported in ticket #4821"). The reason is stored in the audit log.
  </Step>

  <Step title="Confirm">
    Pria reloads as the target user. A pill labelled **Acting as \<email>** appears in the top bar throughout the session.
  </Step>

  <Step title="Stop">
    Click **Stop** on the pill at any time to return to your admin identity. The session also ends automatically after one hour or when your own session would have expired — whichever comes first.
  </Step>
</Steps>

<Warning>
  While impersonating, admin endpoints are blocked. You see what the user sees and can act on their data, but you cannot use admin pages until you stop the session.
</Warning>

### Audit trail

Every impersonation session is logged with: the **admin's** identity, the **target user's** identity, the **reason** you typed, the **start time**, the **end time** (or expiry), the **session id**, and the **IP / user agent** the session was started from. The log is append-only — sessions cannot be edited or deleted.

If an admin closes their browser without clicking **Stop**, the session still expires on the server when its time-to-live is reached; the audit row records the expiry rather than an explicit stop.

### Privacy and limits

* Impersonation does not unlock data the target could not access. If the user does not have access to a conversation or a file, neither do you while impersonating them.
* Sensitive credentials are not surfaced. You see what the user sees in the UI; you do not see their password or stored secrets.
* A session has a **1-hour hard cap** and cannot be extended; start a new session if you need more time.
* Praxis AI staff accounts cannot be impersonated. For escalations involving a Praxis AI staff account, contact [humans@praxis-ai.com](mailto:humans@praxis-ai.com).

## Related

* [Users](/mdx/admin-guide/users) — managing accounts in your instance
* [Entitlements](/mdx/admin-guide/entitlements) — `users.edit` and other role permissions
* [User Memory](/mdx/user-guide/memory/user-memory) — the same memory panel from the user's perspective
* [Shared Memory](/mdx/user-guide/memory/shared-memory) — how shared rows show up to users