Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Forum response workflow


New posts to the GitLab forum are brought in to Zendesk and #gitlab-forum on Slack.

The best place to engage on the forum as a Community Advocate, or anyone representing GitLab, is directly in the forum platform.

Best practices


Most administration tasks will be done from the Discourse Admin Dashboard

How to grant admin permissions

If you need to add an admin:

  1. Go to the list of forum users
  2. Use the search box to find the user you want to grant admin permissions to
  3. Click on the user to modify their profile
  4. Scroll down to the Permissions section
  5. Click on the Grant Admin button
  6. An e-mail confirmation will be sent to the Admin that granted the permission (i.e. you). Go to your inbox and click on the link to confirm granting Admin permission to the user
  7. If all went well, the Permissions > Admin? section on the user's profile admin should read Yes


How to respond to the GitLab forum tickets:

  1. Review the tickets in Zendesk GitLab Forum view
  2. See if all comments have received responses
  3. Write the response if appropriate, involve an expert for assistance if you don't know the answer
  4. Post the comment on the original website (, not Zendesk) using the link provided in the ticket
  5. Solve the ticket with the Replied macro (Replied macro will use the public response field in order to track the first reply time)

Whether you work through forum posts via Zendesk, or the forum platform, consider using some of the following resources to help get answers to questions:

Follow the relevant workflow depending on the question:

graph TD A((Non-support)) --> B B(Account) --> |Sales/Renewal| E[ping #sales] B --> |Other|F(Have they opened a support ticket?) F --> |Yes, using| G[ping #support_gitlab-com] F --> |Yes, self-managed| H[ping #support_self-managed] F --> |No| I[Direct them to] A --> J(GitLab vs Competitor) J --> |Question|K[Find answer via devops tools page/blog and link] J --> |Discussion|L[Link on #competition] A --> M(Feature Proposal) M --> |Already exists|N[Link to the open issue] M --> |Doesn't exist|O[Ask them to open an issue]
graph TD A((Support)) --> B(What level of GitLab are they on?) B --> |Not free|C(Have they opened a support ticket?) C -->|No| E[Link them to the support portal] C -->|Yes| F(Have they provided the ticket number?) F --> |No|R(Ask them for the ticket number) R --> F F --> |Yes|G(Self-hosted or .com?) G --> |Self-hosted|H[ping #support_self-managed] G --> |.com|I[ping #support_gitlab-com] G --> |not provided|J(Ask what they're using) J --> G B-->|Free| D(Is there an issue open already?) D --> |Yes|K[Link the issue] D --> |ask the following questions|L(Self-hosted or .com?) L --> M(What version are they on?) M --> N(Has this happened on a previous version?) N --> O(How long have they been experiencing it?) O --> P(What integrations do they have, if relevant?) P --> |Questions answered|Q[ping relevant product channel]

GitLab Forum Strategy

Engagement drives engagment, so the more the GitLab team engages with our wider community, the more they are likely to engage with us, and with others. By setting the example of providing thorough answers, we can build our forum up as a place of knowledge share and collaboration. See the Forum's 2020 strategy slide deck for more.


New mentions are brought into Slack and Zendesk via Zapier.