How to disable user profile?

Hi, I am new to Nextcloud.
I’ve just testing the NC Hub10 on my web-server.

I noticed that the user profile information is visible by default, and I really don’t want “email address” is visible for the other users.
I tried to chenge visibility setting on my profile, but it didn’t work at all.

I am also trying to chenge the default setting of profile visibility.
Reffered the manual here : Profile configuration — Nextcloud latest Administration Manual latest documentation

I set “account_manager.default_property_scope” as private in config.php, but it does not work at all again. I create new user with this setting, but the information is still visibile.

I can not find any admin setting on the web. Is this the desigin of Nextcloud?

Hi @Noboru_Tanaka,

First of all, you can disable “Profiles” and the “System address book” globally by adding the following line to config.php:

'profile.enabled' => false,

…and running the following command:

occ config:app:set dav system_addressbook_exposed --value="no"

See also here: Nextcloud Documentation: System Address Book

However, even after doing this, users will still be able to find each other via the file-sharing dialog, where email addresses are also displayed.

If you want to prevent this as well, go to “Administration Preferences” → “Sharing” → “Sharing Privacy Preferences” and uncheck “Allow account name autocompletion in the sharing dialog…” However, this will completely prevent users from finding each other in the sharing dialog, making internal collaboration impractical.

Important Note!

None of these settings should be used to implement actual multi-tenancy, such as offering Nextcloud as a service to completely unrelated individuals or organizations. Nextcloud is not designed for this purpose, and even with the above settings, it may still be possible for users to access information about others under certain circumstances. If multi-tenancy is your goal, you should set up dedicated instances for each customer or organization.

As far as I know, Property scopes correspond to the same settings users can configure themselves on the “Personal Info” page, and If you click on the “scope” of the Email field there, it explicitly states that you cannot set the email property to “Private” and explains why.

Conclusion

If users need to collaborate on this instance, inform them that their email address will be visible to others. Users who do not agree can either:

  1. Use a dedicated email address for Nextcloud if they do not want to share their primary address.
  2. Remove their email address from their “personal settings,” which will prevent them from receiving notifications and password reset emails, and possibly from using some collaboration features.
    EDIT: I tested it in the meantime. If a user doesn’t provide an email in their personal settings, the user name is shown in the share dialog instead, and sharing still works.

If collaboration is not required, go to “Administration Preferences” → “Sharing” → “Sharing Privacy Preferences” to adjust visibility settings.

If multi-tenancy is needed, setting up dedicated instances per customer or organization is the way to go.

1 Like

Thanks, bb77.

Well, I did profile disabled and stop shareing information.
And, now understand what you said.

Actually, I need collaboration, but it can be done without email.
I want Nextcloud can provide collaboration function without private information, such as email address. And I believe that can be done.

I will consider how to oparate this system…

If you find out how to do this, I would appreciate it if you could share it here, because we already had a long discussion about this in >> this thread << and at the beginning we also thought it was possible. Unfortunately, at the end of the thread we had to admit that it is not possible.

Or to be more precise, it’s not possible to change email visibility independently of the sharing settings.

There is also an issue/feature request on GitHub regarding this, which is still open: Allow to set email address to private independent of sharing settings · Issue #9638 · nextcloud/server · GitHub

How about using unique “nickname”?
I am using wordpress community for collaboration purpose, and in this way, user doesn’t need to show thier email addres to communicate with other usres.

I am thinking to connect Nextcloud to wordpress, so that the user can share the files. But I don’t want their email visible. That’s the reason I am asking this.

Sorry, I have not read the past discussion, but I would like to know why unique “Nickname” or UID can not be used instead of email?

Allow me to quote myself… :wink:

I tested it in the meantime. If a user doesn’t provide an email address in their personal settings, the user name is shown in the share dialog instead, and sharing still works.

However, the obvious disadvantages of not providing an email address, such as not being able to receive notifications and password reset emails from Nextcloud, will of course still remain.

Since we are in the Netxcloud forum, I am assuming that we are talking about what is possible in Nextcloud, and unfortuantely in Nextcloud it can’t be done. :wink:

I can’t speak to the whys, but I can say that the only way to prevent users’ email addresses from appearing in the share dialog, while still allowing users to find others to share files with, is for those users who don’t want their email address exposed to simply not provide one at all.

Whether this is a viable workaround for you depends on your specific use case and is up to you to decide.

Thanks again.

Well, I did not mean that user does not want to regist their email, but they don’t want to show their email for the other users.
It is okay for them to use email for nortification purpose, but I think for those collaboration purpose, unique nickname can be used for that.

Anyway, I will expolorer Nextcloud how I can manage this issue.
Thank you.

Yes, that would be ideal, but unfortunately it doesn’t seem to be possible in Nextcloud if other users are supposed to find them in the share dialog. I and others have tested it quite extensively, see also the linked thread. Also, I don’t think the GitHub issue about this would still be open if the requested feature was already implemented.

I like the sense of optimism in this. ‘Never lose hope’, I guess :wink:

If you do find a solution, I and I am sure many others would appreciate it if you would post it here.

Good luck.

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.