Open markhughes opened 3 years ago
Similar request:
At work we really need different view permissions for various roles (user groups). But since implementing something like that is quite hard, we just setup two independent instances of Droppy instead, one accessible to all employees, while the other is only for board members and such.
Hey @Tronic do you just have one instance set to read-only and the other not? Would be curious to hear how fine-tuned you would prefer your permissions.
In our system everyone has full write permissions, and we have automatic snapshots on btrfs in case of accidental deletions. The only real concern is that some documents must be kept confidential, and ideally those could be stored on the same customer folder where other public documents are also stored.
@markhughes Btw, I really appreciate the work you are doing with droppyjs. Give me your Bitcoin address and I'll send a tip! :)
Thanks! Really insightful.
Would be nice to integrate it with federated/SSO systems (like GSuite, auth0, onelogin, office 365, etc) as well which might help better with managing groups inside an organisation
@markhughes Now we actually need (self hosted) SSO support. It is not awfully urgent but I definitely second that goal.
@Tronic I'm rewriting a huge chunk at the moment to allow for this stuff :)
Create user roles, something like so: