GitLab University Panorama

What is a GitLab University Panorama?

GitLab University is free and open to all customers for self-serve learning. GitLab University Enterprise is a dedicated, managed portal included with the Signature Success Tier or available for separate purchase through Education Services. Internally, we refer to each customer-dedicated portal as a GitLab University Panorama. The course content is the same as the public catalog. The key differences are:

• SSO configuration for customer users (optional)
• Ability to exclude specific courses from the public catalog
• Custom content hosting alongside GitLab University materials
• Customer-specific reporting

Each Panorama is provisioned and managed by the GitLab University team, and must be requested via an issue (see workflow below).

Who can request a Panorama?

Any CX team member working with the customer can submit the request issue.

Who qualifies?

A Panorama is generally available in these cases:

• The customer has purchased the GitLab University Enterprise SKU
• The customer has purchased the Signature Success Tier, which includes GitLab University Enterprise / Panorama as part of the offering

If you are unsure whether the customer is entitled to GitLab University Enterprise / Panorama:

• Check Salesforce and/or
• Ask in the #digital-success Slack channel

If neither condition is true and you believe a Panorama is still appropriate, follow the workflow in the issue template below to capture a business justification and route for internal approval.

When to request a Panorama

Use a Panorama when an organization needs a dedicated, managed learning environment with SSO, custom content hosting, and customer-specific reporting, for example when:

• The customer wants a centralized learning environment for GitLab-related training, including the ability to host custom content (e.g., recorded workshops, CSM/CSA-created materials) alongside GitLab University courses
• The customer wants a single portal for their organization that can include both GitLab University content and their own custom content
• The customer wants to track GitLab University usage and certification voucher redemption centrally for their organization

Pre-requisite information to gather from the customer

Before opening a request, the requesting team member should gather:

1. Authentication preference
   • Do they want SSO login or site registration code?
   • Default: site registration code and customer account creation — simpler and faster, no IT dependency.
   • SSO:
     • Requires customer IT involvement
     • Customer must provide an IT contact name who can join a 30-minute configuration call with the GitLab University team
     • Capture which SSO provider they use (Okta, Microsoft Entra, other)
     • SSO scheduling can extend the overall setup timeline, depending on customer IT availability.
2. Learning focus areas (top 3) Examples:
   • Duo / AI-focused
   • CI/CD-focused
   • New-to-Git-focused
   • Ultimate / Security-focused
   • Other (describe any custom needs)
3. Certification vouchers
   • How many certification vouchers did the customer purchase (if any)?
   • Do you have the registration code(s)?
4. Customization preferences
   • Content exclusions: Any content from the public GitLab University catalog to be excluded?
   • Custom content uploads: Any customer-provided content to upload? (If yes, see “Requesting custom content uploads” section.)
5. Reporting needs
   • Customer’s GLUE Admin email (required): To access reporting dashboards (e.g., user enrollments, course completions, active users, adoption activity), the customer needs an admin account. Collect the email address(es) of customer stakeholders who should have reporting access and include them in the request issue.
   • To add a reporting admin after the initial setup, see the Adding admins to an existing Panorama section below.

How to request a Panorama

1. Gather customer details Collect all pre-requisite information listed above.
2. Create a new issue Use the Panorama request template: Dedicated portal request template
3. Track progress
   • Use the issue as the system of record for the request
   • Keep the issue updated with:
     • Status updates from the GitLab University team
     • Links to the live Panorama once provisioned
     • Notes from any SSO configuration calls
   • Panorama setup SLA: 5 business days
4. Document for ongoing account management
   • Add the Panorama URL and key details (authentication method, main learning paths, reporting owner) to:
     • The customer’s Gainsight C360, and/or
     • The customer collaboration project on GitLab

After the customer gains access

Initial rollout

• Share the customer-specific welcome one-pager (provided by the GitLab University team)
• Remind them of certification vouchers and how to redeem them
• Recommend learning paths aligned to their goals

Ongoing engagement (at least quarterly)

Review Panorama usage with the customer to:

• Track adoption, course completions, and certification progress
• Identify unused vouchers and highlight expiration dates
• Suggest new learning paths based on current initiatives or product updates

Getting support

For GitLab team members

• For issues with the platform, bugs, or new feature requests, open an issue in the GitLab University project: GitLab University issues
• For post-launch customization (uploading custom content, excluding content), use the same project and select the appropriate issue template

For customers

• Customers can email university@gitlab.com to contact the GitLab University team directly for help with the Panorama

Requesting custom content uploads

To upload customer-specific content into a Panorama:

1. Open a request using this issue template: Custom content upload request
2. Include:
   • Title of the content
   • Short description (audience, purpose, where it should appear)
   • The file to upload (or link, if appropriate)

Target SLA: 3 business days from receipt of complete information

Note: The GitLab University team will upload customer-specific content but will not create custom learning paths due to maintenance overhead when courses are updated.

Adding admins to an existing Panorama

To add a customer as a reporting admin after the initial Panorama setup:

1. Comment on the existing Dedicated Portal issue for the customer
2. Provide the customer stakeholder’s email address(es) who need reporting access
3. The GitLab University team will provision admin access within 5 business days

Admins can view usage reports and dashboards in GitLab University Enterprise, including user enrollments, course completions, active users, and adoption activity.

The value of GitLab University for customers

• Scalable, self-serve learning for teams at any size
• Access to GitLab University content organized by focus area like DevOps and CI/CD, Security, and AI Duo
• A mix of short courses, hands-on labs, and certifications
• Customer-specific reporting on usage and completion
• Ability to include customer-owned content in the same portal
• One centralized hub for all GitLab education used across the organization

Escalation path (internal)

If you encounter blockers or critical issues:

1. Open a GitLab issue in the GitLab University project and tag:
   • @khokanson
   • @p_luong
2. Escalate in Slack:
   • Post in #digital-success with:
     • A link to the issue
     • A short summary of the blocker
   • Tag:
     • @khokanson
     • @p_luong
     • @rpeterson5

View page source - Edit this page - please contribute.