Huge image collection slows down the whole Joomla about jg4-dev

[AlexanderSupp]

I see no reason to define different permissions for individual images in a category. The regulations at the category level are completely sufficient. In my opinion, it also makes no sense to allow permission for different regulations in the configuration.
The "Own-" options can be used to regulate finer details.
Keep it stupid and simple.

[Elfangor93]

Another idea would be to create just one asset per category to handle permissions for all the images in the category.
This way we are able to select the permissions for the images independently of the permissions of the categories.

[MrMusic]

Another idea would be to create just one asset per category to handle permissions for all the images in the category.

Would the permissions tab then appear for every image?
I guess this would confuse the users because they would think the setting would be separate for each image.

What do you think?
Do we need ACL on image level?

I don't think we need ACL on image level. I currently have no 'use case' for this.

Do we wanna create a configuration to turn the creation of assets on or off?

Would this not make the code more complicated and slow down the performance?

[Elfangor93]

Would the permissions tab then appear for every image?

We could decide where we wanna show this. We could also add another tab in the category edit view. Something like Image Permissions.

[Tazzios]

And only create an asset record for the image if image authorization is NOT the same as the category/ an override has been set for the image.

I also do not see an use case for image ACL. For some special occasion maybe a few images, but if you use this option a lot i think you will lose oversight about who can see what image.