cPanel User Manager: Link Email, FTP, and Web Disk Right

A customer creates a user in cPanel's User Manager, expects it to show up under Email Accounts or FTP Accounts, and it doesn't. Or they reset a password there and the person still can't log into webmail. Nine times out of ten this comes down to one thing: User Manager creates an identity first and services second, and it's easy to stop halfway.

What User Manager Actually Is

Most cPanel users are used to two separate tools: Email Accounts for mailboxes and FTP Accounts for file transfer logins. Both still exist and both still work. User Manager (cPanel → Preferences → User Manager) is a newer, unified layer sitting on top of them. Instead of creating a mailbox in one screen and an FTP login in another with a different username and password, you create one "user" — a name and an email address for password resets — and then attach whichever services that user needs: Email, FTP, and Web Disk.

That's the whole point of it: one identity, several services, one password to reset when someone forgets it. The confusion starts because cPanel didn't retire the old tools when it added this one, so you now have two ways to end up with the same kind of account, and they don't always show each other's work clearly.

Where the Two Systems Overlap (and Where They Don't)

That last row is the one that trips people up: an FTP login created through User Manager never appears in the classic FTP Accounts screen. If you go looking for it there, you'll conclude the account doesn't exist, when it's actually working fine.

Symptom: "I Created the User but They Can't Log In"

Cause: creating a user in User Manager only creates the identity. Until you explicitly enable a service and set a password for it, there's nothing to log into. It's a two-step process that looks like one step.

Fix:

1. Go to cPanel → Preferences → User Manager.
2. Find the user, click the three-dot menu, and check which services show a colored icon (enabled) versus a greyed-out one (not set up).
3. Click the service icon (Email, FTP, or Web Disk) you need and choose Manage, not just Edit — Edit only changes the contact name, Manage is where you set the actual login password and quota.
4. Set a password that meets the strength meter and save. The account is only usable after this step.

Symptom: Web Disk Connects, Then Immediately Rejects the Password

Cause: Web Disk (WebDAV) in cPanel defaults to Digest Authentication on most setups, which is a different hashing scheme than the plain password auth Email and FTP use. If the user's Windows Explorer, macOS Finder, or third-party WebDAV client only supports Basic auth, digest-authenticated logins fail with a generic "incorrect password" even though the password is right.

Fix: in User Manager, open the user's Web Disk service and switch to Password Authentication instead of Digest — this uses the same credential type as FTP and is compatible with more clients. If your organization requires digest for security reasons, keep it, but connect using a client that explicitly supports RFC 2617 digest auth (native Windows and Finder WebDAV support varies by OS version).

Symptom: Deleted a User, but an Old Mailbox or FTP Login Still Works

Cause: this happens when the underlying mailbox or FTP account predates User Manager, or was created through the classic Email Accounts / FTP Accounts screens rather than through a User Manager identity. Deleting a User Manager entry only removes what User Manager created and tracks — it doesn't reach into classic accounts that happen to share a similar name.

Fix: don't assume one deletion covers both. After removing a user in User Manager, separately check Email → Email Accounts and Files → FTP Accounts for any leftover entry with the same username, and remove it there too if it's not meant to stay. This is also why mixing the two creation methods for the same person is the single biggest source of "ghost account" tickets — pick one method per account and stick with it.

Symptom: Password Reset in User Manager Didn't Change the Email Password

Cause: if the mailbox was originally created in classic Email Accounts and only later linked into User Manager, some cPanel versions store the credential separately per service rather than truly unifying it. Resetting the "user" password updates the contact record but the individual service (Email) can still need its own reset.

Fix: after any password change, open the specific service (click the Email icon for that user, not just the user row) and confirm or re-set the password there directly. Treat the top-level user password as the account's identity password for notifications, and the per-service password as the actual login credential — they should match, but confirm it rather than assume it.

When to Use User Manager vs. the Classic Screens

• Use User Manager when one person needs more than one service (say, a support staffer who needs both an email inbox and scoped FTP access to a subdirectory) and you want a single password-reset flow.
• Use classic Email Accounts / FTP Accounts for simple, single-purpose accounts — a shared info@ mailbox, or a one-off FTP login handed to a contractor for a single upload — where there's no real person tied to a reset-password contact.
• Don't mix both for the same login name. If priya@yourdomain.com exists as a classic email account, don't also create a User Manager user named priya expecting them to merge — they won't, and you'll end up debugging which one actually owns the mailbox.

Prevention

• Pick one creation method per cPanel account and document it, especially if more than one person on your team manages hosting.
• When onboarding a new team member who needs multiple services, start in User Manager and enable services from there — don't create the mailbox in Email Accounts first and try to "adopt" it into User Manager later.
• Audit periodically: compare the User Manager list against Email Accounts and FTP Accounts for orphaned entries, especially after staff turnover.
• For Web Disk, decide on Digest vs. Password authentication org-wide rather than per-user, so client compatibility doesn't turn into a recurring support ticket.

None of this is complicated once you know cPanel is running two account systems side by side. The tickets happen when someone assumes User Manager replaced the classic tools instead of sitting alongside them.