Wrong avatar flair icon showing

I just created a new group in Humane Tech Community forum with a ‘humanetech-translators’ title and set a fa-globe flair icon. To ensure it showed up for all members I selected “Automatically set as primary group”. I gave members a default trust level of 2.

Due to this my own flair icon changed to the globe icon. I am also part of the ‘community-team’ group, and want this flair icon to be shown on my avatar (the fa-chess-knight icon). I.e. this group should have precedence to the translators group.

In my profile settings the default title was set to ‘community-team’ before creating the new group and the group itself also had “Automatically set as primary group” enabled from the start. The ‘community-team’ group does not have a default trust level setting.

Given that the globe was still shown, in my profile I changed title to None, saved, and then set it to ‘community-team’ once more, and saved again. But still I have the globe icon, while the title shows as ‘community-team’ on my profile card.

Besides me there’s one other member in ‘community-team’ that has the same issue too.


Two members in the ‘community-team’ group:

discourse-wrong-group-flair-icon

My profile card:

discourse-wrong-group-flair-icon2

2 Likes

Hi Arnold,

I think there is a confusion between “group most recently joined” (which is supposed to work), and “group with flair enabled first or last” (which is not), and also between the profile title and the primary group on the user’s admin page (just below the list of groups of the user).

3 Likes

Thank you @Benjamin_D!

Yes, this is a confusing interaction of features to me. I even had to very carefully read your 3 lines of text to understand this, and I could not find anywhere a “group with flair enabled first or last” you mentioned.

So summarizing as I understand it now:

  • Flair icon and title shown next to the avatar are 2 totally independent things.
  • To synchronise flair and title when user selected primary groups is disabled, I would have to adopt a new administrative task and carefully check each member upon group creation, and also when new members join the group (it is open access). The task involves going to the admin page of each affected user and override the primary group.
  • To synchronise flair and title when user selected primary groups is enabled would require me to either instruct members to synchronise 2 both the title setting in their account settings as well as the primary group setting (which is unwieldy), or be content that they just may not be in sync (which in practice this’ll boil down to).

I was expecting ‘group flair’ to change according to user account ‘group title’ setting. Isn’t that the most intuitive way for this to work?

PS: Thanks to your help I fixed this for me and the other member. I wait a bit marking ‘solution’ to discuss intuitiveness of this confusing functionality.

1 Like

sorry about that, it’s only me, I thought it was the behavior you were expecting :sweat_smile: .
about title vs primary group, it seems they are of different nature the first one is meant to be anything (when set by an admin) where the second is a group name. I’m not quite sure of the underlying rationale though :thinking:

2 Likes

Thanks. Maybe @tshenry who wrote the topic you referred to, or someone else on the team might shed a light on that.

2 Likes

I should start by saying we are actively discussing ways to improve the primary group concept, so there may be changes in the not too distant future.

While I wasn’t a part of creating the title and group flair features, I can give an example of why having the two features independent of each other can be helpful, as well as clarify how they currently work.

Let’s say a site has a “Team” group that consists of everyone in the company. It’s helpful to know a user is a part of the team at a glance, so they set up group avatar flair for the “Team” group and make sure all members have the “Team” group set as their primary group to ensure the flair displays.

Team members are broken into different roles - let’s say support and engineering - and are members of corresponding groups. In addition to knowing that a user is part of the overall team, it would also helpful to know what role they have. Given that the site wants everyone on the team to share the same “Team” avatar flair, they can specify a default title in their “Support” and “Engineering” user groups. The end result would look something like this:

I’m not sure if that the best example, but it’s one workflow a site could use.

There are definitely some nuances to both the “Automatically set as primary group” and “Default title” group preferences.

Primary Group

  1. If when creating a new group, the “Automatically set as primary group” option is checked, all members will have their primary group set/overwritten upon the new group’s creation
  2. If you go into an existing group’s settings and check/save “Automatically set as primary group” for the first time, all members will have their primary group set/overwritten with the new group
  3. If users are members of multiple groups that are set to “Automatically set as primary group”, you can go into the settings of one of them uncheck/save then recheck/save to set/override the primary group for all members.

Default Title

  1. Unlike the automatic primary group functionality, the default group titles are only applied to group members that do not have an existing title
  2. Removing a default title from a group will clear it from users that had it set as their title

So given all of the above, the order you add users to specific groups can be very important. It gets tricky if you don’t have control over the order a user joins groups, but you may be able to work something out knowing the behavior outlined above.

If there is a specific workflow you can’t achieve and would like to see supported, feel free to create a feature topic so we can keep it under consideration.

6 Likes

Thanks a lot for taking the time to craft this elaborate explanation @tshenry, really appreciated! For me the issue is currently fixed, and your explanation brings clarity on the mechanism. I’ll mark it as the solution :pray:

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.