In the entity manager I set 2 to a user group so that a user can add maximum 2 instances.
I tried it. Unfortunately a user of this group can add more than 2 instances. What else I have to configure to get it work, so that a user cannot add more than 2 instances (items)?

Hello

Unfortunately a user of this group can add more than 2 instances
Please check, now in our Joomla Website builder, the user may add so many instances as he want.
BUT, published - will only so many Instances - as many Admin set in settings.

This create for not lost data from user

If this not work, please show how we may reproduce this.

Regards
OrdaSoft team

In my opinion it is better that the user can add only the amount of instances which he has bought in his subscription.
If the published instances are related to the bought subscriptions it might be confusing for the user. He might add 10 instances but only 2 get shown. Makes no sence.
On the other side, if the instances first have to be reviewed by the site admin before publishing, how the admin can know how many instances the user has already published and how many he is allowed to publish. He can find it out of course. But it is a lot of work,

I think the first idea of Ordasoft was to restrict the amount of instances that can be added as I can see from the information field of the entity (see photo). Otherwise the text should be changed.

Hello. We've fixed the ability to automatically publish for instances added via the frontend. Now if the value specified in these settings is not exceeded and the option to automatically publish to one or another group is enabled in the add-layout, the instance will be published immediately. We understand that the super admin should not suffer from such restrictions, so if you decide to manually publish an instance in the admin panel, then if you exceed the quota of published material you will get a warning and you can decide to publish or not.

Translated with www.DeepL.com/Translator (free version)

This is great. Thank you very much.

I found a bug. The only thing which I have figured out: If I open the unpublished instance as backend administrator to check the instance and afterwards click the save and close button, then the instance gets automaticly published. One should keep this in mind as an administrtor