Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Manage existing accounts
Accounts, access and security

Manage existing accounts

Users lists every account; open one to change its details, its role, its access or the account itself.

Open an account

  1. Open Users.
  2. Select the account in the directory.

The panel opens on the right and starts on Permissions. Tabs under the name switch between Permissions, Projects and Account, plus one tab for every plugin that adds an account panel. On a phone the panel fills the screen.

Change the display name or username

Open the Account tab and edit Display name or Username. Both save shortly after you stop typing.

The same tab shows the account's preset, role and usage figures, and the two-step-verification status.

Change a role

Use the menu next to the account name and choose Make admin or Remove admin. A confirmation names the access the change gives or removes.

Note: The last administrator cannot be demoted, and the last account on the installation cannot be deleted.

Sign in as an account

The same menu holds Sign in as, which shows the app as that account so you can check what the person sees. Back to your account returns to your own session.

Warning: An impersonated session cannot reset another account's two-step verification.

Delete an account

  1. Open the account's action menu and choose Delete.
  2. Confirm the named account.

Chetty stops the account's running processes and removes its sessions, brain data, account settings, private memories and memory categories, push subscriptions, API tokens, project assignments, external identity links and plugin-owned account data. Memories in a shared project pool are kept and re-attributed.

Administrators cannot be deleted, so demote one first. An account with paired computers cannot be deleted until their owner confirms removal of each computer's Project; see Delete a Project. After removal finishes, return to Users and delete the account.

Chatbot accounts

A chatbot account is non-interactive. It has no password and no self-service sign-in, but a signed-in administrator can enter it with Sign in as.

It can never become an administrator, cannot be linked to an external identity, and cannot hold personal API tokens. It is bound to one project, and that project's instruction files are its persona; read Give a Project its own instructions.

A chatbot account is granted the chatbot plugin when it is created.