jacker sandstorm and hubzilla are different
Hubzilla is not suit your specific need.

Nextcloud or similar Web app are tailored for specific requirement

Great, you choosing foss

In reply to @jackboy:matrix.org
How Sandstorm and hubzilla are similar or different?

It will depend on your editing workflow whether Hubzilla is an option or not. If your team needs simultaneous editing of the same document, then, Hubzilla isn't currently a contender. If you are simply looking for shared or access controlled storage and non-simultaneous edits, it is a possibility.

NextCloud is also a possibility.

Though, it will really greatly depend on workflow.

Also, Hubzilla will allow you to have a local/cloned copy of your shared repository for faster access with files synchronized among the regional offices. I don't think NextCloud would offer this.

I haven't played with multiuser active file storage as much as I would have liked at this point. The one caveat I can see is that if the nodes are not constantly connected so that application lockfiles are constantly synchronized, it may be possible to lose some edits if two people are working on the same docs at the same time.

Hubzilla would also allow each regional office user to store their files on a more local node also - again - meaning less network traffic.

Also with Hubzilla, even though there would be multiple nodes, you would have single-signon - each user would have one set of credentials for the entire network - but it would still be possible to enforce access controls down to a user-by-user basis.

So, like with most things, it depends very much on your use case and workflow. Hubzilla may be a good option, but there may also be options that integrate better with your culture and workflow.

In reply to @andrew:matrix.reticu.li
A serverless option that I also recommend, which might fit your needs, is Syncthing. Basically, Syncthing lets you share folders between devices without a central server. Each device sharing a folder contributes in a BitTorrent-like swarm to keep the devices is sync. It is very robust and has been working almost magically for me for years.

In reply to @dm42:matrix.org

It will depend on your editing workflow whether Hubzilla is an option or not. If your team needs simultaneous editing of the same document, then, Hubzilla isn't currently a contender. If you are simply looking for shared or access controlled storage and non-simultaneous edits, it is a possibility.

NextCloud is also a possibility.

Though, it will really greatly depend on workflow.

Also, Hubzilla will allow you to have a local/cloned copy of your shared repository for faster access with files synchronized among the regional offices. I don't think NextCloud would offer this.

I haven't played with multiuser active file storage as much as I would have liked at this point. The one caveat I can see is that if the nodes are not constantly connected so that application lockfiles are constantly synchronized, it may be possible to lose some edits if two people are working on the same docs at the same time.

Hubzilla would also allow each regional office user to store their files on a more local node also - again - meaning less network traffic.

Also with Hubzilla, even though there would be multiple nodes, you would have single-signon - each user would have one set of credentials for the entire network - but it would still be possible to enforce access controls down to a user-by-user basis.

So, like with most things, it depends very much on your use case and workflow. Hubzilla may be a good option, but there may also be options that integrate better with your culture and workflow.

En réponse à @pastor:netzgemeinde.eu
Ale: What has got Sting to to with it? :-D