Configuration settings

The default language and locale for users of the environment. It has to contain a language code and may contain a country code.

• The language has to be an ISO language code.
• The country has to be an ISO country code.

Examples: en-US, fr-FR.

• Enabled (default): Show the asset type of the target asset in the title of relation tables on an asset page. The target asset can be either the head or the tail of the relation, depending on which asset page you have open.
• Disabled: Hide the asset type of the target asset.

• Enabled (default): When you sign in to Collibra or click the application logo, the homepage is shown, instead of your default dashboard.
• Disabled: When you sign in to Collibra or click the application logo, your default dashboard is shown, instead of the homepage.

The cron schedule for sending automated workflow notification emails at specific times. This allows you to send emails in batches and prevent an overload of messages.

This setting applies only to automated workflow notification emails that inform users about task assignments or workflow status updates. It does not affect emails sent as part of an email task.

If you create an invalid cron pattern, Collibra stops responding.

The days of the week on which Collibra sends notifications. The days are represented by numbers from 1 to 7, where 1 represents Sunday.

You can only add one day per row.

• Enabled: The users receive a monthly summary.
• Disabled (default): The users do not receive a monthly summary.

Enabled: Hyperlinks are created automatically.

Disabled (default): Hyperlinks aren't created automatically.

For more information about automatic hyperlinks, go to Automatic hyperlinking.

Enabled: Hyperlinks are case-sensitive.

Disabled (default): Hyperlinks aren't case-sensitive.

Note If you edit this setting, you must reindexCollibra.

• Enabled (default): The "Data sets you might like" section is included on the Catalog homepage. This section shows data sets you might be interested in, as determined by the recommender, which takes into account your data sets and the data sets of similar users.
• Disabled: The "Data sets you might like" section is not included on the Catalog homepage.

The cron schedule by which the data set recommender looks for recommended data sets for a user.

By default the data set recommender does this every night.

The amount of business assets that have to be related to two data sets before the data sets are considered to be similar.

This percentage is expressed by a decimal where 1 equals 100%.

Example If this value is 0.3 and at least 30% of the related business assets are related to both data sets, they are considered to be similar.

The amount of assets that have to be related to both schemas before the schemas are considered to be similar.

This percentage is expressed by a decimal where 1 equals 100%.

The percentage that determines to what extent assets with a similar name become more important.

The ranking in the search engine results always has an impact on the suggestion score. However, similarity between the asset names can also be taken into account. If you decrease this percentage, the ranking of the search results becomes more important for the suggestion score, while the similarity between the asset names becomes less important. If you increase the percentage, assets with similar names will receive a higher suggestion score.

This percentage is expressed by a decimal where 1 equals 100%. You can enter a value greater than 1.

An ordered comma-separated list of values that define the importance of properties for recommendations. The order of the values reflects the importance of the value.

This setting is only used for data set recommendations if your Collibra does not yet have enough data for relevant results from the active recommendations algorithms.

Possible values:

• CERTIFIED: Data sets that are certified are considered more relevant.
• POPULARITY: The number of visits to the data set page.

A comma-separated list of algorithms that calculate recommendations. By default, all available algorithms are listed.

Possible values:

• BASELINE
• USER_MEAN
• IICF (Item-Item Collaborative Filtering)
• SLOPE_ONE
• WEIGHTED_SLOPE_ONE

Enabled (default): A wildcard (asterisk) is automatically added to the end of each search text to find more matches. For example, search text loan size is treated as loan size*, finding assets containing sizeable.

An asterisk isn't added if:

• The search text contains a tilde (~).
• The search text ends with a quotation mark (").

Note This setting applies only to search texts via the user interface. A wildcard isn't automatically added to search texts via REST API.

Disabled: A wildcard isn't added to the search text.

The maximum batch size for resource reindex.

• Default value: 5,000
• Minimum value: 100
• Maximum value: 30,000

The maximum batch size for relation reindex.

• Default value: 500
• Minimum value: 10
• Maximum value: 10,000

The maximum batch size for the relation path preview of relation index.

• Default value: 500
• Minimum value: 50
• Maximum value: 10,000

The time limit, in milliseconds, after which an index query is logged in Elasticsearch.

If the value is set to 0 (zero), all index queries are logged.

Changes to this setting require a full reindex of your Collibra Platform environment.

The MIME type names of the files you want to allow for uploads.

For example, type application/pdf for PDF files.

The maximum amount of statistics entries that the buffer can contain before saving them in the database.

The default value is 10.

The maximum amount of time in milliseconds to keep statistic entries in memory before saving them in the database.

The default values is 10,000.

• Enabled: Allow workflows to start as a result of the changes performed by an import operation.
• Disabled (default): Prevent workflows from starting as a result of the changes performed by an import operation.

Note This setting does not affect API import calls, which never start workflows.

• Enabled: Enable importing responsibilities at asset level.
• Disabled (default): Disable importing responsibilities at asset level.

Warning Setting specific responsibilities on a large number of resources will affect the performance and stability of the system.

An import job with the option to continue on error enabled will stop after the specified number of commands have failed. Any valid command is still committed to the database until the moment the job stops, which can lead to some resources being imported.

The default and maximum value is 100.

The location of the temporary files used by the import job.

The default value is FILE.

• Enabled: Use quotes for every cell in the CSV.
• Disabled (default): Only use quotes when necessary.

Content of the HTTP-header X-Frame-Options. This is set on all rendered pages and is used to avoid clickjacking attacks. By default, only pages with the same origin can use the rendered pages in a frame.

• Enabled: Users can only open only one session.
• Disabled (default): Users can open multiple sessions.

• Enabled: The Office research integration is always allowed guest access via REST, regardless of the general Guest access setting.
• Disabled (default): The general Guest access setting is retained.

Note Currently, the Office research integration is available only when Collibra Platform is publicly available, which is why this override setting is necessary.

Text widgets in dashboards can contain full HTML, which introduces the risk of cross-site scripting (XSS) attacks if malicious HTML is injected. You can use this setting to control the behavior of Text widgets.

• Enabled (default): Potentially dangerous HTML elements are removed from Text widgets after saving.
• Disabled : No HTML elements are removed from Text widgets after saving.

• Enabled: LDAP integration is enabled.
• Disabled (default): LDAP integration is disabled.

• Enabled (default): LDAP data is synchronized with Collibra when an initial data set is bootstrapped.
• Disabled: LDAP data is synchronized with Collibra only when the LDAP synchronization job is triggered.

The page size that is used when retrieving users during synchronization.

The default value is 500. You can set it to 0 to disable paging.

Note This is a global setting. If you are working with multiple LDAP servers, only the value for the main server is considered.

The page size that is used when retrieving groups.

You can set it to 0 to disable paging.

Note This is a global setting. If you are working with multiple LDAP servers, only the value for the main server is considered.

The time limit in milliseconds for all LDAP searches.

The default value is 120,000.

You can set it to 0 to disable the time limit.

• Enabled (default): The synchronization job is enabled.
• Disabled: The synchronization job is disabled.

The schedule to perform an LDAP synchronization (CRON).

The default value for this setting is daily at midnight.

If you create an invalid cron pattern, Collibra stops responding.

The middle name field of the LDAP directory, this is usually givenName.

The language and locale of the user. It must contain a language code and may contain a country code.

• The language has to be an ISO language code.
• The country has to be an ISO country code.

Example pl, en_US, nl_BE.

The LDAP property that defines to which Collibra groups the user should be added.

Use group names, this field does not support group IDs.

If there is a group entry in the LDAP directory, use the Group field mapping settings.

An additional email list.

The name of the group to use in the application.

The Collibra parameters to map with your LDAP server parameters.

The filter that specifies which users are imported by the synchronization job. The users have to be the same as, or a subset of, the Authentication user LDAP filter.

If you provide no value for this setting, the same filter as specified for the Authentication user LDAP filter setting is used. That allows you to synchronize only the users that need to have access to the application, even if they have not signed in yet. Users in the Authentication user LDAP filter are synchronized each time they authenticate and are only available after the first sign-in to the application. This is the default setting.

The authentication mechanism for authenticating users on the LDAP servers.

• Enabled: The LDAP context is destroyed immediately. When using TLS, some servers require the connection to be shut down by the client before the LDAP context is destroyed.
• Disabled (default): The LDAP context is not destroyed immediately.

Specifies what to do with referrals. The following table contains the possible values.

Note If you are experiencing slow searches on Microsoft Active Directory with the follow value for the Referral setting, try using the Global Catalog as Active Directory domain controller. The Global Catalog enables searching for Active Directory objects in any domain in the forest without the need for subordinate referrals. This can dramatically speed up searching. However, the Global Catalog only contains a subset of the attributes of an object. This solution is only viable if the attributes requested for the search results are stored in the global catalog. Note that the Global Catalog is accessible on port 3268/3269, not the standard 389/636 LDAP ports.

The minimum length of passwords.

The default minimum length is 12.

The maximum length of passwords.

The default maximum length is 1,024.

• Enabled (default): Passwords have to contain one or more digits.
• Disabled: Passwords do not have to contain digits.

• Enabled (default): Passwords have to contain one or more non-alphanumeric (special) characters.
• Disabled: Passwords do not have to contain non-alphanumeric characters.

• Enabled (default): Passwords have to contain one or more upper-case characters.
• Disabled: Passwords do not have to contain upper-case characters.

• Enabled (default): Passwords have to contain one or more lower-case characters.
• Disabled: Passwords do not have to contain lower-case characters.

• Enabled (default): Passwords cannot be the username.
• Disabled: Passwords can be the username.

The number of months before users have to change their passwords.

Set it to 0 if users never have to change their passwords.

The default interval is 3 months.

The number of consecutive failed login attempts that are allowed before the user account is disabled.

Set it to 0 for unlimited attempts.

The default is 3 login failures.

The number of previous passwords users cannot reuse. The default is 1: the user cannot change his password to what it currently is.

Set this to 0 to allow using the same password.

The number of minutes that a link to reset a password remains valid. Beyond this time, the user has to request a new password reset link.

The default value is 60 minutes.

The minimum value is 15 minutes, the maximum value is 1,440 minutes (24 hours).

This option offers limited security, so we recommend upgrading to the Enhanced CSRF.

• Enabled: The validity of a request is checked with a CSRF token.
• Disabled (default): The validity of a request is not checked with a CSRF token.

• Enabled: The HTTP referrer header is used to identify the origin of the request.
• Disabled (default): The HTTP referrer header is not used to identify the origin of the request. It is recommended to leave this option disabled.

The SSO mode of Collibra.

The possible values are:

• SAML_ATTRIBUTES
• SAML_LDAP
• SSO_HEADER
• SSO_HEADER_LDAP
• DISABLED

The name of the header to be checked. The contents of this header is used for the search query, which is SSO_HEADER = username.

The value of the actual query depends on DN and possibly Attribute.

If the SSO mode is SSO_HEADER_LDAP or SAML_LDAP, this field determines whether the distinguished name (DN) or attribute is used:

• Enabled: The header has to contain the distinguished name (DN) of the user in the LDAP.
• Disabled (default): The header has to contain the value of Attribute.

If the SSO mode is DISABLED, SSO_HEADER or SAML_ATTRIBUTES, this field is ignored.

This field is only used if the SSO mode is SSO_HEADER_LDAP or SAML_LDAP, and if DN is False.

If the above criteria are met, the LDAP has to contain this value.

If users try to sign in via SSO, they still need a user account in Collibra. You can either create the user accounts automatically when they sign in, or create the user accounts manually or via LDAP synchronization

• Enabled: User accounts are not created automatically.
• Disabled (default): User accounts are created automatically.

When SSO is enabled, a user can still navigate to the /signin page and try to log in via that page. However, you can disable that page.

• Enabled: Users cannot access the Collibra signin page.
• Disabled (default): Users can access the Collibra signin page

The entity ID inside the metadata to be referenced.

Note A metadata file can describe multiple entity IDs, make sure to use in the entity ID from the correct metadata file.

The mappings of attributes in the SAML response. The values are used as keys to look for in the SAML response.

Examples of attribute fields are first name, last name, address information, phone numbers and so on.

The mapping for the user's first name.

This attribute is optional. The value can be empty.

The mapping for the user's last name.

This attribute is optional. The value can be empty.

The mapping for the user's email address.

This attribute is optional for existing users, but mandatory for new users.

Warning If the email address is invalid when you synchronize, the user is deactivated and the user information is not updated.

The mapping (attribute) which indicates to which Collibra groups the user should be added. If the groups don't exist yet, they will be created. This attribute can have multiple values (groups) or the groups can be sent as a comma-separated list of groups.

Use group names, this field does not support group IDs.

If passing groups in this attribute, you must set Groups DGC Managed to False.

Option to configure that groups should be managed by Collibra, or that groups should be set by the SAML assertion (SAML+Attributes mode).

This option is only relevant if Mode is SAML_ATTRIBUTES.

• Enabled: The groups are fully managed by Collibra. In the UI the admin has the option to assign groups to users, without it being overwritten by SAML.
• Disabled (default): The groups are managed by the SAML assertions. In this case the groups are managed by the SAML IDP. Be sure to configure the Group attribute in the Attribute Fields section.

Field that determines the value of the Entity ID parameter in the service provider metadata returned by Collibra. The default value is empty, in which case Collibra uses the value of the Base URL field.

Enter a custom value if the base URL does not match the audience configured in your SAML identity provider.

Warning The value of the audience restriction in the SAML response has to be exactly the same as the value of this field.

Note SSO does not work if the Service Provider Entity ID field contains the base URL with trailing forward slash (for example www.collibra.com/), and the audience of your IDP contains the base URL without a trailing forward slash (for example www.collibra.com).
Both values need to be exactly the same. In this case, you can resolve the issue by changing the value in the configuration of your IDP, or the value of this field. It does not matter whether both have a trailing forward slash or not, as long as they contain the same value.

• Enabled: Authentication requests have to be signed.
• Disabled (default): Authentication request don't have to be signed.

• Enabled (default): The SP authentication request forces re-authentication.
• Disabled: The SP authentication request does not force re-authentication.

• Enabled: The reauthentication has to happen in the background.
• Disabled (default): The reauthentication does not have to happen in the background.

This is only relevant if Force authn is True.

Name ID that is used in the SP authentication. The default value is urn:oasis:names:tc:SAML:2.0:nameid-format:persistent.

The Name ID value is mandatory.

• Enabled (default): The IDP can create a name ID to fulfill the SP authentication request.
• Disabled: The IDP cannot create a name ID to fulfill the SP authentication request.

• Enabled: The validation of the client IP address in the assertion message is disabled.
• Disabled (default): The validation of the client IP address in the assertion message is enabled.

Settings for the SAML requested authentication context. The IDP uses the authentication context to authenticate the user. By default, the authentication context mandates user/password authentication over HTTPS.

• Enabled: The requested authentication context section is not sent in the SAML request.
• Disabled (default): The requested authentication context section is sent in the SAML request.

The comparison type that is transmitted in the requested authentication context.

Possible values:

• minimum
• maximum
• better
• exact (default value)

For more information about the comparison type values, refer to the SAML specifications.

The list of class references in the requested authentication context. You can separate list items with the pipe character (|).

For more information about this list, refer to the SAML specifications.

The list of class declarations in the requested authentication context. You can separate list items with the pipe character (|).

For more information about this list, refer to the SAML specifications.

Enable the support for encrypted SAML responses.

• DISABLED: Collibra only accepts plain-text SAML responses.
• OPTIONAL: Collibra can handle both encrypted and plain-text SAML responses.
• FORCED: Collibra only accepts encrypted SAML responses.

Once OPTIONAL or FORCED is selected, the encryption key pair is generated and added to the Collibra SAML keystore. A self-signed certificate is generated and works in most situations. If your IdP rejects self-signed certificates, you will have to add a certificate that is signed by a trusted 3rd party.

• Enabled: Redirect the user to a specific website after signing out.
• Disabled (default): Redirect the user to the sign-in page after signing out.

The option to disable Formula Injection into Excel. When enabling this option, an escape character is added at the beginning of Excel formulas during the export and is removed when importing formulas.

The escape character will be added to fields that start with one of the following characters:

• equation: =
• plus: +
• minus: -
• at-sign: @

This option is enabled by default.

The URL to retrieve public key information needed to verify the authenticity of JSON Web Tokens (JWTs), issued by an authorization server.

This setting is required to enable JWT authentication.

A case-insensitive comma-separated list of accepted JWT media types coming in the typ header parameter.

Leave blank if the authorization server does not provide a media type parameter.

The default values is at+jwt,jwt.

A comma-separated list of accepted JWT algorithms coming in the alg header parameter. See https://tools.ietf.org/html/rfc7518#section-3.1 for details.

Leave blank to accept all digital signature algorithms.

The accepted issuer coming in the iss JWT claim.

Leave blank if the authorization server does not provide an issuer claim.

A comma-separated list of accepted audience values for the aud claim.

The value for this field is a configuration setting in your authorization server, which identifies your Collibra environment as the intended recipient of the JWT.

Leave blank if the authorization server does not provide an audience claim.

The name of the JWT claim containing the principal's identity. See https://tools.ietf.org/html/rfc7519#section-4.1.2 for details.

Defaults to the standard subject claim, sub.

Change this setting only if your authorization server has other means of identifying the principal, for example, a client_id claim.

This setting is required if JWT authentication is enabled.

• Enabled: Upon signing in, show a disclaimer that you have to agree with before you can continue.
• Disabled (default): Don't show a disclaimer.

A list of AWS regions that Data Catalog is allowed to connect to. For example, eu-west-3 and us-east-2. For a list of all AWS locations, see the AWS documentation.

• If you want to allow Collibra to make a connection to any AWS region, leave the field empty.
• If you remove a region from this list and that region was previously used for an S3 integration, you may want to delete the Glue database from the previously used region manually. By default, Collibra does not remove it. The Glue database has the following naming convention: collibra_catalog_<Asset Id>_<Domain Id>
  For example: collibra_catalog_d3174a88-5ffe-4d50-8fbe-7bf0832ec3af_5d198ce9-4e56-4d0e-a885-58204da50741
• When using Edge, a warning is added to the logs if an invalid region is detected in the restricted regions list.

Allowed number of AWS API calls per second.

Use this option to limit the number of API calls per second to prevent throttling errors from the AWS API.

Number of assets in a single batch that are fetched from a Glue database and ingested into Collibra.

CRON schedule that specifies when to refresh configuration options from the external system for integrations that support this functionality.

An option to enable database registration via Edge.
The available options are:

• Enabled: You can register a data source via Edge or Jobserver.
  Enabling data source registration via Edge doesn't prevent you from registering a data source via Jobserver as well.
• Disabled: You can register a data source via Jobserver only.

Warning Jobserver and all related Jobserver integrations reached their End of Life in commercial environments in October, 2024. In Collibra Platform for Government and Collibra Platform Self-Hosted environments, they will reach their End of Life on May 30, 2027.
For information on registering a data source via Edge, go to Registering and synchronizing a data source via Edge.

This setting specifies the maximum number of Edge jobs that can run simultaneously to connect to a data source, update a schema list, or synchronize a schema. If the maximum number is reached, subsequent jobs are queued.
The default value is 10. You can enter a value from 1 to 20.
This setting applies only to JDBC data sources.

The list of registered Jobserver instances.

The name of the Jobserver as it will appear when you register a data source in Data Catalog.

The name is a freely chosen name but it is recommended to only use alphanumerical characters and dashes, for example Jobserver-1.

You will have to use this name as the ID of the gateway and in the address of this configuration.

The protocol that is used for the communication between the Data Governance Center service and the Jobserver service.

It is recommended to use HTTPS, especially if the services are hosted in different network segments.

The address (IP address, URL, hostname) of the Jobserver.

The certificate of the trusted CA needed to validate the server certificate. If blank, the default truststore will be used. The default truststore is defined in the SSL configuration section of the DGC service.

The CA certificate of the server party (Jobserver).

The client certificate offered by the DGC service to the server. If blank, you cannot select mutual authentication as the Jobserver service authentication level.

The private key of the DGC service's certificate.

The approximate maximum disk size of the data in MB that will be used to profile a table. The value cannot exceed 10,000.

• Enabled (default): Show the new Settings landing page in your Collibra environment.
• Disabled : Use the classic Settings page in your Collibra environment.

Enable this setting to allow admins to set a default domain view for a domain type in the operating model.

• Enabled: Admins can set a default domain view for a domain type in the operating model.
• Disabled: A default domain view cannot be set.

For more information, go to Set or remove a default domain type view (in preview).

• Enabled: Activates the Derived Relations feature in the latest user interface. A derived relation is a kind of relation that shows how one asset is related to another asset that is multiple relations away.
• Disabled (default): Deactivates the Derived Relations feature in the latest user interface.

Enables the relation table default view migration feature. In the migration tool, the default relation table views are exported along with the asset type assignments when this setting is enabled.

• Enabled: Enable the new diagram canvas in the user interface.
• Disabled (default): Use the standard diagram canvas.

Enable smart checks for assets.

Enables lifecycle management for status-based control, introducing granular control over asset lifecycle activities, allowing administrators to define mandatory steps, including smart checks, assessments, and required sign-offs based on the asset's current status. This applies to all asset types except BI Folder, BI Report, Data Element, and Data structure and its children.

Enables the AI-powered writing assistant, a feature designed to significantly boost productivity and content quality for asset pages. Once enabled, administrators can define and configure context-aware AI prompts for generating, transforming, summarizing, and explaining content across various textual attributes and asset types. This provides precise control for enforcing governance standards and guaranteeing consistent, high-quality metadata output.

Enable this option to show the Start Date filter for history on all pages. This may help with performance when there are many history entries.

Select the date format to use in the new Collibra Frontend experience.

The default value is LOCALE.

• Enabled: Shows a dialog box when users click external links to warn them about the redirection to third-party websites. Enabling this setting may decrease the UI performance.
• Disabled (default): Does not show a dialog box when users click external links.

• Enabled: Enable limiting the number of root elements as result of a Graph query.
• Disabled (default): Disable limiting the number of root elements as result of a Graph query.

The maximum number of root nodes that you can request in the view configuration of an API call (REST or workflow).

If you exceed this value in the view configuration, an exception is shown. If no value is defined in the view configuration, then the default value is taken.

The default value is 100,000.

Note If the number of asset types or domain types exceeds the set number, the hierarchy will be incomplete. Make sure that the limit is always higher than the actual number of asset and domain types.

• Enabled: Tables can be sorted on multiple columns.
• Disabled (default): Tables can be sorted on one column.

Cron expression specifying the timing and frequency of purge cycles. The default value is 02:00 AM every day, which equates to 0 2 * * *. The minimum value is 1 minute, which equates to * * * * *.

Maximum time, in seconds, allowed for each purge cycle. The default value is 7200 seconds, which is 2 hours.

Data elements and the age, in months, at which they will be purged (deleted). If you add a data element and specify its age, all data specific to the data element older than the specified age is deleted from your environment without any possibility of recovery.

The following data elements are available for purging:

• AUDIT_HISTORY: Platform audit history, which includes the data shown on the History tab of community, domain, asset, and user profile pages.
  
• AUTHENTICATION_EVENTS: Data about authentication in your environment.
• GLOBAL_CREATE_RECENT_ASSET_TYPES: Data about which types of assets were recently created in your environment. This data is shown on the Recent tab when users create assets. By default, this data element is set to 2 months, and is visible only to users who have the SUPER role. If deleted, it is automatically restored when the application restarts.
• JOBS: Data about all the jobs created in your environment. By default, this data element is set to 6 months.
• LICENSE_USAGE: Data about how licenses are used in your environment. By default, this data element is set to 24 months.
• STATISTICS: Data used to calculate data quality.
• VALIDATION_RESULTS: Information about data validation.

Click Add to specify the age, in months, at which each individual data element will be purged. This setting is available only to users who have the SUPER role.

Option to enable or disable the automatic deletion of tags that aren't assigned to any assets.

• Enabled (default): Orphan tags are deleted based on the timing and frequency specified in the Orphaned tags removal schedule field.
• Disabled: Orphan tags aren't deleted.

Cron expression specifying the timing and frequency for deleting orphan tags. The default value is 01:00 AM every day, which equates to 0 1 * * *. The minimum value is 1 minute, which equates to * * * * *.

• Enabled: Enable Collibra's data classification technology.
• Disabled (default): Do not use Collibra's data classification technology are not accepted.

This setting is no longer in use. For information, go to About Data Classification.

Enables the Unified Data Classification method on Edge.

• Disabled: The feature is not enabled.

Enabled: The automatic acceptance and rejection of data classification suggestions is active.

Disabled (default): Data classification suggestions are not automatically accepted or rejected.

Tip Start by manually accepting and rejecting a suggested data class. Only switch to automatic acceptance and rejection if you are comfortable with the data classification results.

The percentage that determines when data classification suggestions are automatically accepted.
For example, if you set this value to 75%, classification suggestions with a confidence level of 75% or higher are automatically accepted.

If multiple classification suggestions meet the threshold for a column, the suggestion with the highest confidence level percentage is accepted automatically, as long as this suggestion is the only one to have that confidence level percentage. If two or more suggestions have the same confidence level, none are accepted automatically, and all remain visible.

The default acceptance threshold is 90.

The Tableau URL pattern, which should contain {reportName}.

• Enabled: Catalog experience is enabled. This will improve the layout of Data Catalog's asset pages, such as those of Data Set, Schema, Table and Column assets.
• Disabled: Catalog experience is disabled.