Auth expertise distribution across SGGs

After the SSG redistribution in #4903 and #4925 (closed), this is what it looks like:

Topic	SSG	Distribution
SAML + SSO	Baobab	Total: 5 AMER: 3 APAC: 0 EMEA: 2
	Ginkgo	Total: 4 AMER: 0 APAC: 0 EMEA: 4
	Kapok	Total: 3 AMER: 0 APAC: 3 EMEA: 0
	Maple	Total: 7 AMER: 1 APAC: 2 EMEA: 4
	Pine	Total: 5 AMER: 1 APAC: 2 EMEA: 2
SCIM	Baobab	Total: 3 AMER: 1 APAC: 0 EMEA: 2
	Ginkgo	Total: 3 AMER: 0 APAC: 0 EMEA: 3
	Kapok	Total: 2 AMER: 0 APAC: 2 EMEA: 0
	Maple	Total: 3 AMER: 1 APAC: 2 EMEA: 0
	Pine	Total: 3 AMER: 0 APAC: 1 EMEA: 2
LDAP	Baobab	Total: 4 AMER: 2 APAC: 1 EMEA: 1
	Ginkgo	Total: 1 AMER: 0 APAC: 0 EMEA: 1
	Kapok	Total: 1 AMER: 0 APAC: 1 EMEA: 0
	Maple	Total: 2 AMER: 0 APAC: 0 EMEA: 2
	Pine	Total: 5 AMER: 2 APAC: 3 EMEA: 0

Notes:

• All team members listed in SCIM are also listed in SAML + SSO.
• For the combination SAML + SSO, I manually went through the list of people for SAML and SSO for Groups.
• OmniAuth is not included because outside of SAML, it's not a common topic.

ZenDesk tickets

Doing a quick search in ZenDesk on the number of tickets where the subject mentions the topic. As of 2023-03-02:

Topic	1 month	3 months	6 months	1 year
SAML	110	216	378	705
SCIM	22	45	100	191
LDAP	39	83	140	285

Note: There is often overlap between SAML and SCIM.

Areas of possible concern

2. SCIM: Maple | Expertise list needed updating, see #4920 (comment 1295935049)
3. LDAP: Ginkgo | See #4920 (comment 1299458189)
4. LDAP: Kapok | See #4920 (comment 1299457108)

Less concern:

1. SAML: Kapok | See #4920 (comment 1299457108)
2. SCIM: Kapok | See #4920 (comment 1299457108)
3. LDAP: Maple | See #4920 (comment 1299453205)

Possible strategies

If SGGs are struggling in these topics, some possible things to do:

1. Have 1-2 team members complete the topical training module so that the group has at least 2 experts
2. Ensure the SGG team members know where to get help from experts when their own experts are unavailable
3. ???