- Access the Admin Area
- Default first day of the week
As an administrator of a GitLab self-managed instance, you can manage the behavior of your deployment.
The Admin Area is not accessible on GitLab.com, and settings can only be changed by the GitLab.com administrators. For the settings and limits on the GitLab.com instance, read GitLab.com settings.
To access the Admin Area:
- Sign in to your GitLab instance as an administrator.
- On the top bar, select Menu > Admin.
- On the left sidebar, select Settings, and the group of settings to view:
The General settings contain:
- Visibility and access controls - Set default and restrict visibility levels. Configure import sources and Git access protocol.
- Account and limit - Set projects and maximum size limits, session duration, user options, and check feature availability for namespace plan.
- Diff limits - Diff content limits.
- Sign-up restrictions - Configure the way a user creates a new account.
- Sign in restrictions - Set requirements for a user to sign in. Enable mandatory two-factor authentication.
- External Authentication - External Classification Policy Authorization.
- Web terminal - Set max session time for web terminal.
- Web IDE - Manage Web IDE features.
- FLoC - Enable or disable Federated Learning of Cohorts (FLoC) tracking.
The CI/CD settings contain:
- Continuous Integration and Deployment - Auto DevOps, runners and job artifacts.
- Required pipeline configuration - Set an instance-wide auto included pipeline configuration. This pipeline configuration is run after the project’s own configuration.
- Package Registry - Settings related to the use and experience of using the GitLab Package Registry. Some risks are involved in enabling some of these settings.
The Geo setting contains:
- Geo - Replicate your GitLab instance to other geographical locations. Redirects to Admin Area > Geo > Settings are no longer available at Admin Area > Settings > Geo in GitLab 13.0.
The Integrations settings contain:
- Elasticsearch - Elasticsearch integration. Elasticsearch AWS IAM.
- Kroki - Allow rendering of diagrams in AsciiDoc and Markdown documents using kroki.io.
- Mailgun - Enable your GitLab instance to receive invite email bounce events from Mailgun, if it is your email provider.
- PlantUML - Allow rendering of PlantUML diagrams in documents.
- Slack application - Slack integration allows you to interact with GitLab via slash commands in a chat window. This option is only available on GitLab.com, though it may be available for self-managed instances in the future.
- Third party offers - Control the display of third-party offers.
- Snowplow - Configure the Snowplow integration.
- Google GKE - Google GKE integration enables you to provision GKE clusters from GitLab.
- Amazon EKS - Amazon EKS integration enables you to provision EKS clusters from GitLab.
The Metrics and profiling settings contain:
- Metrics - Prometheus - Enable and configure Prometheus metrics.
- Metrics - Grafana - Enable and configure Grafana.
- Profiling - Performance bar - Enable access to the Performance Bar for non-administrator users in a given group.
- Self monitoring - Enable or disable instance self monitoring.
- Usage statistics - Enable or disable version check and Service Ping.
- Pseudonymizer data collection - Enable or disable the Pseudonymizer data collection.
The Network settings contain:
- Performance optimization - Various settings that affect GitLab performance, including:
User and IP rate limits - Configure limits for web and API requests.
These rate limits can be overridden:
- Package Registry Rate Limits - Configure specific limits for Packages API requests that supersede the user and IP rate limits.
- Git LFS Rate Limits - Configure specific limits for Git LFS requests that supersede the user and IP rate limits.
- Files API Rate Limits - Configure specific limits for Files API requests that supersede the user and IP rate limits.
- Deprecated API Rate Limits - Configure specific limits for deprecated API requests that supersede the user and IP rate limits.
- Outbound requests - Allow requests to the local network from hooks and services.
- Protected Paths - Configure paths to be protected by Rack Attack.
- Incident Management Limits - Limit the number of inbound alerts that can be sent to a project.
- Notes creation limit - Set a rate limit on the note creation requests.
The Preferences settings contain:
- Email - Various email settings.
- What’s new - Configure What’s new drawer and content.
- Help page - Help page text and support page URL.
- Pages - Size and domain settings for static websites.
- Polling interval multiplier - Configure how frequently the GitLab UI polls for updates.
- Gitaly timeouts - Configure Gitaly timeouts.
- Sidekiq Job Limits - Limit the size of Sidekiq jobs stored in Redis.
The Reporting settings contain:
- Spam and Anti-bot Protection - Enable anti-spam services, like reCAPTCHA or Akismet, and set IP limits.
- Abuse reports - Set notification email for abuse reports.
The Repository settings contain:
- Repository’s custom initial branch name - Set a custom branch name for new repositories created in your instance.
- Repository mirror - Configure repository mirroring.
- Repository storage - Configure storage path settings.
- Repository maintenance:
- Repository static objects - Serve repository static objects (for example, archives and blobs) from an external storage (for example, a CDN).
The Templates settings contain:
- Templates - Set instance-wide template repository.
- Custom project templates - Select the custom project template source group.
You can change the Default first day of the week for the entire GitLab instance:
- On the top bar, select Menu > Admin.
- On the left sidebar, select Settings > Preferences.
- Scroll to the Localization section, and select your desired first day of the week.