You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Neckaralb-Project will work several scientist on their thesis/work and will create data for the bigger and perhaps one day public project. But until their thesis is finished or at least the data is in a state of "it could go public", their data should be protected from other users. This could prevent unwanted changes of own data from other people. People perhaps feel more comfortable if their data is not (yet) visible to a wider range of people who are not closely related to their very own project (thesis or whatever).
Feature request
In multi-user environments i would be useful if users or groups could have permissions to view and/or edit data of their part of the project but could not view/edit the data of another part of the same project.
What do you think about this?
How could it be implemented?
The text was updated successfully, but these errors were encountered:
If I remember correctly, we already talked about it on the phone?
Unfortunately, we haven't made any progress in this. If you're still interested in this, it would be great if we could meet up to discuss a workflow (and possible implementation)?
Hey @DavidKi
I started working on a group feature (additional to permissions and roles) to restrict access to specific entities/files/geodata to groups and either don't allow access at all, only allow read access or full (read & write) access.
I'd like to hear your feedback on this. You can check out the group-restrictions branch in an existing or new database or I can setup a testing instance for you?
I can also give you instructions on how to setup grouns and restrict access and how it works in general.
Allow advanced settings for user privileges
Use case/background
In the Neckaralb-Project will work several scientist on their thesis/work and will create data for the bigger and perhaps one day public project. But until their thesis is finished or at least the data is in a state of "it could go public", their data should be protected from other users. This could prevent unwanted changes of own data from other people. People perhaps feel more comfortable if their data is not (yet) visible to a wider range of people who are not closely related to their very own project (thesis or whatever).
Feature request
In multi-user environments i would be useful if users or groups could have permissions to view and/or edit data of their part of the project but could not view/edit the data of another part of the same project.
The text was updated successfully, but these errors were encountered: