GitHub administrators now have granular control over how user profiles are displayed across the platform, a change impacting repositories, issues, pull requests, and discussions. The new settings allow enterprise and organization admins to choose whether to show a user’s full name alongside their username.
The update introduces three options for managing profile name visibility. At the enterprise level, administrators can “Enable everywhere,” “Disable everywhere,” or “Let organizations decide.” When an enterprise-level policy is set to “Let organizations decide,” individual organizations within that enterprise gain the ability to independently configure their own profile name visibility settings – toggling the feature “On” or “Off” as desired. If an enterprise sets a policy of enabling or disabling profile names, that setting applies across all organizations within the enterprise.
The change is intended to provide flexibility for organizations with varying privacy or branding preferences. According to GitHub documentation, the organization-level setting is only configurable if the enterprise-level policy allows it.
The rollout of these features follows a period of public preview for organization custom properties, which were made generally available earlier this month, according to a GitHub blog post. These custom properties allow organizations to add metadata to their repositories, and members.
The new profile name visibility settings are available immediately. Administrators can access the configuration options through their enterprise or organization settings on GitHub.
