Improve Service Desk Documentation

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Reorganization

• Add a setup/configuration sub-page !127828 (merged)
• Add a using service desk sub-page !127828 (merged)
• Add a security & privacy sub-page (create when there's content for it)
• Add content for general information/introduction

Additions

• Default Email Address
• Diagram for how incoming email/email alias/custom emails work
• Service Desk best/recommended practices
  • Use internal comments to write notes that are not sent as emails (this isn't mentioned anywhere in the docs)
  • Use gitlab-triage for automatic triaging - see gitlab-org/monitor/respond#262 (closed)

Guidance

• Start small and add one page per MR.
• Make use of templates in CTRT topic types, most relevant Concept (for WHAT) and Task for HOW.
• In introductions and concept topics, don't be too marketingy/salesy 😉
• After a page is created, it needs to be added in a separate MR to the navigation: https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/content/_data/navigation.yaml