Skip to content
English - United States
Contact Us
  • There are no suggestions because the search field is empty.

FAQ - What are the validation requirements for a Username, Password, Email, and Phone Number in Smartwebs?

This article is an overview of Smartwebs' User Information Validation Requirements, which help maintain accurate account details and protect account security. Validation applies when creating user accounts, editing profiles, resetting passwords, updating account information, and changing multi-factor authentication (MFA) methods.

Purpose

Smartwebs validates user information to help maintain accurate account details and protect account security. Validation applies when creating user accounts, editing profiles, resetting passwords, updating account information, and changing multi-factor authentication (MFA) methods.

If a value does not meet the system's requirements, it will be rejected and an error message will identify the field that needs correction.

1. What are the USERNAME requirements?

Your username must meet all of the following requirements: 

  • Unique Username required: Usernames must be globally unique across Smartwebs, independent of account or application.
  • Allowed characters: Only visible Unicode characters are supported. Any Unicode control, formatting, surrogate, private-use, and unassigned characters will be rejected.
  • Length requirements: Minimum length of 2 Unicode characters, maximum length of 100 Unicode characters.
  • Normalization: Leading and trailing whitespace and Unicode separators are rejected.
  • Case sensitivity: Usernames are case-insensitive.
  • Validation Process: Usernames are not silently trimmed, truncated, or case-normalized.

2. What are the PASSWORD requirements?

Your password must meet all of the following requirements:

  • Length: Must contain 8–50 characters.
    • At least one uppercase letter.Required characters:
    • At least one lowercase letter.
    • At least one number.
    • At least one symbol.
  • Patterns: Must not contain any obvious sequential patterns, such as 123456, abcdef, or qwerty.
  • Personal Information: Must not contain your first name, last name, username, email address, or cell phone number.
  • Breached Passwords: Must not be identified by the system's breached-password screening.
  • Case Sensitivity: Passwords are case sensitive. Password checks for personal information are case-insensitive where applicable.
  • Hashing: Password validation occurs before password hashing.
  • Validation Process: Passwords are not silently trimmed, truncated, or case-normalized.

Tip: Create a unique password that combines uppercase and lowercase letters, numbers, and symbols without including personal information or predictable sequences.

3. What are the EMAIL address requirements?

Your email address must meet all of the following requirements:

  • Format: Use a valid email address format, such as name@example.com. Must meet conventional ASCII email address standards. Missing or invalid characters, multiple @ symbols, and disposable email addresses will be rejected.
  • Content: Must contain exactly one email address per field. Multiple email addresses added to the same field will be rejected, even if separated by commas or semi-colons. 
  • Domain validation: Include a valid domain and top-level domain. Must meet internationalized Unicode domain names. Invalid domain labels and missing domain syntax will be rejected, such as John Smith <john@example.com>
  • Length: Must be a maximum of 254 characters *subject to database storage capacity.
  • Normalization: Leading and trailing whitespace, leading or trailing dots, consecutive dots, control characters, and invisible formatting characters are rejected.
  • Validation Process: Email addresses are not silently trimmed, truncated, or case-normalized.

Tip: Check for spelling errors and make sure the domain is complete. Leading and trailing spaces will be removed, and uppercase letters will be converted to lowercase.

4. What are the PHONE number requirements?

Your phone number must meet all of the following requirements:

  • Format: Phone numbers will be accepted in the following standardized formats:
    • +1 512-555-0123
    • (512) 555-0123
    • 512-555-0123
    • 5125550123
  • Normalization: Formats are then normalized before storage as canonical values using ASCII characters only.
  • Content: One phone number per field. 
  • Length: Maximum of 21 characters.
  • Extensions: Optional extensions will be supported, containing 1–4 digits.
  • Location: US based phone numbers will be supported. International phone numbers will be supported using the international standard E.164.

5. Why was my user information rejected?

A username, password, email address, or phone number may be rejected if it does not meet the system's validation requirements. Review the requirements above, correct the invalid information, and try again.

6. Which phone numbers or characters are not accepted?

Phone numbers may be rejected if they contain:

  • Alphabetic characters or unsupported punctuation.
  • An invalid number of digits or an unsupported numbering format.
  • Spaces and periods.

7. Can I use a landline for multi-factor authentication (MFA)?

No. If your phone number is selected as your MFA method, it must be a mobile-capable number that can receive SMS messages. Landlines and numbers that cannot receive SMS are not eligible for SMS-based MFA.

8. Does validation apply only when I create an account?

No. Validation applies when creating accounts, editing profiles, resetting passwords, updating account information, and changing MFA methods. It also applies to user information entered through supported imports and integrations.

9. What should I do if my information is rejected?

Review the error message to identify the field that needs correction. Verify that the information meets the requirements in this article, make the necessary changes, and submit it again. If the issue continues, contact your association's management team or Smartwebs Support for assistance.

End of FAQ