What Is a Username
A username is a name that a computer system uses to identify an account. For example, a person might sign in to a learning website as `maya27`. The username tells the website which account they mean; a password, passkey, or another authentication method helps establish that they are allowed to use it. A username is not a password and should not be treated as a secret proof of identity. Knowing someone's username does not, by itself, authorize access to their account.
An account is the collection of information and permissions the service keeps for a user: saved preferences, documents, messages, course progress, and access rights. A username is one way to refer to that account. Many systems also assign an internal account identifier that is different from the visible username. This allows the system to keep records attached to the same account even if it permits the person to change their username. Other services do not allow username changes, so the rules must be checked for each service.
A username, display name, email address, and password have different jobs. A username often has to be unique within one service: if `maya27` is already taken, a new account may need another name. That does not make it globally unique; a different person could use the same name on another website. A display name is the friendly label other people see, such as “Maya,” and a service may allow many people to share it. An email address identifies a mailbox and may be used for contact, recovery, or sign-in. Some services use the email address itself as the login identifier; others ask for a separate username. A password is a secret authentication factor. A public profile handle, such as `@maya27`, may match a login username, but that depends on the service.
Signing in separates identification from authentication. In a common username-and-password flow, you enter a username, the service locates the associated account, and it checks the submitted authentication information. If an additional factor is required, that check must also succeed before normal account access is granted. The service then establishes a signed-in session. Authorization is a further question: which actions may this account perform? A student account might read a course, while a teacher account may also edit it. Correctly signing in does not automatically grant administrator privileges.
The following flow is a simplified successful sign-in path. A failed check must not grant access; the service may show a generic error that does not reveal whether the username or password was wrong. Some modern sign-in flows use passkeys without asking the user to type a username, but they still associate successful authentication with an account.
Choosing a username means following the rules of that particular system. A service may limit length, allow only certain characters, reserve names such as “admin,” or treat uppercase and lowercase letters as equivalent. Other systems distinguish letter case. Never assume that rules from one website apply to another. If a name is already in use, choose a variation you can remember. For a public username, avoid including private information such as a full birth date, home address, or phone number. Do not reuse your password as a username. A recognizable username can help friends find you, but reusing the same public handle across services can also make those accounts easier to connect.
On Ubuntu, a local username identifies an operating-system account. A local account can own files and run processes, while permissions control which files it can read or change. The command `whoami` prints the username associated with the current effective user identity. A home directory often has a path such as `/home/maya`, although administrators can configure a different path. Linux also uses numeric user identifiers, or UIDs, for ownership and permission checks. A username is the human-readable label associated with that identity. A website account and an Ubuntu account are normally separate: choosing `maya27` on a website does not create a Linux account on your computer.
Try it: imagine a learning-site profile with the username `maya27`, display name “Maya,” and an email address used for recovery. Which field selects the account at sign-in? The username, unless the service uses email sign-in. Which field is a friendly label? The display name. Does knowing either field let someone access the account? No: the service must still authenticate access. This connects usernames to the earlier topics on accounts, passwords, files and permissions, and the difference between data that identifies something and evidence that authorizes its use.