1
0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-24 10:27:10 +02:00

Doc: Mention that E2EE works with the notebook sharing feature

This commit is contained in:
Laurent Cozic 2022-01-16 16:50:05 +00:00
parent 35e6aaceb7
commit 8cdb73bd65

View File

@ -34,15 +34,13 @@ On mobile and CLI, you cannot currently share notebooks, but you can view or mod
Currently they have full access to the data, including reading, writing and deleting notebooks or notes. In a future version, access control might be implemented. For example, to only give read-only access to the shared notebook. Currently they have full access to the data, including reading, writing and deleting notebooks or notes. In a future version, access control might be implemented. For example, to only give read-only access to the shared notebook.
### What can actually be shared? ### What is actually shared?
All the sub-notebooks, notes and resources within the shared notebook are shared. All the sub-notebooks, notes and resources within the shared notebook are shared.
### Does it work with End-To-End-Encryption? ### Does it work with End-To-End-Encryption?
Yes and no. It is possible to use the share notebook feature even with E2EE enabled, however any shared notebook or note will not be encrypted, otherwise you would have had to give your master key password to the people you share with, which you'd probably not want to do. Yes it does. Both sharer and recipient need to have E2EE enabled for it to work.
In a future version, this might be supported. For example by automatically creating a new master key for the shared notebook. You would then provide the recipients with that master key password.
### What can it be used for? ### What can it be used for?
@ -52,4 +50,4 @@ Some ideas:
* Work on a project with colleagues. Everybody can access various work-related documents, add to them, modify them, etc. That could serve as a knowledge base for a project. * Work on a project with colleagues. Everybody can access various work-related documents, add to them, modify them, etc. That could serve as a knowledge base for a project.
* Another possible use, which has been requested many times, is to support multiple profiles. You could create a main profile that have access to all notes, and in there create a Work and Personal notebook. Then you would create a separate account for work. You can then share your Work notebook with that other account. That way the work account will only have access to the Work notebooks. You can use this technique in various ways to split your notebooks between multiple accounts and ensure strict separation between datasets. * Another possible use, which has been requested many times, is to support multiple profiles. You could create a main profile that have access to all notes, and in there create a Work and Personal notebook. Then you would create a separate account for work. You can then share your Work notebook with that other account. That way the work account will only have access to the Work notebooks. You can use this technique in various ways to split your notebooks between multiple accounts and ensure strict separation between datasets.