No, you cannot change the username assigned to your control panel account. The username is embedded in the file system path of your hosting account root, making any modification impractical without risking service disruption across FTP, web sites, application pools, and scheduled tasks.

For Windows-based customers on Shared Hosting, VPS, or Hosted Email plans, the control panel includes a peer user feature. A peer user acts as an alias to the primary account, letting you log in with a different username while retaining identical access to files, settings, and resources. This provides a practical workaround when the original username is inconvenient.

#Why Control Panel Usernames Cannot Be Changed

The primary username is assigned at account provisioning and becomes part of the underlying Windows server directory structure. Your account root is typically mapped to a path that includes the username directly. Changing it would require renaming the home folder, updating IIS site bindings, adjusting FTP user isolation settings, and revising any internal references in databases or application configurations. These operations introduce substantial risk of downtime, permission errors, and broken dependencies, which is why the platform keeps the original username immutable.

D:\Hosting\Customers\primaryusername\wwwroot

System stability takes precedence. Most accounts are configured with the expectation that the username remains constant for the lifetime of the hosting plan. This design prevents accidental breakage of paths referenced in web.config files, connection strings, or scheduled tasks that rely on the original account context.

#Understanding Peer Users

A peer user is an additional login that maps directly to your primary account. It shares the same security context, file permissions, email mailboxes, and control panel features. From the server's perspective the peer authenticates and then assumes the identity of the primary user for all operations. This makes peer users ideal for team access, automated scripts, or simply using a shorter or more memorable username for daily logins without exposing the original credentials.

Peer accounts do not create separate directories or isolated environments. Everything remains under the primary account's folder structure. You can use the peer username for both the control panel and FTP sessions.

#Prerequisites

  • Active Windows Shared Hosting, VPS, or Hosted Email account
  • Access to the primary control panel username and password
  • A chosen peer username that complies with character requirements (alphanumeric, typically 3-20 characters)

#Step-by-Step: Creating a Peer User

Always perform these steps while logged in with the primary account. Peer users cannot manage other peers.

  • Navigate to https://panel.aspnix.com and log in using your primary username and password.
  • Hover over or click the Account Menu in the top navigation, then select the Peers menu item.
  • On the Peers management page, click the Create Peer Account button.
  • Enter the new peer username, a strong password meeting complexity requirements, and any additional profile details requested by the form.
  • Click Add User to provision the account. The system will confirm successful creation.

After creation, sign out of the control panel and test a new login session with the peer credentials. You should see the identical dashboard and have full access to file manager, FTP, email, and other services.

#Limitations and Best Practices

  • Peer users cannot manage, create, or delete other peer accounts. You must log in as the primary user for any peer administration.
  • Peer credentials carry the same privileges as the primary account; treat passwords with equivalent security and rotate them regularly.
  • If a peer password is lost, reset it only while logged in with the primary username.

Choose peer usernames that are easy to type yet hard to guess. Avoid reusing the same password across multiple peers. Monitor active sessions in the control panel if you suspect credential compromise. For FTP clients or application configurations, simply substitute the peer username and password in connection settings while keeping the same server hostname and port.

Using a peer user is the recommended workaround for inconvenient primary usernames. It preserves system integrity while giving you flexibility in daily operations. When performing account-level changes always use the primary login.