I think it is specific to the application and what the application does and who its users are.
For example, an application used by retailers that allows multiple users per location, so a manager and a clerk. These two may both need to view certain data, while only one should have rights to manipulate the data. Setting up privacy rules based on the users role in an organization is one use case. It would be up to the developer to decide how to implement them.
One thing I am planning on doing is providing the main user (the one who creates the first account and then signs up other users) to be able to select permissions for each user they sign up. These permissions will be used in the privacy rules.
There are so many different possibilities that it is difficult to give a one sizes fits all type of answer.
However, one thing that you could consider for every application, is that any data the user is sharing with the application and is stored in the database but is not meant to be displayed to other users of the application, this data should get privacy rules…maybe things like mailing addresses or contact details.
1 Like