Support Portal

Account Management

Creating a support portal account

NOTE If you have filed a ticket without signing into a support portal account previously or another associated contact had requested you be added to your organization, an account was already created for you. You will need to reset your password first to be able to login. See reset your password for more details.


To create a support portal account, you can do it one of three ways:

  1. Submit a ticket without logging into the support portal. Doing so will result in an account being automatically created for you. You will need to reset your password first to be able to login if your account is created in this way. See reset your password for more details.

  2. Have an associated contact request you be added to your organization (via a Support Operations ticket). This will result in an account being automatically created for you. You will need to reset your password first to be able to login if your account is created in this way. See reset your password for more details.

  3. Manually create the account. You do this by:

    1. Navigate to the support portal
    2. Click the Sign in button at the top right of the page
    3. Click the Sign up link towards the bottom left of the page.
    4. Enter your full name and email address, then click the blue Sign up button.

If doing this manually (option 3 from above), there are a few results that can occur:

  • An account already exists with the email you tried to use. In this case, a password reset email is sent to the account's email address.
  • A new account is created for you. An email will be sent to your account's email for setting up your password and confirming your accounts' email.

Both results will appear the exact same on the portal, so you will need to check your account's email to be sure which result occurred.

Logging into your support portal account

  1. Navigate to the support portal
  2. Click the Sign in button at the top right of the page
  3. Determine the method to use for signing in:
    • If you have filed a ticket without signing into a support portal account previously or another associated contact had requested you be added to your organization, an account was already created for you. You will need to reset your password first to be able to login. See reset your password for more details.
    • If you have a Google or Twitter account using the same email as your support portal account, you can click the corresponding Oauth button on the left side.
    • Otherwise, you'd enter the email and password for your account on the right side login box and then click the blue Sign in button.

Logging out of your support portal account

  1. Navigate to the support portal
  2. Sign in to your account.
  3. Click your profile link in the top right of the page (shows your profile picture and account name).
  4. Click the Sign out link

Reset your password

To reset your support portal account's password:

  1. Navigate to the support portal
  2. Click the Sign in button at the top right of the page
  3. Click the Forgot password? link on the right side of the page (below the Email/Password input boxes)
  4. Enter your support portal account's email address and click the blue Submit button.

This will send password reset instructions to your email inbox.

Change your password

To change the email used for your support portal account:

  1. Navigate to the support portal
  2. Sign in to your account.
  3. Click your profile link in the top right of the page (shows your profile picture and account name).
  4. Click the Change password link (some browsers may not show it as a link). This will cause a modal to popup showing your profile information.
  5. Enter the password you used to login under Current password.
  6. Enter your the new password you wish to use under New password.
  7. Re-enter your the new password you wish to use under Confirm password.
  8. Click the black Save button. (NOTE this will sign you out of the account).

An alternative to doing this is using the information within Reset your password, which will accomplish the same end-result.

Change your name

To change the name used for your support portal account:

  1. Navigate to the support portal
  2. Sign in to your account.
  3. Click your profile link in the top right of the page (shows your profile picture and account name).
  4. Click the Profile link (some browsers may not show it as a link). This will cause a modal to popup showing your profile information.
  5. Change the name showing in the modal and click the black OK button.

Change your profile picture

To change the profile picture used for your support portal account:

  1. Navigate to the support portal
  2. Sign in to your account.
  3. Click your profile link in the top right of the page (shows your profile picture and account name).
  4. Click the Profile link (some browsers may not show it as a link). This will cause a modal to popup showing your profile information.
  5. Click the Change photo button (below the Name input box). This will open the file browser your for browser, allowing you to select an image file to use for your profile picture.
  6. Wait for the image to render on the preview bubble (to the left of the Change photo button).
  7. Click the black OK button.

Change your email

NOTE Changing your email might result in you being de-associated from your organization depending on your organization's setup. You should speak with your organization to ensure that changing your email is acceptable and will not cause issues.


To change the email used for your support portal account:

  1. Navigate to the support portal
  2. Sign in to your account.
  3. Click your profile link in the top right of the page (shows your profile picture and account name).
  4. Click the Profile link (some browsers may not show it as a link). This will cause a modal to popup showing your profile information.
  5. Change the email showing in the modal and click the black OK button.

This will only work if the new email is available for use. If another account is using the new email address, you will see an error message of This email address is already in use by another profile. after clicking the black OK button.

If you wish to add a secondary email address to the support portal, please open a ticket using Support Portal Related Matters as the reason you're reaching out. Adding a secondary email will help us identify you in the event that you open a ticket with an alternate email address. It's important to be aware that email notifications from tickets will always go to your primary email only.

Ticket management

Creating a ticket

NOTE This requires using the support portal to do. We do not accept tickets created via email, with the exception of billing, account receivable, and emergency emails.

To create a ticket via the support portal, you will want to navigate to the Submit a ticket page. The location of the button for this can be found in multiple locations:

  • At the top right on all support portal pages
  • Below the search bar on the main page
  • As one of the 6 block items on the main page (the 6th one on the bottom-right)

This page will then ask you to choose the reason you are reaching our to us. The answer on this question will determine the form that is used for your ticket submission, which will be used to route your ticket to the correct team.

This is a brief overview of the options and what they mean:

Form Team What it is for
Support for GitLab.com Support Technical support tickets for customers using GitLab.com (not relating to user account specific issues)
GitLab.com user accounts and login issues Support Technical support tickets for customers using GitLab.com relating to user account specific issues
Support for a self-managed GitLab instance Support Technical support tickets for customers using self-managed instances
Support for GitLab Dedicated instances Support Technical support tickets for customers using GitLab Dedicated
Subscription, License or Customers Portal Problems Support For matters relating to Customers Portal, subscriptions, license issues, credit card errors, etc.
Billing inquiries/refunds Billing For matters relating to refunds, invoices, etc.
Support for alliance partners Support For Alliance partners to file technical tickets
Support portal related matters Support Operations For issues relating to ticket management, contact management, support portal usage, etc.

On each form, you will want to fill out as much information as is possible. The more detailed and thorough of a description given to the various GitLab teams, the quicker and more efficient the ticket will be resolved.

NOTE If you are logged into the support portal, you can add a CC on your ticket at the time of submission. The option will not be available if you not signed into the support portal.

Creating emergency tickets

To create an emergency ticket, please use the emergency request form.

Viewing your tickets

NOTE This requires logging into the support portal to do.

To view your tickets:

  1. Sign in to your account.
  2. Click your profile link in the top right of the page (shows your profile picture and account name).
  3. Click the Requests link

This will bring up a list of your requests. You can also just use the Requests link to get to the same page.

Filtering your tickets

You can use various filters to limit the number of tickets showing. This is done by using the search bar or dropdown menu (to the right of the searchbar).

Some common filters you might find useful:

Viewing tickets you are CC'd on

NOTE This requires logging into the support portal to do.


  1. Sign in to your account.
  2. Click your profile link in the top right of the page (shows your profile picture and account name).
  3. Click the Requests link
  4. Click the Requests I'm CC'd on link

This will bring up a list of your requests you are CC'd on. You can also just use the Requests I'm CC'd on link to get to the same page.

Viewing your organization's tickets

NOTE This requires logging into the support portal to do. It also requires a shared organization has been setup for your organization. If that has not been done, the link will not appear in the support portal.


  1. Sign in to your account.
  2. Click your profile link in the top right of the page (shows your profile picture and account name).
  3. Click the Requests link
  4. Click the Organization requests link

This will bring up a list of your requests you are CC'd on. You can also just use the Organization requests link to get to the same page.

Getting notified about your organization's tickets

If you wish to be notified about your organization's tickets (and your organization has a shared organization setup, you can click the Follow button to the right of the search bar on the Organization requests page.

To turn this off, simple click the Unfollow button to the right of the search bar on the Organization requests page.

Updating a ticket

NOTE The support portal displays the first comment of the ticket at the top of the page, and the most recent comment at the bottom of the page.


There are currently two ways to update a non-closed ticket:

  • Via email
  • This is done by replying to the latest notification email you received for the ticket.
  • Via the support portal
  • This is done by navigating to the ticket in question via the support portal, going to the very bottom of the page, clicking the Add to conversation field, typing out your response, and then clicking the Submit button.

Adding additional participants (CCs) to your ticket

NOTE This requires logging into the support portal to do. It cannot be done via email. Requests to add additional participants made through the ticket interaction will not be actioned on.

When updating a ticket, you can add additional participants (CCs) on your ticket. This will ensure the CC'd person gets update notifications for the ticket (and can also reply on said ticket).

To do this, you will have to post an update on the ticket itself (meaning a comment must be made). Right above the comment text box is the CC box, which will allow you to type out email addresses to be CC'd on the ticket. To enter the email, the system waits for a space delimeter. So add the emails of [email protected], [email protected], and [email protected], you would enter

[email protected] [email protected] [email protected]

into the field. You can remove an email before you submit the update by clicking the x to the right of the email address.

Once a CC is added, it cannot be removed via the support portal. You will need to make a comment on the ticket requesting the GitLab agent completely remove the email as a CC on the ticket.

Creating a follow-up ticket

NOTE This requires logging into the support portal to do.

To create a follow-up ticket for a previously solved/closed ticket, navigate to the ticket in question, scroll to the last comment on the ticket, and click the create a follow-up link. This will send you to the ticket creation page, copying over the fields from the original ticket. It will also pre-populate the ticket's description with a message about it being a follow-up to the original ticket.

Solving a ticket

NOTE This requires logging into the support portal to do.

In very specific situations, you are able to mark your ticket as solved. To be able to do this:

  • The ticket must be assigned to a GitLab Agent
  • The ticket's type may not be problem
  • You must be the requester on the ticket (i.e. you cannot mark other members of your organization's tickets as solved).

If all of these criteria are hit, you can mark the ticket as solved. To do this:

  1. Navigate the to ticket in question
  2. Go to the bottom of the page for your ticket
  3. Click the white Mark as solved button

If you wish to mark the ticket as solved and update the ticket with a reply, you would type out your reply in the text box (bottom of the ticket) and then click the white Mark as solved & Submit button.

Information on ticket flow

When it comes to the flow of your ticket, there are some things to keep in mind.

We use auto-responders for efficiency

Where possible, for the sake of efficiency, we use auto-responders from a bot account we control. The goal of these is to try to solve common issues that can be easily solved with a quick reply.

We utilize these to help ensure the fastest resolution to your tickets whenever possible.

We automatically modify the ticket status based on unresponsiveness timelines

To ensure tickets do not stay in a pending (awaiting your response) forever, we have setup automated triggers to change the status based on unresponsiveness timelines:

  • If a ticket is pending (awaiting your response) for 7 days, a reminder notification is sent on your ticket reminding you of the current state of the ticket.
  • If a ticket is pending (awaiting your response) for 14 days, we change the ticket's status to solved (and send out a notification email). At this point, you can still update the ticket to get it moved out of the solved state.
  • If a ticket is in a solved state for 7 days, we automatically close the ticket. At this point, the ticket can no longer be updated. The only way to resume a conversation about the ticket is to create a follow-up ticket.

Ticket responses can be in other languages

Ticket support is available in the following languages:

  • Chinese (Simplified)
  • English
  • French
  • German
  • Japanese
  • Korean
  • Portuguese
  • Spanish
  • Italian

While we do not currently provide translated interfaces for our Support Portal, you can write in your preferred language and we will respond accordingly.

Should you be offered a call, only English is available.

NOTE: Any attached media used for ticket resolution must be sent in English.

Troubleshooting support portal issues

Occasionally, you may find the Support Portal not acting as expected. This is often caused by the user’s setup. When encountering this, we recommended the following course of action:

  1. Ensure your browser is allowing third party cookies. These are often vital for the system to work. A general list to allow would be:
  • [*.]zendesk.com
  • [*.]zdassets.com
  • [*.]gitlab.com
  1. Disable all plugins/extensions/addons on the browser.
  2. Disable any themes on the browser.
  3. Clear all cookies and cache on the browser.
  4. Try logging in again to the the Support Portal.
  5. If you are still having issues, obtain the following:
  • the browser’s version
  • the browser's type
  • your operating system (and distro)
  • any other identifying information
  • the complete contents of your Javascript console for your browser
  1. Send all of that to support. If you are unable to create a ticket, then communicate with your Account Manager. The next best place to send the information is via a GitLab.com issue.
On this page
Account management
Ticket management
Information on ticket flow
Troubleshooting support portal issues