The second sheet is good, but you shouldn’t need to create another tab if you want to stay with the original design. Keep the sheet, but remove the tab. Read through all of this first. Looks like you went down a different path. You should be able to stick with your original design plan with only a couple of minor changes to make it work. But let’s stick with the app flow you want.
The next problem is that it appears you haven’t enabled Row Owners on the email column. So changing who you view as will have no effect on which row is visible to the user.
Of the two methods I mentioned in my previous post, the first one is less secure since it does not use row owners. The second one that does use row owners is more secure. Row owners determines what data is sent to a user’s device. Otherwise all data is sent to a user’s device, regardless if they can visibly see it or not within the app. (Thus Row Owners is a more secure method).
How you want your app to flow is up to you. A separate tab will work if you set a filter on the tab to filter by signed in user or you set Row Owners on the sheet.
If you want to to stick with your original app flow, and keep the links secure, then I would follow the last paragraph in my previous post and set row owners on the Photos sheet and then create a single value column in your Items sheet that pulls that link into your items sheet (confused now because your new screenshot doesn’t show all the sheets/tables that you showed in your previous post). The goal is to get a unique photo url in the items sheet that changes dynamically based on the signed in user.
Oh, and like @ThinhDinh originally mentioned. Can you explain why you are using a user specific column for the link? You already have a unique row for each user, so there is no need to create a column that is designed to hold several unique values for several different users in the same cell. The way you are trying to use it will actually complicate things because that url may become tied to your account (since you are the one adding the links), but would be empty for everybody else (even though row owners would allow them access to the row). You don’t need a user specific column in this case, because you have a unique row for each user. Make a new basic column to hold the url. If multiple users shared a row and were able to make changes to that row at the same time, while remaining a unique experience for each user, only then does it make sense to use user specific columns.
Now I’m not sure off the top of my head if the Row Owner/Single Value method will work correctly in the glide editor, but it will work for sure in the published app. It may work everywhere, but if it doesn’t, then let me know.