[IMPORTANT] Please note that this site will be disabled on October 31. In it's place, the new JumpCloud Help Center is live! Check it out here!

Support Center

Naming Convention for Users

Bringing together multiple existing, disparate services like Windows, Linux, Google Apps and others into a single directory requires consideration of a naming convention for the username.  This article will discuss:

Determining Local Usernames

JumpCloud The JumpCloud account username is specified in the Username field of the User aside User Details tab in the JumpCloud Administrator Console.  
IMPORTANT: In order for the JumpCloud account to take over an existing account on a system, the usernames must match, for Linux and Mac, this match is case sensitive.
  • Mac -  The GUI typically shows the term 'username' next to what JumpCloud would consider the 'Full Name'. Here, the 'Account name' needs to match the JumpCloud account.  

    - To find the Account name, go to: System Preferences > Users & Groups > right-click the user > Advanced Options.  The Account name is shown on this screen
  • Windows - The GUI within the control panel for 'User Accounts' shows the 'Full Name' and not the actual username of the Windows user.

    - To find the 'username', go to: Control Panel> Administrative Tools > Computer Management > Local Users and Groups> Users. The 'username' name is shown on this screen under the 'Name' heading. 

Please refer to How To Use Commands To Query Existing Local Accounts for more information on querying local users using JumpCloud Commands or the system's command-line.  

Determining a Naming Convention

Usernames must:

  • Start with an alphabetic character.
  • Be 30 characters or fewer for Mac or Linux, or 20 characters or fewer for Windows.
  • Contain only valid Unix Characters - letters, numbers, “-”, “.”, and “_”.
  • Not contain spaces.

  • System character restrictions.
  • Length (Windows is limited to 20 characters).
  • Case - “user” is not the same as “USER” is not the same as “User.”
  • Generally, it's good practice to use a convention such as first initial and last name (bexample), first name and last name (bobexample), or another convention where it is unlikely two users will have the same username. After a convention is selected, recreate or rename any users that aren’t in compliance.
  • We recommend creating a scalable naming convention to grow with your organization. Consider how your organization may change or grow in the future when as you select a naming convention.

Changing Existing Usernames in JumpCloud

If a JumpCloud user is not bound to any resources, you can change their username.


  • We recommend that you change a username during the user creation process, prior to binding the user to resources. For example, if you mistype a username after you create and save a user, you can change the username.
  • A username can only be modified if the user is not bound to any resources. Learn more about potential impacts of removing resource bindings to make username modifications.

Changing Existing Usernames in Systems

Application installations can be dependent on the existing username. Refer to your software vendor for further consideration on possible issues and remediation.

The process of renaming users will vary by OS type and version. The following is not meant to be exhaustive, nor the only method for renaming usernames.

NOTE: Changing existing usernames for Mac and Linux is generally not recommended unless you have a full understanding of the impacts from doing so. Changing the username on these platforms can have adverse effects on application and file access.

Last Updated: Jul 24, 2019 10:55AM MDT

Related Articles
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found