Skip to main content

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.

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

Memory Parameters

Inspect, add, edit and delete the named values Pria remembers for users in your instance.

Act As

Temporarily impersonate a user from your instance 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:
ScopeWhat it meansWho can read it
PersonalThe user’s private vault. No instance attached.Only the user
Per-instance privateTied to an instance, but not shared.The user, in that instance
Shared instance memoryTied 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

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.
The panel is the same in both places, with filters for namespace, scope, and free-text search.

​
Adding, editing, and deleting rows

1

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

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

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.
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 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.
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 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).
If your role does not have impersonation permission on an instance 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, locate the user, and open Act As.
2

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

Confirm

Pria reloads as the target user. A pill labelled Acting as <email> appears in the top bar throughout the session.
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.
  • Praxis AI staff accounts cannot be impersonated. For escalations involving a Praxis AI staff account, contact humans@praxis-ai.com.
  • Users — managing accounts in your instance
  • 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