4 ms·
Has anyone defined or experienced a good workflow and process for multi-user, selective access/partitioned org-roam notes? Imagine I’m on a team of five and ea
by sokoloff 5y ago
Has anyone defined or experienced a good workflow and process for multi-user, selective access/partitioned org-roam notes?
Imagine I’m on a team of five and each of us have information that we consider public, private, company, and company/private. The last two being info that should stay with the company and not with me when I leave, and information that should stay with the company and with me when I leave (perhaps research or best practices we adopted in our use of language Foo or technology Bar [“how we integrate CUDA” or “rules for smooth DB migrations”], where it’s not company proprietary but the company should have continued access.)
I can easily see how I could use org to organize my own information, but if I use it to create a silo of information that only I can access and that, from the company perspective, dies with me when I resign, that feels selfishly sub-optimal.
(Perhaps “public” and “company/private” are the same category in effect, but user1’s private and user2’s private are definitely different. I’d be willing to take any reasonable restriction such as segregation must be on a per-file basis.)
- nanna 5y agoThink multi-user org-roam publishing is what the folk around anagora.org are doing. https://anagora.org/ https://anagora.org/
- bloopernova 5y agoAs far as I can tell, there's no multi-user features in org-roam. It uses a SQLite database to keep track of files and UUIDs, so multiple user access is going to be difficult.
- sokoloff 5y agoAh right. I didn’t say it (my bad) but was considering relying on the property that the “SQLite DB contents can be regenerated from the files” (in this case on a periodic basis or in conjunction with a git operation to push or pull new data).