Skip to main content
This page covers two related admin capabilities that touch user state:

Memory Parameters

Inspect, edit, share and delete the named values Pria remembers for the people in your Digital Twin.

Act As

Temporarily see Pria as one of your people to reproduce a support issue.

​
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: 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.
Memory parameters are the hand-managed store. A Digital Twin can also build Long-term Memory on its own — memories it decides to keep from conversations, each shown to the user with a receipt. It is additional to memory parameters, private to each user (you see counts only, never content), and configured per twin under Instance Settings → Knowledge → Long-term Memory: who gets it (everyone, or administrators only), the default mode for new conversations, and whether recalled memories are listed under answers (Display Memory Details). Turning the feature on for a twin (and sharing memories across an Account) is done by the Praxis AI team — contact humans@praxis-ai.com to request it; the other controls are available to the twin’s own administrators in that panel. See Twin Memory.

​
Where to find it

Admin → Users → edit a user → Memory tab. Rows are grouped by Digital Twin, with personal entries in their own group. You see the entries on the Digital Twins where you hold users.edit. Their personal entries appear only once the person has joined your Digital Twin themselves (an active membership of their own — an address you imported counts once they have used your Digital Twin).
The panel is the same in both places: a search box, a namespace filter, a scope filter (All scopes, Private (non-shared), Shared only), a Digital Twin filter when there are several, and Group by namespace. Export CSV downloads the rows you are looking at.

​
Adding, editing, and deleting rows

1

Filter to the right scope

Use the search box and the filters to narrow the list.
2

Edit a row

Click the pencil icon. You can change Value and Description, and for an entry that belongs to a Digital Twin, tick or clear Shared with this instance — only administrators can share an entry with every member. You cannot rename an entry: its name and namespace identify it, so delete it and have it saved again under the new name.
3

Delete one or many

The trash icon removes a single row after showing its name and value. Delete filtered (N) removes every row matching your filters — the confirmation lists each one first.
Deletes are permanent. A deleted memory row is gone — Pria will not remember it on the next conversation. There is no soft-delete.

​
How memory shows up in conversations

When a person talks to Pria, the relevant memory rows are added to the conversation automatically. Personal rows are included for the person who owns them; shared rows for every member of the Digital Twin. The panel’s footer counts the rows, characters and approximate tokens you are looking at, so you can see how much room memory takes.
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.

​
Act As (impersonation)

“Act As” lets an admin sign in as one of their people for up to an hour to reproduce an issue, debug a flow, or confirm a fix. Each session is logged with the admin’s identity, the person’s identity and the reason given.

​
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 hold users.edit on a Digital Twin where the person has an active membership of their own (an address you imported counts once they have used your Digital Twin). 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).
If you do not hold users.edit on a Digital Twin you support, contact the Praxis AI team at humans@praxis-ai.com to request access.

​
Starting and stopping a session

1

Find the user

Go to Admin → Users, open the person’s record and select Act As… in its footer.
2

Provide a reason

Enter a short reason (for example, “Reproducing thumbnail upload error reported in ticket #4821”), then select Confirm — Act as user. The reason is stored in the audit log.
3

Confirm

Pria reloads as the person. A pill labelled Acting as <email> stays in the top bar throughout the session, and everything you do is recorded as theirs.
4

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.
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.

​
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.
  • Users — managing accounts in your Digital Twin
  • Entitlements — users.edit and other role permissions
  • User Memory — the same memory panel from the user’s perspective
  • Shared Memory — how shared rows show up to users
  • Twin Memory — Long-term Memory from the user’s perspective, and how it is enabled per twin