Skip to main content

Configure preferences

In order to configure preferences to fine tune your GitGuardian instance, navigate to Settings > General > Preferences.

danger

Please be careful some preferences allow you to activate features in beta mode. If in doubt, please seek advice from GitGuardian team.

Table of Preferences

General

PreferenceDefault ValueDescription
token_expire_in_days7Lifespan, in days, of invitations and password reset links
presence_check_enabledtrueEnable secret presence check. For more info, please refer to Investigate incidents page
presence_check_display_enabledtrueEnable display of secret presence checks
background_presence_check_enabledtrueEnable automatic secret presence check in background tasks
validity_check_enabledtrueEnable secret validity check
background_validity_check_enabledtrueEnable automatic secret validity check in background tasks

SAML SSO

For more info, please refer to the SAML SSO page.

PreferenceDefault ValueDescription
use_model_signature_settingstrueEnable the manual configurations of the SAML signatures requirements
is_custom_nameid_format_enabledfalseEnable the choice of NameID format

Bitbucket

For more info, please refer to the Bitbucket integration documentation.

PreferenceDefault ValueDescription
min_delay_between_syncs60Minimum delay, in minutes, between two consecutive synchronizations of a Bitbucket installation
auth_error_grace_period0Minimum period, in minutes, of repeated authentication errors after which a token should be revoked

On Premise

PreferenceDefault ValueDescription
bitbucket_disable_admin_checkfalseDisable Bitbucket integration Admin Check when creating integration
prometheus_metrics_activefalseActivate Prometheus Metrics Exporter on /metrics. For more info, please refer to Applicative metrics page
custom_telemetry_activetrueEnable sending telemetry metrics to GitGuardian
openai_api_key-OpenAI API key

Notifier

For more info, please refer to the Custom webhook page.

PreferenceDefault ValueDescription
max_webhooks_per_integration_type1000Maximum number of configured webhooks per integration type

Policy

PreferenceDefault ValueDescription
is_repo_size_controlledfalseLimit size of repositories for historical scan. For more info, please refer to the following page.
repo_scan_size_limit1073741824Maximum repository size for historical scan, in Byte. For more info, please refer to the following page.
repo_scan_pending_limit_in_hours168Timeout, in hours, of the queue time of a repository's historical scan. For more info, please refer to the following page.
repo_scan_time_limit_in_sec7200Timeout, in seconds, for historical scan of repository. For more info, please refer to the following page.
token_scanner_maximum_file_size_MB1048576Maximum file size for secrets detection scan, in Byte
displayed_content_max_size1048576Maximum displayed content size, in Byte. Introduced in 2023.11.
displayed_content_max_lines1000Maximum displayed content lines. Introduced in 2023.11.

Public API

For more info, please refer to our API documentation.

PreferenceDefault ValueDescription
maximum_multifile_documents20Maximum number of files in a multi-file document for scanning via API
maximum_scan_size1048576Maximum document size for secrets detection scan via API, in B
maximum_token_per_account150Maximum number of API keys allowed per workspace
maximum_token_per_member5Maximum number of personal access tokens allowed per member
quotas10000000Monthly sliding quotas for API calls

GitHub

For more info, please refer to the GitHub integration documentation.

PreferenceDefault ValueDescription
is_actionable_checkrun_enabledfalseEnables action buttons on checkruns (removed in 2024.2.0)
check_runs_overrides_labels_ghefalseEnable overriding the check run settings with repository labels on GitHub Entreprise
commit_collector_max_workers4Maximum number of calls per worker for the commit collector. Higher number will make the commit collection faster, but is more prone to reach GitHub rate limits. Expected value between 1 and 4.

Filters

PreferenceDefault ValueDescription
ai_filters_enabledfalseEnable AI filters on the compatible pages, it requires an OpenAI API key to be setup.

Background Presence Check Frequencies

For more info, please refer to the Investigate incidents page.

PreferenceDefault ValueDescription
ignored_old0Frequency, in days, of automated checks for presence in git history for ignored secret incidents more than 1 year old
ignored_recent178Frequency, in days, of automated checks for presence in git history for ignored secret incidents less than 1 year old
open_old7Frequency, in days, of automated checks for presence in git history for open secret incidents more than 1 year old
open_recent1Frequency, in days, of automated checks for presence in git history for open secret incidents less than 1 year old
resolved_old178Frequency, in days, of automated checks for presence in git history for resolved secret incidents more than 1 year old
resolved_recent30Frequency, in days, of automated checks for presence in git history for resolved secret incidents less than 1 year old

Background Validity Check Frequencies

For more info, please refer to the Investigate incidents page.

PreferenceDefault ValueDescription
ignored_old0Frequency, in days, of automated secret validity checks for ignored secret incidents more than 1 year old
ignored_recent178Frequency, in days, of automated secret validity checks for ignored secret incidents less than 1 year old
open_old7Frequency, in days, of automated secret validity checks for open secret incidents more than 1 year old
open_recent1Frequency, in days, of automated secret validity checks for open secret incidents less than 1 year old
resolved_old178Frequency, in days, of automated secret validity checks for resolved secret incidents more than 1 year old
resolved_recent30Frequency, in days, of automated secret validity checks for resolved secret incidents less than 1 year old

How can I help you ?