Is there an existing issue for this?
Current behavior
The Workspace name field (Workspace Settings → General) validates character composition in real time — entering a disallowed character (e.g. a comma) is immediately rejected with the message "Workspace name can only contain letters, numbers, spaces, hyphens, and underscores." This confirms the field has active validation logic, not just a passive character filter on submit.
However, this validation only checks character type, not character content. A workspace name consisting entirely of hyphens, underscores, and/or spaces — with zero letters or numbers — passes validation and is saved successfully. This produces a non-descriptive workspace name (e.g. -_________-) that persists across the UI: settings header, sidebar, and workspace switcher.
Steps to reproduce
- Go to Workspace Settings → General
- In the Workspace name field, enter a string with no alphanumeric characters, e.g.
-_________-
- Click Update workspace
Environment
Production
Browser
Safari
Variant
Cloud
Version
Latest
Is there an existing issue for this?
Current behavior
The Workspace name field (Workspace Settings → General) validates character composition in real time — entering a disallowed character (e.g. a comma) is immediately rejected with the message "Workspace name can only contain letters, numbers, spaces, hyphens, and underscores." This confirms the field has active validation logic, not just a passive character filter on submit.
However, this validation only checks character type, not character content. A workspace name consisting entirely of hyphens, underscores, and/or spaces — with zero letters or numbers — passes validation and is saved successfully. This produces a non-descriptive workspace name (e.g.
-_________-) that persists across the UI: settings header, sidebar, and workspace switcher.Steps to reproduce
-_________-Environment
Production
Browser
Safari
Variant
Cloud
Version
Latest