Privacy Rules for Event Team Members data type

Need help Database
1

I have the following data types ( simplified )

I am trying to set up the privacy rules so that the team’s manager can see the subset fields of the user.

Requirements
the manager can see the team member’s details when their role is set to manager.
In all other instances (when their role is an ordinary user) they can only see their own user details.

Privacy Rules

  1. if you add event teams to the user, you cannot say
    this users event team manager because
    event team is a list and
    managers is a list on the event team

  2. You could add a list of maangers to the user and add the event team manager to the list but that would mean the manager would always see the users details.
    I would have to add a role restriction as well.

  3. What would be nice would be able to say on the event team member data type is
    this event team manager contains current user
    and giving access to the member (user) but this is not possible unless the privacy on the user is satisfied.

Since a player will play in many teams, at many events, tournaments, and courses their list of events and managers will grow quickly and go beyond the recommended 100 list maximum for best performance.

Maybe I need to look at this a different way to find a solution.

I would appreciate any guidance or suggestions

2

Hey, @paul.brown ,

The way I see, one possible solution for this is the following approach:

image
image737×740 20.8 KB

You replicate some fields from USER into EVENT_TEAM_MEMBERS (I’d recommend creating a database trigger to maintain everything synced), and create a field manager in this table too.

So you’ll set your privacy rules on EVENT_TEAM_MEMBERS instead of USER and the manager will see only what he can see.

3

Thanks for the suggestion.
I was thinking along these lines but was reluctant to replicate but maybe that is the best solution. Always good to get another opinion.

1 Like
4

Anytime!

Btw, my guess is that depending on the complexity of the rest of the app, you’ll actually be glad to have these fields replicated, so you don’t have to rely on the User table when setting up these specific privacy rules, because User privacy rules tend to get a bit messy :sweat_smile: