I would really like to have shared notebooks but I don't want to have a proprietary server backend to do so (and I have a working Nextcloud sync and would prefer to not need to install a dedicated server for one feature). Is there any way to do this now without Joplin server?
Awesome feature, I just setup Joplin server for this feature and its working great.
For those of us using shared notebooks with joplin cloud, can you clarify whether all people sharing a notebook need to be a paid subscriber, and whether only the owner of the notebooks needs to be a pro or teams member? I am trying to introduce my colleagues to Joplin with the minimum investment so I might suggest they start with the basic subscription while I use the higher level to setup the notebook.
Thanks, Phil
Same question as philrasch here. I am about to upgrade to Pro Plan but I am hesitant as it is not clear whether the person who is being shared with should also have Pro Plan. It does not make sense to me he/she also needs to have the plan, as I would be sharing very scarcely
Indeed, I understood that both accounts must be pro or team for the sharing to happen : Joplin cloud plans, Pro share vs Team users - #2 by laurent
Now, @kiteloopdesign , there are various ways to export a given note if this happens scarcely -among others, if I understand correctly, one can just publish it in the form of a web page. So, easy export, but no sharing...
thanks Herve5 for the answer.
Additionally, I am not sure whether it is possible to share notebooks when NOT using Joplin cloud but some private server (eg owncloud). From this github issue it looks like it is possible:
Rgds
@kiteloopdesign , I read above (by @koturk ) that indeed one can benefit from all features when setting one’s own server...
We are currently searching a new notes application / wiki and we are looking at joplin because some developers already use as their personal note taking app. The important feature for us would be a sharing service that we are able to host ourself. I found joplin server but is not well documented. I found something on docker hub.
Will this product be available for everyone? We are willing to pay for joplin Server. Joplin Cloud is a no go.
Regards
Joplin server is available for anyone to host themselves. If you don't find the documentation sufficient, maybe you can find extra install information on this forum? I know others have asked about it in the past.
Joolin cloud is just a Joplin server hosted by the Joplin company, so there isn't really difference to the user. If you're worried about hosting location or the shared host, perhaps you can contact them and work out a deal (I don't know if they do that).
There's an install guide here: joplin/README.md at dev · laurent22/joplin · GitHub
E. g. my Guide for Raspberry Pies. It can easily be used to setup a "normal" server, too.
Thanks for your suggestions. I wikll have a look at that and in the end it might be the best to actually contact joplin. As a company we are interested in long lasting / stable products. All the docker images on docker hub are marked as beta and I found nothing if joplin plans to maintain joplin-server as a self hosting solution in the future.
Lets see how this will play out. Thanks!
The Joplin server is officially provided and maintained as Docker image only and docker is a self hosting solution. It's just that an ARM image is not officially provided only the linux/amd64.
Not only it allows you to use sharing feature, but also separates the services. For example when Nextcloud is on the maintenance you won't be able to use Joplin if it uses Nextcloud. Even if sharing with Nextcloud was possible, I would set it up separately anyway.
Is there a reason for this feature to be limited to the Joplin server?
Yes. Unless you have control of the server software you cannot implement these features. So if you are using somebody else's server it cannot be done,
To elaborate a bit on dpoulton's answer: Joplin wants anyone to be able to use it for free, so you can use all of those services. But they can only do operations such as 'store this file and retrieve that one'. To have a working sync between multiple users, you need more complex custom logic, and it's impossible to reliably get it with the other services.
Let's go back to sharing with E2EE enabled. Now version 3.2 is out and E2EE should be really ready for large note collections on mobile devices.
However as I understand it E2EE is working today with shared notebooks unlike what it says the above feature description.
I tried it on 3.1 and ended with thousands of conflicts because probably one profile/user/device had E2EE enabled and the other not.
But how does it work with the encryption keys. Should I have the same on both users? Or will it ask me somehow for the password of the shared encrypted note on the receiving side and then put me the 2nd key on all devices that are currently synced with the receiving profile?
Now I have one Joplin Cloud user with all my private notes (10K+). Different members of the family use that user. It is not E2EE encrypted and does not need to be but it could if it has to. I will import an other 10K+ set of business notes from Evernotes that have to be encrypted and accessible only by me on a subset of the currently used devices.
I plan making one new Joplin Cloud Pro user for the business notes and will enable E2EE as described in the documentation, import my notes, let things to settle, go to the next business device, sync, let it settle and continue to the next device. So far so good.
Now I want this new user to have access to the private notes of the first user using the sharing feature. I do not want to use a second profile for this.
So what would be the best approach.
Delete all the private profiles on all the devices but one master with private notes (non mobile) and then proceed as in the documentation step by step enabling E2EE and re sync everything? And then share the to second (business) user from the first user the now encrypted notes and let thing settle business device by device?
Is there a way to avoid deleting the notes/profiles of the existing private notes of all devices but one (except naturally those on the business devices)?
Do I really have to activate E2EE on the private devices/user?
Any advices here?
Thanks
OK. I did it and finally had to roll back because of an issue on my business device/proxy
In the long process of getting this to work a stumbled on 3 issues
a) I activated the beta encryption too late on some notes (the welcome notes) could never be recovered. No big deal and now I know where the beta encryption check mark is on the Mac
b) When sharing from a non E2EE user to a E2EE user a notebook this works fine BUT it seems that after sharing you need to resync all the devices. I got conflicts all over and I assume that I actually sync multiple devices at the same time
c) The proxy settings that I tested and worked a while back on our business network to not work anymore. I am not sure if this is a change in Joplin or on the network side
So I will need to try again and here is what I noted to pay attention to:
- ensure that on the new test user on the Mac that the beta encryption (which I hope will then be released) is active at the very beginning
- Clean-up all previous notes before starting in the test user (I still have stuff from my previous tests. Here I located a plugin to start fresh)
- Redo the sharing of the home notes and get those on all the relevant devices synced and settled
- Also sync all the home devices with the shared notes ( what I noted in the previous test is that actually sharing a notebook seems to require quite a extensive resync of all devices that have the notebook)
- Make it step by step and watch for conflicts. Do this on ALL devices with home notes
- At this point no notes should be encrypted anywhere and no clonclits
- Then import all the business notes on the Mac at once from Enex and sync and encrypt up to the very end
- Sync all business devices step by step and let it decrypt (watch for not decrypted notes)
- Check on ALL home devices and delete ALL home profiles from the business devices. Be very careful that they do not start syncing