You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an admin-configurable end-user display name for Public Workspace so organizations can brand the feature with their preferred terminology, such as "Domain Knowledge", without changing internal/admin terminology.
User Value
Some organizations want end users to see language that matches their internal knowledge-management vocabulary. Admins should be able to keep managing the feature as Public Workspace while presenting a clearer tenant-specific label to users.
Proposed Behavior
Admin app settings continue to call the capability Public Workspace.
Admins can configure an end-user display name up to 32 characters.
End-user UI surfaces use the configured display name, with Public Workspace as the default when no custom value is configured.
Internal route names, API names, document fields, permissions, and admin-facing terminology remain Public Workspace/public_workspace for compatibility and admin clarity.
Acceptance Criteria
Admin settings include a Public Workspace configuration field for the end-user display name with a 32-character limit.
End-user navigation, page titles, headings, empty states, prompts, and relevant client-side messages use the configured display name.
Admin pages, admin help text, code identifiers, API contracts, permissions, and storage fields continue to use Public Workspace/public_workspace terminology.
The default display remains Public Workspace/Public Workspaces when the setting is empty or unset.
The setting is sanitized before it is sent to frontend templates or JavaScript.
Functional tests cover default and customized display-name behavior.
Summary
Add an admin-configurable end-user display name for Public Workspace so organizations can brand the feature with their preferred terminology, such as "Domain Knowledge", without changing internal/admin terminology.
User Value
Some organizations want end users to see language that matches their internal knowledge-management vocabulary. Admins should be able to keep managing the feature as Public Workspace while presenting a clearer tenant-specific label to users.
Proposed Behavior
Acceptance Criteria
Notes