Task List table has row owners for various Roles. When a row is added (a new task is made), users can select which of the row owner columns get filled out, so some tasks are not visible to others. Seems to work great.
Many tasks are re-usable, so i have a “Task Assignment” table that connects user ID to a task ID. there is a relation column to pull data from the task table like Name/Details. This table has row owners for admin, management, and the email of the assigned user.
Issue Example
Task A is only “owned” by admin and management.
Task A is assigned to “Steve” who has the role “Employee”. Steve cannot see the Task A row in the task list table.
However, when Steve views the data from the row of the assigned task table, he can see the data pulled in from the Task List table that he doesn’t have access to.
Is this correct? If it is, can somebody help me understand the benefit of this?
I understand i can avoid this scenario through other means, but now im curious how it works. My understanding was it doesnt download any rows that are not owned by the user. But this seems to do so.
No, that doesn’t sound right at all.
Would you mind adding some screen shots of the tables mentioned? If I can see them, I may be able to spot what is wrong.
Your understanding is correct. If it is, that’s either a bug (unlikely), or something in your setup isn’t quite right (more likely).
Before i go and get screenshots, is it possible it only shows like this in the editor and wont when published?
I remember it was possible to assign roles to the user coloumn from within the “app” in the editor, but it didnt work when published (which it shouldnt)
Yes, absolutely. All rows will always be visible in the Data Editor, regardless of ownership.
However, any unowned rows should not be visible in the Layout Editor or the Published App.
It’s a bit hard to tell from the screen shot - but the important question is; is that row visible in the Layout Editor? If not, then I don’t think there is a problem.
