Skip to content

Update Enterprise badge applies to SAML as well

Daphne Kua requested to merge docs-dkua1-enterprise-badge-saml into master

What does this MR do?

This Docs MR is a small modification to when Enterprise badge gets applied to users - to be for both SAML and SCIM provisioned users.

As part of the Enterprise Users epic, the MR writes Adds an "Enterprise" badge to group members that were provisioned via SAML/SCIM., but in the current docs, only SCIM provisioning gets the Enterprise badge.

I think this is the relevant section in the code:

A customer (internal ZD ticket) with no SCIM setup has users with Enterprise badge next to some users.

Related issues

Author's checklist

If you are only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.

Merge request reports

Loading