Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Organization permissions for visibility on profile #35093

Closed
1 task done
radwanromy opened this issue Oct 29, 2024 · 2 comments
Closed
1 task done

Organization permissions for visibility on profile #35093

radwanromy opened this issue Oct 29, 2024 · 2 comments
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@radwanromy
Copy link

Code of Conduct

What article on docs.github.com is affected?

Benefits of Setting Organization Permissions for Profile Visibility

  1. Enhanced Privacy Control: Users can choose who sees their profiles, which can help protect personal information and reduce unwanted contact.

  2. Customizable Visibility: Allow users to set different visibility levels, such as public, organization members only, or private, enabling them to tailor their profiles based on their preferences.

  3. Improved User Experience: Giving users control over their profile visibility can lead to a more comfortable experience, encouraging engagement within the organization.

  4. Streamlined Collaboration: By limiting visibility to organization members, it can foster a more collaborative environment while keeping sensitive information secure.

Suggested Features

  • Visibility Options: Provide clear options for users to select their preferred visibility settings directly in their profile settings.

  • Notifications: Notify users of any changes to visibility settings or permissions, ensuring they are aware of who can see their profile.

  • Admin Controls: Allow organization administrators to set default visibility settings for all members while still permitting individual adjustments.

  • Audit Logs: Implement logs to track changes in visibility settings, providing transparency and accountability.

What part(s) of the article would you like to see updated?

Benefits of Setting Organization Permissions for Profile Visibility

  1. Enhanced Privacy Control: Users can choose who sees their profiles, which can help protect personal information and reduce unwanted contact.

  2. Customizable Visibility: Allow users to set different visibility levels, such as public, organization members only, or private, enabling them to tailor their profiles based on their preferences.

  3. Improved User Experience: Giving users control over their profile visibility can lead to a more comfortable experience, encouraging engagement within the organization.

  4. Streamlined Collaboration: By limiting visibility to organization members, it can foster a more collaborative environment while keeping sensitive information secure.

Suggested Features

  • Visibility Options: Provide clear options for users to select their preferred visibility settings directly in their profile settings.

  • Notifications: Notify users of any changes to visibility settings or permissions, ensuring they are aware of who can see their profile.

  • Admin Controls: Allow organization administrators to set default visibility settings for all members while still permitting individual adjustments.

  • Audit Logs: Implement logs to track changes in visibility settings, providing transparency and accountability.

Additional information

No response

@radwanromy radwanromy added the content This issue or pull request belongs to the Docs Content team label Oct 29, 2024
Copy link

welcome bot commented Oct 29, 2024

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 29, 2024
@nguyenalex836
Copy link
Contributor

Hi @radwanromy 👋 The best place to send your feedback regarding GitHub as a product is to https://github.com/github/feedback/discussions.

If there's anything in the documents that you have suggestions for updating, please feel free to open an issue.

@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

No branches or pull requests

2 participants