Is there an existing issue for this?
Current behavior
The Display name field does not allow spaces, even though a display name should support full human-readable names.
Currently, the field only allows:
- letters
- numbers
- periods
- hyphens
- underscores
Because of this validation, names like Name Of User, John Doe, Maria Silva cannot be used as display names.
Current behavior
When editing a user profile, the Display name field rejects values containing spaces.
Example value:
The UI shows the following validation error:
Display name can only contain letters, numbers, periods, hyphens, and underscores
This makes the Display name behave like a username, slug, or handle instead of a real display name.
Steps to reproduce
The Display name field should allow spaces and common characters used in personal names.
Valid examples should include:
John Doe
Maria Silva
Name Of User
Restrictions such as "no spaces" should apply to fields like username, handle, slug, or mention name, not to display_name.
Why this is a bug
A display name is meant to be shown in the interface as a readable user name.
The current validation makes user names harder to read in professional workspaces, especially when users have first and last names.
Also, the API already treats display_name as a full display value, so the UI validation appears to be inconsistent with the API behavior.
Steps to reproduce
- Open the user profile settings.
- Go to the name/profile section.
- Set:
- First name:
NAME
- Last name:
USER
- Display name:
NAME OF USER
- Try to save the profile.
Actual result
The form rejects the display name and shows:
Display name can only contain letters, numbers, periods, hyphens, and underscores
Expected result
The profile should accept NAME OF USER as a valid display name.
Suggested fix
Update the frontend validation rule for display_name to allow spaces.
The stricter validation rule should be kept only for username-like fields, such as:
- username
- handle
- slug
- mention name
The display_name field should be validated as a readable name, not as an identifier.
Additional context
This issue affects the user experience in business workspaces because real names are commonly displayed with spaces.
Example:
Displaying names without spaces or forcing users to use underscores/hyphens makes the interface look less natural and less professional.
Environment
Production
Browser
None
Variant
Self-hosted
Version
2.6.0
Is there an existing issue for this?
Current behavior
The
Display namefield does not allow spaces, even though a display name should support full human-readable names.Currently, the field only allows:
Because of this validation, names like
Name Of User,John Doe,Maria Silvacannot be used as display names.Current behavior
When editing a user profile, the
Display namefield rejects values containing spaces.Example value:
The UI shows the following validation error:
This makes the
Display namebehave like a username, slug, or handle instead of a real display name.Steps to reproduce
The
Display namefield should allow spaces and common characters used in personal names.Valid examples should include:
Restrictions such as "no spaces" should apply to fields like username, handle, slug, or mention name, not to
display_name.Why this is a bug
A display name is meant to be shown in the interface as a readable user name.
The current validation makes user names harder to read in professional workspaces, especially when users have first and last names.
Also, the API already treats
display_nameas a full display value, so the UI validation appears to be inconsistent with the API behavior.Steps to reproduce
NAMEUSERNAME OF USERActual result
The form rejects the display name and shows:
Expected result
The profile should accept
NAME OF USERas a valid display name.Suggested fix
Update the frontend validation rule for
display_nameto allow spaces.The stricter validation rule should be kept only for username-like fields, such as:
The
display_namefield should be validated as a readable name, not as an identifier.Additional context
This issue affects the user experience in business workspaces because real names are commonly displayed with spaces.
Example:
Displaying names without spaces or forcing users to use underscores/hyphens makes the interface look less natural and less professional.
Environment
Production
Browser
None
Variant
Self-hosted
Version
2.6.0