Table of Contents

Profile

Last updated:

Profile settings let the signed-in user update their own full name, email address, password, and profile picture.

Note

Your profile is your own account record. Admin user management is separate and cannot reset your own password from the Administration screen.

Open your user menu and select Account. Every signed-in user can edit their own profile. No admin role is required. Your username is shown for identification but is not editable here.

Account details

Edit Full name and Email address, then click Save changes.

The email address must be valid and cannot already belong to another user. A clear full name helps other users recognize you in admin screens, profile menus, and shared-agent context.

Change password

Leave all password fields blank to keep your current password.

To change it:

  1. Enter Current password.
  2. Enter New password.
  3. Repeat it in Confirm new password.
  4. Click Save changes.

The new password and confirmation must match exactly. If the current password is wrong, the save is rejected.

Tip

If you are only changing your name or email, leave every password field empty.

Account fields are processed before an optional password change. If a password error appears after you also edited your name or email, close and reopen the dialog to confirm which account details saved before retrying the password.

Vault Password

The Vault Password unlocks encryption for stored API keys, OAuth and bot tokens, other reversible secrets, encrypted workspace files, and chats and task runs saved by agents using Confidential Chat. It is separate from your Account Password and must be 12 to 256 characters.

You create the Vault Password after first sign-in, before onboarding or other authenticated pages load. In Profile, choose Change Vault Password, enter the current password, then enter and confirm its replacement. Oscova keeps the same underlying data-encryption key, so changing the password does not require rewriting existing protected data.

Important

Save the Vault Password somewhere safe. Oscova never stores it and cannot recover it.

Logging out ends only your browser session. It does not remove the unlocked key from the running Host, so credential-backed background work can continue. A Host restart clears all unlocked keys and invalidates old browser and CLI sessions. Sign in again, then enter the Vault Password once to make your confidential data and enabled bots available.

Keep these jobs separate: the Account Password signs in, the Vault Password unlocks confidential data, the Export Passphrase protects one backup, and the CLI bearer token authenticates terminal commands.

An imported environment keeps each user's wrapped encryption key. Each user must enter their own Vault Password after restore before Oscova can open that user's protected credentials, chats, or task runs.

Panic Password

A Panic Password is a second password for a coerced sign-in. When you enter it on the password sign-in screen, Oscova opens a normal-looking session after permanently destroying the private data you selected in advance.

Configure it after you have created the agents, tasks, and workspaces you may want removed. In Profile, choose Set panic password to open the replacement-policy dialog. Enter your Account Password, choose a new Panic Password of 12 to 256 characters, then choose any optional targets:

  • Delete all conversations removes every conversation and its related stored data.
  • Selected custom agents are deleted. Shared agents cannot be selected.
  • Selected tasks are deleted. Deleting an agent alone does not delete its tasks.
  • Selected workspaces are emptied. The workspace remains available, and the default workspace is never cleared.

The Panic Password deletes only the agents, tasks, workspace contents, and conversations selected in its policy. It preserves the vault, credentials, tokens, encrypted files, and other data you did not select.

Important

Selected data is permanently removed. Recovery is possible only from a backup taken before the Panic Password was used.

Oscova cannot display the saved policy or tell you whether a Panic Password is set. The form therefore starts empty every time you open it. Saving replaces the complete unseen policy instead of adding to it. There is no remove action.

If a selected agent or task was deleted after you saved the policy, it is treated as already handled. Renaming it does not change its selection. A deleted or renamed workspace is also treated as already handled. If you keep an agent or task that writes into a cleared workspace, it can create new files there later.

The Panic Password works only on the password sign-in screen. If you usually use a PIN, switch to password sign-in when you need it. It protects the sign-in moment and does not close a session that is already open.

The panic record is tied to the Account Password. If the record is missing or damaged, normal-password sign-in is refused rather than allowing the account to open without protection. An administrator can reset the account password to recover access.

Profile picture

Click Change profile picture to open the picture gallery. From there you can choose a built-in picture or upload your own PNG, JPEG, or WebP file up to 2 MB.

The gallery shows the current picture and the selected picture before you apply it. Click Use this picture to save the selected built-in picture or upload.

The profile picture saves from the gallery. Save changes applies only to account details and password fields.

Oscova validates the first bytes of the uploaded file, not just the filename, so renaming an unsupported file to .png will still be rejected.

An upload rejected for size or format leaves the current picture in place. For another error, close and reopen the gallery after the connection recovers, check the current preview, then select the picture again.

Troubleshooting

  • If the image is rejected, check the format and 2 MB size limit.
  • If the built-in gallery is empty, close and reopen it after checking the connection.
  • If the picture does not change immediately, wait for the success toast, then refresh the page.
  • If email save fails, another account may already use that address.
  • If password save fails, re-enter the current password and matching new-password fields.
  • If stored credentials remain unavailable after restart, reopen Oscova and enter the Vault Password when prompted.
  • If normal sign-in reports invalid credentials after the panic record was edited or damaged, ask an administrator to reset the account password.