Saved logins and private sign-in
When a coworker needs to be signed in to a website, you sign it in privately: what you type goes into its browser, never into the conversation, and the coworker is only told whether it worked.
3 min read
When a Bot asks to be signed inCopy link to this section
The Bot pauses and the conversation shows Waiting for you to sign in with a button, Open private sign-in. If you are not there, the request reaches you as a link wherever you get your notifications. It stays open for 15 minutes. You answer it in one of four ways:
- Enter your login: type the username, password and, if the site asks, the verification code. They are typed straight into the Bot's browser.
- Use a saved login: choose one of yours and press Confirm and sign in.
- Take over to sign in: take the Bot's browser, sign in by hand, hand it back and press I've signed in.
- Decline: the Bot is told you said no.
Whichever you choose, the Bot learns only whether the sign-in worked and how it was done, never the username, password or code. A wrong password brings the form back so you can try again.
How saved logins are keptCopy link to this section
Tick Save to Passwords when you type a login, and once the sign-in works it is kept under Settings → Passwords, in Saved logins. A saved login is yours, not a Bot's: any of your Bots can be signed in with it, but only when you choose it.
- Passwords are stored encrypted. The page shows the site, the username and when it was last used; a password can be deleted but never displayed, to you or to an administrator.
- A login is offered and filled only on exactly the site it was saved for: a subdomain, a look-alike address or a page without a secure connection does not count.
- Set expiry records an expiry or rotation date; you are reminded in Notifications 14 and 3 days before it, and when it passes.
- Add two-factor keeps the site's authenticator secret with the login. When you choose that login for a sign-in, the code is worked out and filled for you.
Note
No Bot can use a saved login on its own, and no standing approval covers one: choosing it in the sign-in form is the confirmation, every time.
Typing a secret during a hand-offCopy link to this section
While you hold the Bot's live screen (Take control, then Hand back when you are done), what you type is not recorded. When you select a password or code field, a masked box appears: what you type there goes only to that field on the page, is not shown in the conversation and never reaches the Bot. A Bot can also ask for such a value with The assistant needs and the name of what it needs.
If you start to send something that looks like a password or a one-time code in the chat, the message is held with a warning. Use the secure box moves it to a private sign-in instead; Remove it and send the rest sends the message without it.
What is recordedCopy link to this section
The audit trail records each sign-in request and how it ended, each login saved or deleted, and each time a two-factor code was filled, with the site and the method. It never holds a username, password or code. When a person is deleted from the workspace, their saved logins are deleted with them.
On a Bot's Sites tab, the Sign-in board shows which sites it is signed in to; Sign in privately starts a sign-in and Forget removes a site. On the live screen, Clear one site… signs the Bot out of one site, and Fresh session… starts a browser with no sign-ins at all for one task.
Tip
Administrators can switch saved logins off for the workspace under Enterprise controls. Private sign-in still works then, for logins typed each time.
Last updated