Set the AnyDesk unattended access password on the rep's forecast PC to longer than 12 characters, free of simple or repeating patterns, and turn on two-factor authentication. AnyDesk requires a minimum of 8 characters but highly recommends going past 12; the 6-digit code from your authenticator app adds a second door.
- Minimum password length is 8 characters with no simple or repeating patterns
- Recommended length is longer than 12 characters — this is what you set
- Enable two-factor authentication: a 6-digit code from Google Authenticator, Microsoft Authenticator, or FreeOTP follows the password
- Decide the short-term password checkbox: unticked means no 2FA prompt on automatic reconnect, such as a remote restart
- Store the password in your firm's password manager, and rotate it when the rep leaves or you suspect a leak
You have a rep out this week. The forecast sits on their PC. You need in, from your desk, without waiting on a phone call. AnyDesk is the tool, and the main thing standing between you and that machine is a password you chose once, with 2FA adding a second check once it is enabled. Two lengths matter here. One is the floor. One is the length you should actually set.
AnyDesk's unattended access documentation sets the floor at 8 characters. The same page recommends going past 12. Those are the two numbers that should shape what you type into the password field on the rep's forecast PC today.
What the two lengths mean
The first length is a rule you must clear. The password on any AnyDesk client with unattended access enabled has to be at least 8 characters. It should also avoid simple or repeating patterns. That is the floor AnyDesk sets in its unattended access setup guide. If you set fewer characters, or a string of the same letter, you have not met the requirement.
The second length is advice, not a rule. The same guide recommends a password longer than 12 characters. The reason it gives is practical: anyone who has your password and your AnyDesk ID can gain full access to the device, subject to the permissions you configured. A longer string gives an attacker more to guess before that happens.
So your two lengths are an 8-character minimum you must meet, and a 12-plus length you should aim past. On the rep's forecast PC, set the second one. Treat the first as the line below which you never go.
Why two lengths and not one? Because they do different jobs. The minimum stops you from choosing something useless. The recommendation is what actually protects a machine that sits alone in a hotel room or a home office, where anyone holding both the unattended access password and the AnyDesk ID could gain access.
How the floor works in practice
The floor is a hard stop. AnyDesk's documentation states the password must be at least 8 characters long and should not use simple or repeating patterns.
The source does not define which strings AnyDesk treats as simple or repeating, so judge the pattern yourself before you save. These clear the length bar but fail the pattern bar. AnyDesk groups both conditions into one sentence, which means satisfying one does not satisfy the other.
Before you type anything into the field, run a quick mental check. Count the characters. Then look for runs, repeats, and anything you also use for email or the CRM. If any of those show up, start over.
The floor also applies every time you change the password. If a rep rotates machines, or if you reset access after someone leaves, the new string clears the same bar.
Why past 12 is the length you should set
The recommendation past 12 characters exists because of a specific attack path. Anyone with your password and your AnyDesk ID can take full control of the device, within the permissions you configured. For an attacker without 2FA, the password is the main secret; with 2FA on, the 6-digit code is a second one.
Past 12 characters, the guessing space grows fast. A string that clears the floor by only a few characters gives an attacker far less work than a string that runs well past the recommendation, even if both technically qualify. AnyDesk frames the recommendation as "highly recommended," which is stronger than optional.
On a rep's forecast PC, the stakes are not abstract. The machine holds a live pipeline, the notes that explain each deal, and likely the login to your CRM. Full access means someone could read it, copy it, or alter it. The permission settings you configure limit what a session can do, but reading is often enough.
A practical shape for the string: pick a passphrase of several real words, joined without spaces, running well past 12 characters. Passphrases are easy to type under pressure and hard to guess. Avoid the rep's name, the company name, and the word "forecast."
Change it when the rep leaves the firm, when you suspect a leak, and on any schedule your own security policy requires. AnyDesk's page does not set a rotation interval, so that schedule is yours to write.
Where two-factor authentication changes the flow
AnyDesk provides two-factor authentication for remote access to devices where no one is physically present. That is exactly your situation: the rep is away, and you are reaching the PC unattended.
With 2FA enabled, the password alone is not enough. After you submit the unattended access password, AnyDesk prompts you for a 6-digit authorization code from your authenticator app. That prompt arrives whether you typed the password yourself or let AnyDesk fill it.
The 6-digit code comes from an app on your phone. AnyDesk names Google Authenticator, Microsoft Authenticator, and FreeOTP as examples. Install one before you turn 2FA on, so the first connection does not stall while you set the app up.
The sequence looks like this. You enter the AnyDesk ID of the rep's PC. You submit the unattended access password. AnyDesk asks for the 6-digit code. You read it off your phone and enter it. The session opens.
Notice what this does to the two password lengths. With 2FA on, a longer password still matters, because the password is still the secret that protects the machine when the second factor is not asked. But the code adds a second door. An attacker with only the password faces a fresh 6-digit prompt on each manual connection, though not on automatic reconnects while the short-term password checkbox is unticked.
The source does not say how long the 6-digit code lives, or how many wrong attempts AnyDesk allows before it locks. Ask your AnyDesk administrator, or check your own account settings, if you need those details before you roll this out.
Short-term passwords and what they skip
AnyDesk has a setting for short-term passwords. The checkbox is labeled "Enable for short-term passwords," with remote restart as the example given. When it is unticked, AnyDesk will not ask for the 2FA verification code when a session reconnects on its own. A remote restart is the example the documentation gives.
This matters for a forecast PC more than you might expect. If your process involves rebooting the machine, or if the session drops and reconnects, the behavior depends on that checkbox. Ticked, the 6-digit prompt appears on reconnect. Unticked, it does not.
The checkbox governs only automatic reconnection: a hand-typed connection still prompts for the 6-digit code whether the box is ticked or unticked. It describes the reconnect case. Confirm the behavior in a test session on a machine you can physically reach, before you rely on it during the rep's absence.
Set the checkbox to match your risk. If the rep's PC will reboot while unattended and you need to reach it afterward without someone at the desk, unticking the box stops AnyDesk requesting the 2FA code when the session reconnects automatically after the restart. If you would rather see a 6-digit prompt every time the session resumes, leave it ticked.
The two lengths do not change with this setting. You still clear the 8-character floor and still aim past 12. The checkbox only governs whether the second factor reappears when AnyDesk reconnects by itself.
A short table of the settings that matter
Here is the whole configuration at a glance, built from the facts above.
| Setting | What AnyDesk's page says | What you do on the forecast PC |
|---|---|---|
| Password length, minimum | at least 8 characters, no simple or repeating patterns | never go below this line |
| Password length, recommended | longer than 12 is highly recommended | set a string past 12 |
| Two-factor authentication | available for remote access with no one present | turn it on |
| Code format | 6-digit authorization code from your authenticator app | keep the app on your phone |
| Authenticator apps named | Google Authenticator, Microsoft Authenticator, FreeOTP | install before enabling 2FA |
| Short-term password checkbox, unticked | no 2FA code asked on automatic reconnect, such as remote restart | decide based on whether you need reconnects |
Setting the password on the rep's forecast PC
You have the two lengths. Now the sequence. If the rep is available for one more call before they leave, do this with them. If they are already gone, you will need physical access to the machine, or a colleague who has it.
Open AnyDesk on the rep's PC. Find the unattended access settings. AnyDesk's setup guide walks through this path. Type your chosen string into the password field. Make it past 12 characters, free of runs and repeats, and unrelated to anything the rep uses elsewhere.
Confirm the password. If the field rejects the string, you are under the floor or inside a banned pattern. Start over rather than trimming.
Now check the permissions you configured. AnyDesk's note about full access is explicit that access depends on the configured permissions. A long password with wide-open permissions is still a wide-open machine. Limit the session to what a forecast review needs, and narrow it to whatever the configured permissions allow.
If the rep is present, connect from your desk to their PC while they watch their screen. The 6-digit prompt should appear on your side. The session should open only after you enter it.
If the rep is gone, test from your desk to the PC. Walk the full sequence: ID, password, 6-digit code. Confirm you can reach the forecast, open the file, and then disconnect cleanly.
Write the password down in your firm's password manager, not in a note on your own desktop. Anyone with your password and the AnyDesk ID can take the machine, so treat the string with the same care you would give a bank credential.
What to do after you are in
You have the session. The job is the forecast, not a tour of the machine. Open the file, read what you need, and close it. Resist the urge to leave the session open while you work on something else. Each minute the connection stays open is a minute an already-open session can be used, which is the risk 2FA does not cover.
If you need to pull the forecast out, work within the permissions you set for the session. If the rep uses a cloud drive, reaching the drive through the session is cleaner than copying files to your own machine.
Log what you did. A short note with the date, the session, and what you touched keeps the audit trail straight if someone asks later. AnyDesk's page does not describe a log format, so use whatever record your firm already keeps.
When the rep returns, tell them you were in. Hand back control. If you changed any permission during the session, change it back before they resume work.
If the rep is leaving for good, rotate the password the same day. The old string has been typed, screenshotted, and possibly remembered. A fresh string past 12 characters starts the clock clean.
A word on what the sources leave open
AnyDesk's setup guide gives you the floor, the recommendation, the 6-digit flow, and the short-term password behavior. It does not tell you how often to rotate, how long a 6-digit code lives, or what a specific permission set allows on your plan. Those details are yours to confirm. Ask your AnyDesk administrator, or open your own account's permission panel, before you write the policy for your firm.
Related guides
Questions a revenue leader usually asks
Does the rep need to be at their desk when I connect? No. That is the point of unattended access. AnyDesk provides two-factor authentication for remote access to devices where no one is physically present, which is your exact case.
What if I lose my phone with the authenticator app? The documentation names Google Authenticator, Microsoft Authenticator, and FreeOTP as examples but does not describe a recovery path. Confirm recovery with your AnyDesk administrator before you rely on the app alone. If your firm uses a shared authenticator, know who holds it.
Is an 8-character password fine if I also turn on 2FA? The floor stays the floor. AnyDesk requires at least 8 characters regardless of 2FA. The recommendation past 12 still stands. The 6-digit code adds a door; it does not shrink the first one.
What happens if the PC restarts while I am away? It depends on the short-term password checkbox. Unticked, AnyDesk will not ask the 2FA code when a session reconnects automatically, and the documentation names a remote restart as the example. Ticked, the prompt reappears on reconnect.
Set a distinct string on each machine, past 12 characters, so one leak does not open the whole floor.
Do I need to change the password after every session? The source does not say so. Rotate when someone leaves, when you suspect a leak, or on the schedule your own policy sets. Ask your AnyDesk administrator if you need a firm interval.
Will AnyDesk stop me from picking a weak string? The page states the rules, but it does not describe how or whether the field enforces them, so check the string yourself against both conditions before you save it. Check the string yourself against the two conditions before you save it. The floor and the pattern rule are both on you to meet.