No automatic filling
SoftGlaze copies the code; a person pastes it. It doesn’t type 2FA codes into sites by itself.
Team 2FA
Save an account’s 2FA secret on its browser profile in SoftGlaze Browser, a multi-profile (antidetect) browser for Windows teams. From then on, the secret stays sealed on your computer and no one sees it again, the Owner included. A Manager clicks the profile’s 2FA badge and gets the current 6-digit code. Operators can’t read codes at all, account and proxy passwords stay masked, and every code read is recorded in the activity log.
3 members in the trial and on SoftGlaze Browser Pro, 25 on SoftGlaze Browser Enterprise.
The 2FA phone on one desk
Someone has to read out a code every time a colleague signs in. Or the secret key gets pasted into a chat so everyone can add it to their own authenticator, and from then on nobody knows who has it.
The 2FA secret on the profile
The secret is saved once, sealed, and never shown again. The people you choose copy a live code from the profile’s row when a site asks for one. Who read a code, and for which profile, is in the activity log.
01Save the secret once
In the profile editor, paste the account’s 2FA secret, the base32 key a site shows when you set up an authenticator app. Creating profiles from a spreadsheet? A column named 2FA Key (or 2FA, TOTP, OTP secret, authenticator) fills it for each profile. SoftGlaze seals the secret with Windows encryption before it is stored.
2FA Secret: JBSWY3DPEHPK3PXP
Saved as: enc:v1:•••••••• (sealed with Windows encryption)02One click for a live code
A profile with a saved secret shows a 2FA badge in the Profiles list. Click it and the current 6-digit code is copied, ready to paste where the site asks. Codes follow the authenticator standard: 6 digits, a new one every 30 seconds.
Store-DE-01 [ 2FA ] -> Copied!
Code: 6 digits, renewed every 30 seconds03Who can read a code
Reading a live 2FA code is role-gated in the app’s main process. Owners, Admins and Managers can copy codes for the profiles they can open. An Operator is refused, sees •••••••• where secrets would be, and can still launch the profile and use the account inside it. The secret itself never reaches the app window for anyone.
| Role | Copy a live 2FA code | See the 2FA secret | See account and proxy passwords |
|---|---|---|---|
| Owner | Yes | No | Yes, except on profiles shared to them “use only” |
| Admin | Yes | No | Yes, except on profiles shared to them “use only” |
| Manager | Yes | No | Yes, except on profiles shared to them “use only” |
| Operator | No | No | No, shown as •••••••• |
04Every read is logged
Each code read is written to the workspace’s activity log with the member and the profile. Owners and Admins see it in Team activity on the Members page, next to launches, edits and sign-ins. On Enterprise, and during the trial, the log exports as CSV or JSON.
05Shared “use only”
Share a profile with someone as Use (launch) and they can open it and work in the account. A copy they make of it leaves out the 2FA key and the saved logins, and the proxy password and rotation link stay hidden from them. Exports leave the 2FA key blank for anyone who may not read codes.
| Place | The 2FA secret | A live code |
|---|---|---|
| The database file | Sealed with Windows encryption | Not stored |
| The app window | Never, for any role | Copied on a click, Manager and above |
| The activity log | Never | Each read is recorded |
| A copy of a profile shared “use only” | Left out | Not applicable |
| An AI app connected through SoftGlaze AI | Never | Never |
Save the secret
Open the profile, paste the account’s 2FA secret in 2FA Secret and save. Or import it in a 2FA Key column.
Share the profile
On Profiles, select it, click Share, pick the member and Use (launch) or Use + edit.
Copy a code when asked
A Manager or above clicks the profile’s 2FA badge and pastes the code into the site.
Limits and caveats
SoftGlaze copies the code; a person pastes it. It doesn’t type 2FA codes into sites by itself.
If an Operator must sign in again where a code is asked, a Manager or above copies the code for them, or you give that person the Manager role.
Once saved, SoftGlaze shows the secret to no one. Keep your own backup of the key, as the site advises when you set up 2FA.
Profiles, codes and members live in the workspace on the computer where SoftGlaze is installed. People on their own laptops are not sharing that workspace.
One business day, Monday to Friday for a first reply.
Yes. SoftGlaze Browser saves the account’s 2FA secret on its browser profile, sealed. Managers and above copy a live 6-digit code with one click, nobody sees the secret again, Operators see passwords as dots, and every code read is logged.
No. After you save it, the secret never reaches the app window, for any role, the Owner included. Only live codes are handed out, and only to Managers and above.
No. Reading a code needs the Manager role or higher. An Operator can still launch the profile and work in the account it is signed in to.
Yes. In a spreadsheet import, a column named 2FA Key (or 2FA, TOTP, OTP secret, authenticator) fills the secret for each profile.
No. SoftGlaze AI has no tool for 2FA codes, so no AI app can read them.
Read it in the source
The trial includes all four roles and 3 seats.
No card needed.Windows 10 and 11, 64-bit.