هذه الصفحة غير متوفرة بلغتك بعد. أنت تقرأ النص الإنجليزي.
Accounts
Two-factor codes next to the profile: what that changes
فريق ARMANOS8 minUpdated

In short
A key and a code are different things. A code is six digits for thirty seconds, and the key produces them by the clock.
The key sits next to the profile. Digits appear in the profile window, and the phone drops out of the work.
The key stays with you. The server stores no key, and it reaches an assistant by your choice.
Why your assistant waits every time
A platform asks for six digits at a login from an unfamiliar device, and an ad account often asks at every login at all.
The digits live thirty seconds and appear wherever the app holding the key is installed, which is in your pocket.
The hands are your assistant's, and the permission to work comes from you, by hand. On three accounts that is nothing, on thirty it is your whole working day.
- 1
The password went through
The platform asks for the second step and waits for six digits.
- 2
The digits live half a minute
The window is short, and they have to go across at once.
- 3
The app sits with you
The key is on your phone, and your assistant does the work.
A key and a code differ
A code is six digits for thirty seconds. A key is the short string you took off a QR picture once, back when you turned the protection on at the platform.
A code comes out of the key and the current time, and there is no road back: a dozen codes read over your shoulder will not give up the key.
So a code you hand over costs you a minute, and a key you hand over costs the account until you bind the second step again.
A phone app does the same thing: it holds the key and shows digits by the clock. The difference is where the key lies and who can reach it.
| What you hand over | What it costs |
|---|---|
| One code | One minute of work and one message |
| The whole key | Entry to the account until the second step is bound again |
| Password and key together | An account that works without you |
Three ways and the price of each
There are three ways in all, and you have probably walked two of them already. Forward every code by hand, give your assistant the key itself in a chat, or put the key where the profile opens.
The first runs into your time, the second into a chat you cannot recall.
The third leaves the key on a machine rather than in somebody else's chat, and that alone is what separates it from the second.
| The way | What you pay with |
|---|---|
| Forward every code | Your attention across the whole working day |
| Give the key in a chat | A copy of the key nobody can recall |
| Put the key by the profile | Access for whoever opens that profile |
What changes with the key there
The key already sits next to the account anyway: in a spreadsheet, in a note, in a shared password vault.
Next to the profile it moves one step closer to the window where that account is actually used.
Then the digits appear in the same window, and the phone drops out of the work. The app computes the code on this computer, and nothing goes out to the network for it.
The window does not show the key back: the One-time code window in the profile menu shows the digits, the seconds left and the account name, and the card carries only a 2FA mark.
You paste it once, and after that you work with digits alone.
- 1
No second device
The digits appear in the same window the profile lives in.
- 2
Nothing to look up
The key belongs to the profile, so there is nothing to match by name.
- 3
Nothing to retype
You copy the code with a button, and a flow types it into the form.
- 4
No network needed
The key and the clock sit on this computer, and the code needs no network.
What ARMANOS does with codes
The "One-time code" window in the profile menu shows the digits, the seconds left and the account name.
You paste the key once: a whole otpauth:// string or a bare key.
A key column in the import table brings keys in together with the profiles.
Who you open the account to
A key on a profile means one thing: whoever opens the profile signs in to the account without you. Say that decision aloud before you hand over the first profile.
Keys are stored on your computer, in the folder of your account.
A key, like a password, cannot be revoked in one step: you have to link the second step again on the platform. So hand over the key for the whole length of work with the person.
What never leaves your machine
The key does not go to the server. Signing in on another machine, you see the profile but find no key beside it, and sync back does not erase it.
The server does not accept cookies or the sign-in pair either. ARMANOS keeps a profile's key, cookies and sign-in on the machine where you created them and never sends them anywhere itself.
You choose the shared folder for sessions yourself, and then cookies and sign-ins travel into it.
- 1
The key stays with you
The server stores no key: it lives on your computer.
- 2
A login on a second machine
The profile arrives, and the key stays on the first one.
- 3
A transfer under a password
Only a profile archive carries the key, and your password opens it.
How the key reaches your assistant
Shared access to a profile does not bring the key along: your assistant opens the profile from their own machine and finds no digits there.
The key travels by two roads: a profile transfer with its session, whose file opens with a password you set, and a profile export with the Export button if you pressed «Include secrets» yourself.
That second file has no password.
A profile copy does not take the key: a copy is a new account. A transfer file does not open with a wrong password, and a clear refusal comes instead of the content.
The session travels into the archive along with the profile: cookies, logins and the state of the sites. Your assistant sits down in a warmed profile instead of signing into thirty accounts again from scratch.
Why a right key gives wrong codes
Most of the time the trouble is not the key but its settings.
A bare key carries only the secret itself, while a whole otpauth:// string also carries the number of digits, the step and the algorithm, and an unusual platform sets those its own way.
The same key with eight digits, a sixty second step and SHA256 gives one code with those settings and a different one without them.
An account looks lost after that, although what got lost was three fields.
The app turns down a string that counts logins rather than seconds the moment you paste it: time based digits will never come out of it.
Spaces, dashes, lower case and equals signs in a key are no obstacle at all.
| What you pasted | What you get |
|---|---|
| A whole otpauth:// string | The digits, step and algorithm of the platform that issued it |
| A bare key | Six digits, a thirty second step, SHA1 |
| A string that counts logins | The key does not land, so no wrong digits |
| A string with a typo | A refusal on saving, and nothing written to disk |
Will the digits match another app
Your assistant types the digits into the same platform that expects them from a phone, and a disagreement has nowhere to come from: the step and the method are set by RFC 6238, one for everybody.
Six reference samples of that standard, the farthest of them at a time of 20000000000 seconds, give exactly what the app on your phone gives.
The clock is a separate trouble: the digits follow this computer's clock, and a clock that has drifted gives what the platform does not expect.
A few wrong tries in a row read as guessing, and the platform closes the entry itself after that.
You can leave the app on your phone switched on: two places holding one key do not get in each other's way and give the same digits.
That is also how you check yourself on the first day.
Your own login is another door
The second step on a platform account and the second step on your own account are two different doors. The first you hand to your assistant along with the profile, the second you hand to nobody.
On your own login the same number does not work twice, ten misses shut the door for a while, and turning it on gives you ten recovery codes, each good once.
Lose the phone and a recovery code lets you in, while your assistant gets in with neither.
Which order to choose for yourself
With one assistant and three accounts, leaving it as it is comes out cheaper: your time on ten codes a day costs less than untangling things when you part.
With thirty accounts, forwarding codes is the very work you hired a person for.
If you hand the account over for good, the key travels with the profile, and after you part the second step has to be bound again. If the account stays yours, hand over access to the profile and not the key.
There is a middle arrangement too: you hand over access to the profile and keep the key.
Your assistant works in the profile, still writes to you at the second step, and every login stays your choice.
| Your case | What to do |
|---|---|
| Three accounts and one assistant | Keep the codes yourself and forward them |
| Thirty accounts and shifts | Put the key by the profile on your assistant's machine |
| Handing the account over for good | Transfer the profile under a password and change the account password |
| The account stays yours | Give profile access without the key and keep the digits |
Common questions
- Will my assistant see the key or only the digits?
- The One-time code window gives back the digits, the seconds left and the account name, and it does not show the key again. But the machine holding the profile holds the key too, so count it as handed over together with the machine.
- I shared the profile through the team. Did the key travel?
- No. There is no such field on the server, and a shared profile does not carry the key: from their own machine your assistant sees the profile and no digits.
- How do I take the access back?
- Changing the password is not enough: the key keeps working afterwards. Take back access to the profile and bind the second step at the platform again, and the old key stops giving right digits.
- What if the account uses eight digits or a one minute step?
- Paste the whole otpauth:// string: it carries those settings itself. A bare key does not carry them, so the app falls back to six digits, thirty seconds and SHA1.
- Can a page from the web pull out my code?
- No. A call that looks like it came from a page is turned down whatever token it carries, and the digits never reach the page.
- Do I paste fifty keys one at a time?
- The key arrives as a spreadsheet column together with the profiles, and the column heading needs no adjusting. A key that cannot work never lands in the profile, so you never see wrong digits.
Keep reading
One time codes in a profile
Where the key goes and what shows on the card afterwards.
Two-factor authentication
What that second step is and which kinds exist.
Profile transfer
What travels with a profile and under which password.
Free fingerprint check
12 values read in your browser, with nothing sent anywhere.
Add a code to a profile
Paste the key once, and the digits appear in the profile window.