Unfortunately my use case is one file - one thing. So In would need to create many things. This creates two issues for me:
1 I can’t know upfront many files a user will upload;
2 I don’t know where to indicate the things since there is only room to specify one
I have spent some time to understand who privacy works and I have eventually made it work.
However I wanted to point your attention to a potential issue in the Data Privacy section. This is what happens in my sample app (just one page to demonstrate the behaviour).
Click on the leftmost Image Uploader button and upload an image
You should see a blank image placeholder
Click on Save Image
Goto the Data Privacy section and delete the “administrator” role for the “ImageFile” data type
Go back to the app and upload an image
Now you should see the uploaded image as well as the previously uploaded image
Images for steps above
Step 4 - blank image
Step 5 - saved image (in app fileupload folder, not in appforest)
Step 6 - delete administrator role
after deletion of administrator role:
Step 8 - image is now displaying - also previously uploaded image
So it looks like that the privacy manager ignores the second role attribution and after evaluating “administrator” to false, it defaults to “everyone” which hasn’t got the permissions.
I expected “creator” role to be evaluated as the most permissive, granting access to attached files.
Could you please help understand how the privacy managers evaluates those expressions?
Can you create one situation where we don’t need to modify the app to the issue? Basically what we want is an app where you say “the user shouldn’t be able to see this and he can see this”
At step 4 the user should be able to see the uploaded picture, a white area (see Step 4 - blank image above), replacing the initial “click to upload…” thumbnail, is displayed instead of the uploaded picture.