nextcloud / nextcloud/server

User Profile should be usable without public visibility

Open
#32,086 20 comments 19 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

2. developing enhancement feature: profile privacy
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
The new user profile feature is a valuable addition to every cloud, but it's sad that it always is publicly visible. The most private clouds are just that: private. And so no information should be visible to the public.

The current profile is a choice between "make some information visible to the public" or "don't use profiles". But profiles are useful for private use inside the cloud, too.

Describe the solution you'd like
The user profile as a whole should at least get an option "only visible to logged in users". Even better, the administrator should be able to configure the visibility for all accounts.

So I request:

  • a user option to make the profile invisible to the public
  • administrator options
    • make no profile visible to the public and the user could not change this
    • make no profile visible to the public by default and the user can change it afterwords
  • for updates make all profiles not visible to the public and the user could change this

Describe alternatives you've considered

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by tracing the user-profile visibility flow and its administrator settings, then compare the implementation with the requested user, default, enforced, and update behaviors; done means the listed visibility policies work for users and administrators.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
full-stack, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.