Replies: 1 comment 1 reply
-
|
@Kantziko I've been deep down the rabbit hole you're in. Long story short, to work in environments like that or SMB shares, it's theoretically possible, and I've started developing plugins myself that in theory will do it. However, nothing exists yet that allows for resolving the conflicts that happen when you do that approach. Currently, I'm developing a fork of this project (will do PRs soon) for corporate type environments that allow assigning tasks Having multiple users on a shared vault like this requires either something like Obsidian Livesync (requires know-how to self-host it), or you buy Obsidian Sync, and you get it for everyone else who will be working in the vault. Issue is that anyone can open the vault outside of corporate environment which presents data security risks. If you can swallow that risk, then you can have the IT team use host firewalls on the computer to limit network connections for the Obsidian application using what mentioned in the Obsidian docs around team usage. Don't use mine yet, but I'm at least developing it and should have PRs ready in the next week or two. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there,
First of all, I just found out about the plugin, and it shows great potential imo.
Context
For the context, I am helping a small business in building a complete set of reference tables, knowledge repositories, structured data for their Enterprise Architecture, and so on. Of course, I am building most of it in Obsidian. Therefore, we have common vault, stored in a shared folder through Teams (probably not the best idea, but fastest for now). Each user (we have around 10 of them) can access part of the information through the Publish website, but also access all of it through a local access to the shared vault, by using a local Obsidian app.
Issue
As I started configuring the TaskNotes plugin and being really happy about what I was creating, another user opened the vault. And, magically, my world turned to s**t. It turns out that the simple fact of launching Obsidian from another device, in that environment, after my initial installation and configuration on my device, simply erased all the config items I set previously. It was like I just re-installed the plugin from scratch.
Interpretation
My understanding is that, locally, on any other device than mine, when Obsidian is launched and detects that their is a new plugin, the plugin is being installed and all the config items are lost and back to their original value.
Questions
Is there a way, now or in the future, to prevent this ?
Could all these configuration items be stored differently in order to not lose them in such a case of multiple users on a shared vault ?
Beta Was this translation helpful? Give feedback.
All reactions