Ga naar de inhoud

Deze pagina is nog niet in uw taal. U leest de Engelse tekst.

Team and devices

A password on a single profile

The Password… item in the profile menu protects the profiles that matter: ARMANOS asks for the password before launch, editing, export and deletion. It works in the app, in the dashboard and in scenarios.
3 attempts
and the profile is locked for an hour for the one who erred
a fingerprint
not the password itself, on the server

What you get

  • Asked before the action

    Launch, edit, export, delete, copy and granting access.

  • Works everywhere

    In the app, in the dashboard and in scenarios, on every team machine and on both engines.

  • Protection from guessing

    Three wrong entries in a row lock the profile for an hour, only for the one who typed them.

  • Reset by the owner

    The owner and admins of your workspace can reset it, and the reset is logged.

  • Scripts and the AI assistant

    The local API takes the password in the request body, not in the address.

  • A badge by the name

    A protected profile carries a badge in the app and in the dashboard.

The password window: a password and a repeat. The window flags a short password with a warning.

How it works

  1. 1

    Open the profile menu

    The three dots by a profile, the Profile password item.

  2. 2

    Enter the password twice

    The confirmation guards against a typo.

  3. 3

    Click Set password

    The profile is protected: access to it in the app opens only with the password.

What the password covers

The password is asked before this profile is opened, edited, exported, sent to the sync folder, deleted, copied or shared, and before its saved sign-in or 2FA key is shown. A copy keeps the same password. It holds in the app, in the dashboard and in scripts, on every machine of your team.

Questions and answers

Does a teammate need the password?
Yes, to open, edit or share a profile that has one: on their own machine, in the dashboard and in scenarios.
Who can set a password?
Whoever created the profile, an administrator or the workspace owner.
What about a copy of the profile?
The copy gets the same password on the server in the same step that creates it, so there is no open twin.

Protect your key profiles with a password