# Saved logins and sign-in help > For websites without an API, save a login on a secure page, approve each use from your texts, and finish two-step sign-ins on a live view of the assistant's browser. Coming soon. Source: https://asktack.com/docs/saved-logins/ Some tools have no way for apps to connect. For those, the assistant will use the website the way you would, in its own browser. This page explains how it signs in there without ever seeing your password, and what you do when a site asks for a code. **Coming soon.** Saved logins and sign-in help are built and in testing, but not turned on for accounts yet. This page describes how they work. ## Saving a login When the assistant needs a site you haven't saved a login for, it texts you a secure link instead of asking for your password. Your password never goes in the text thread. You can also save one ahead of time: on the **Saved logins** tab of your [account dashboard](https://asktack.com/docs/account-dashboard/), under **Save a login**, enter the **Website address** (like buildertrend.net), choose **Who can use it** (owners and admins only) and tap **Continue** to open the secure page. 1. Tap the link. The page says which site it's for, like **Save your buildertrend.net login**. 2. Enter your **username or email** and **password**. You can add a **name** too, like "Office account". 3. Tap **Save login**. You see **Saved**, and the assistant picks up where it left off. The link works **once** and expires after **15 minutes**. A link preview in Messages doesn't use it up. If it expired, ask the assistant for a new one. Saving again for the same site replaces the old login. ### Your login or the company's - **Personal** (the default): only you can use it. - **Company:** everyone on your team can use it. Only the owner or an admin can save a company login. When both exist for a site, the assistant uses your personal login first. ## Approving each use The assistant asks every time it wants to sign in with a saved login. You get a text with a link, and the page asks: > **Log into buildertrend.net?** Your assistant wants to sign in to buildertrend.net with your saved login. It types the login into its browser; it never sees it. Tap **Approve** or **Deny**. - One approval covers **one sign-in**. Next time, it asks again. - A request **expires after 30 minutes**. If you miss it, the assistant can ask again when you're ready. - Only you can approve a sign-in with your personal login. For a company login, the teammate who asked approves it. ## Finishing a sign-in step yourself When a site asks for a code from your phone, a CAPTCHA or a security question, the assistant pauses and texts you, for example: > Buildertrend is asking for a 2FA code. Tap to finish it: … 1. Tap the link. You see the assistant's browser, live, on the page that's waiting. 2. Finish the step there: type the code, solve the puzzle or answer the question. If your keyboard doesn't open, tap **Open full screen**. 3. Tap **Done**. The assistant continues the task. Tap **Cancel** instead to stop the task. The link expires after **30 minutes**. The assistant's browser keeps that sign-in for next time, like your own browser would, so you won't be asked every time. Each person has their own browser profile; your sign-ins aren't shared with your team. ## How your login is protected - **Encrypted** as soon as you save it, with the same encryption we use for tool connections. - **The AI never sees it.** The assistant only learns whether the username and password boxes were filled. - **Only typed into the right site.** The login is filled only on a secure (https) page of the site it was saved for. If the page has sent the browser anywhere else, it isn't filled. - **The browser stays on task.** For each task, the assistant's browser can only visit the site you asked about. Pages that try to send it elsewhere are blocked. - **Changes ask first.** Anything the assistant would change on a website (submitting a form, saving, sending) waits for your OK, even when the same change wouldn't need one through an app connection. - **Everything is logged.** Saving, approving, denying and each sign-in are recorded in your account's audit log, without the password. ## Deleting a saved login ## Seeing and deleting saved logins The **Saved logins** tab of your [account dashboard](https://asktack.com/docs/account-dashboard/) lists each login by website, whether it's **Personal** or **Company**, and when it was last used. Passwords are never shown. Members see their own logins plus the company's; the owner and admins see every login on the team. To delete one, tap **Delete** next to it. Members can delete their own; the owner and admins can delete any. Deleting a login also cancels any approval request still waiting for it, and the assistant can't sign in to that site until a login is saved again.