Edit: The issue is that the default admin isn’t added to ‘staff’ or ‘admin’ groups initially despite showing as admin: yes in their profile.
Just tinkering with a new test instance and noticed that after enabling chat the default admin couldn’t see the speech bubble and chat/browse/open kicked them back to /latest.
I think I’ve seen something like this previously. Is it the addition of both staff and admins? Does removing one of those allow the admin to chat without bumping their trust level?
This is a fresh instance built by hand on DO this morning, I’m effectively testing the current out-of-box experience. They have automatic TL group memberships, no custom ones. Admin yes, moderator no - it’s the default admin on a new instance, so following the defaults.
It looks like the automatic groups aren’t being applied. I’ve just spun up another instance and the default admin only has trust levels, they don’t have ‘staff’ or ‘admin’. I can trigger those memberships by either making them a moderator, or creating another admin. I was tempted to leave the instance overnight to see whether a sidekiq job would address this, but it probably shouldn’t be in that state for the only admin on a fresh instance for any amount of time.
So it looks like the issue isn’t chat, as much as the memberships of the default admin on a fresh instance… Will rename this topic and remove the chat tag.
Is this a new issue? Are you suggesting that the new admin should be an admin and moderator? I wonder if this was a design decision long ago or a new change.
As regards chat, it seems to me like the admin user should be able to access all chat even if they are not listed in chat allowed groups, just like they can access everything else on the site.
As it happens, I was looking at the new user experience this week too and noticed that the groups page on a new site is potentially confusing for the first non-staff to show up. It’s bland, only the moderators group shows up on the list, and there are no members of the moderators group.
The default admin should be a member of the admins group and the staff group. On the instances I created today that wasn’t the case. Their only group memberships initially were TL0 and TL1, giving them TL4 solved the symptom I was observing with chat but not the root cause.
If I manually added them as a moderator they received the staff group membership. If I added another admin their memberships were corrected.
Though while I was there I went to /sidekiq and ran Jobs::EnsureDbConsistency and that did fill in the right automatic groups. Like @Stephen said earlier though, it should really be ready from start up.
I just merged a core fix for this, we likely didn’t notice this previously since less settings relied on these auto groups, but now we are generally heading in the direction of using group_list site settings so this should help:
This is the admin’s user page on a fresh install:
