Problem with the Auth groups

Hello Guys,

i have realized if i add and rename auth groups in the auth modul, it doesnt change the auth groups in the enum i can see in the database section.


if i add a new group on the enum in database area it doenst add a new row, instead it seems to try to override the existing options:

eventhough in front end most elements are using the choice of options i entered in the auth modul, i dont get the new options as an output from the database. e.g. if i say i have the standard options in auth: “user” and “admin” ( everything works fine with only those two) and i add a new option like “new auth” and implement a business process that should prove the auth group and navigate to site A if user is “new auth” and to side B if user is “admin”, it wont work with “new auth”, so i never get to side A. can you confirm this or is it jut on my side?

Hey @Marcel
We got several reports about user groups issue.

About 4 months ago we’ve released a new DB designer with real-time collaboration, moved all enums to DB schema and made them globally usable.

With that change, we temporarily hooked Auth Module User Groups (enum) changes from module UI to DB schema under the hood: module settings change
User Groups enum in DB schema and it looks like we have some issues now with that mechanism.

Our team is investigating this issue with high priority.

@leryq_it please expedite

@Marcel Hello, the issue solved.
We recommend recreating the problematic user groups and manually modifying the records in the database where they were used.
P.S. Remember to push changes in Database after adding new groups