On Admin -> user accouns -> module settings, you can configure the columns that will be displayed.
These settings are saved for the current portal.
If you save the settings on host -> user accounts, you are effectively changing the settings of the active portal.
But the settings are not used on the display view while on Host -> User accounts.
go to host -> user accounts -> module settings and show / hide some columns
on the view you expect to see the configuration you just applied.
But the configuration is not used.
Lorrain. I would not document the setting change yet and wait for it to be completely fixed in 7.3.4. Changing the docs for just a single maintenance release will only add to the confusion. We know that there is a bug here (albeit, a different bug than the one originally being addressed). This fix just highlighted that there is a bigger underlying issue and I would rather we document the correct behavior when that actually works the way we want, rather than document what we know is buggy behavior.
Please don't troll the Jira comments. You are not adding value or helping to clarify this issue.
IMO this is a totally useless discussion. It would be better to combine all User Management into a single module instance with an option for superusers (vs. portal users) - this will eliminate duplicate module settings. Note: any duplicate menu items are just irritating novice users.
For best performance and integrity, Superusers should be member of each site, i.e. get a UserPortal record for each existing Portal and a user profile (for convenience, default profile properties might get synced across all sites, which would be a nice option for all users). The current Situation, where just around 30% of all superusers in all installations are having a userportal record, is just hard to deal with and has absolutely no benefit.
The initial description is not clear to me, and the fixes for this issue are not fully completed.
As a conclusion of current behavior in 7.3.3
The User Account Settings change happened through "Admin > User Accounts" page will impact "Host > SuperUser Counts" as well, and vice versa.
The proper behavior will rely on Joe's input and decision in the future release, but I expected those 2 different pages shall have 2 separated module instances, shall not impact each other.
close the issue as it is.
Each module instance should store Display Settings in ModuleSettings table.
Portal Settings might be stored in PortalSettings table, but not for module instance on Host pages, which should store settings (if necessary) in Host Settings table. IMO we need to get rid of any user properties etc. for superusers - they should get userPortal records for each portal and any PortalSetting with PortalID = Null should be considered as Default value.