DGC service configuration settings

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

• True (default): The view permissions feature is enabled.
• False: The view permissions feature is disabled.

The base URL for this Collibra instance, for example http://dgc.example.com. It is the consistent part of the URL to access Collibra Data Intelligence Platform.

This is used amongst others to:

• construct hyperlinks to the system, for example in emails.
• display your profile picture.
• display Tableau report images.
• ...

• True (default): Audit and history information is stored.
• False: Audit and history information is not stored.

The Google Analytics 3 Tracking ID for capturing web analytics for your Collibra environment.

The tracking ID is used to have the code snippet embedded on the Collibra page to capture default Google Analytics 3 events that occur, such as page visits and form submission.

The Google Analytics 4 Tracking ID for capturing web analytics for your Collibra environment.

The tracking ID is used to have the code snippet embedded on the Collibra page to capture default Google Analytics 4 events that occur, such as page visits and form submission.

• True (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.
• False: Hide the asset type of the target asset.

The default value is true.

The usage data is used to understand how users interact with Collibra. The information can be used to provide reporting and recommendations.

When you enable this setting in a cloud environment, the data collection starts immediately. When you enable the setting in an on-premises environment, you may need to approve the tracking script (pendo.io, app.pendo.io, and cdn.pendo.io).

• True (default): Gathering usage data is enabled and sent to Collibra.
• False: Gathering usage data is disabled.

The Pendo usage data API key that you want to use to collect the usage data.

The Cron schedule to send emails only at specific times. With this, you can send emails in batches and avoid an overload of mails.

Keep in mind that these emails are only workflow emails and have nothing to do with the notification schedule.

If you create an invalid Cron pattern, Collibra Data Intelligence Platform stops responding.

The email address used as the sender of all outgoing emails.

Contact Collibra Support to change the From address, see also Email configuration.

• True: Use TLS (Transport Layer Security) to connect to your SMTP server.
• False (default): Do not use TLS to connect to your SMTP server.

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

Per row you can add one day.

• True: The users receive a monthly summary.
• False (default): The users do not receive a monthly summary.

Note  The additional S at the end of the abbreviations stands for the secure version of the protocol using SSL. Using this requires the SSL certificates to be correctly configured.

• True: Only handle emails from the same domain as the handler's email address.
• False (default): Handle emails from any domain.

• True: The handler is enabled.
• False (default): The handler is not enabled.

• True: Delete messages from the mail server once the mail is processed.
• False (default): Keep messages on the mail server after the mail is processed.

This option is only relevant if Protocol is IMAP or IMAPS.

• True: Hyperlinks are created automatically.
• False (default): Hyperlinks are not created automatically.

For more information about automatic hyperlinks, see Hyperlinking.

• True: Hyperlinks are case-sensitive.
• False (default): Hyperlinks are not case-sensitive.

Note If you edit this setting, you have to reindex Collibra.

• True (default): The "Data sets you might like" section is included on the Data Catalog Home page. 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.
• False: The "Data sets you might like" section is not included on the Data Catalog Home page.

The schedule (CRON job) 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,00 equals 100%.

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,00 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,00 equals 100%. You can enter a value greater than 1,00.

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

• True (default): A wildcard (asterisk) is automatically added to each search query. An asterisk is not added if:
  • The query contains a tilde (~).
  • The query ends with a quotation mark (").

  Note This applies only to queries via the user interface. A wildcard is not added automatically for REST API queries.

• False: A wildcard is not added to the search query.

The amount of resources that are scanned in a single operation for the search query.

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

The maximum batch size for relations reindex.

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

A list of stop words that are ignored as tokens for the index.

The default list of English stop words includes the following:

a, an, and, are, as, at, be, but, by, for, if, in, into, is, it, no, not, of, on, or, such, that, the, their, then, there, these, they, this, to, was, will, with

If you do not create your own list of stop words, the default list is used.

If you create your own list of stop words, you need to:

1. Reindex Collibra Data Intelligence Platform.
2. Restart the environment to apply your changes. For more information, go to Stop an environment and Start an environment.

The tokenizer that determines how the search text is split.

The Type field must contain either Standard (default) or Character.

• Standard: The Standard tokenizer is a method of splitting the search text into individual terms and is based on a default set of characters. This tokenizer follows the word break rules from the Unicode Text Segmentation algorithm.
  
• Character: The Character tokenizer allows you to customize when you want a search text to be split into individual terms. For more information, go to When and how to use the Character tokenizer.

The boost factor of data classes.

The boost factor of attribute types.

• Field key: The attribute type ID.
• Field value: The boost factor of the attribute type.

• True (default): If the name of an asset is exactly the same as the search text, put it at the top of the search results regardless of boost factors.
• False: Use the regular search order, taking into account boost factors.

The boost factor of asset types.

• Field key: The asset type ID.
• Field value: The boost factor of the asset type.

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 Data Intelligence Platform environment.

The maximum file size in bytes for uploads.

• For cloud environments, the default value is 512 MB or 536,870,912 bytes. This value cannot be changed.
• For on-premises environments, the default is 10 MB or 10,485,760 bytes.

The maximum number of uploads per user per day.

• For cloud environments, the default value is 1,235,465 uploads. This value cannot be changed.
• For on-premises environments, the default is 150 uploads.

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.

• True: Allow starting workflows upon importing assets.
• False (default): Do not allow to start workflows upon importing assets.

• True: Enable importing responsibilities at asset level.
• False (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.

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

• True (default): The CSS files are optimized to improve performance of the user interface.
• False: The CSS files are not optimized.

• True (default): The JavaScript code is optimized to improve the performance of the user interface.
• False: The JavaScript code is not optimized

• True (default)
• False

• True: The velocity cache is enabled.
• False: The velocity cache is disabled. This allows you to reload velocity templates without restarting Collibra.

• True: API call logging is enabled for REST Core API v1 (deprecated) calls.
• False (default): API call logging is disabled for REST Core API v1 (deprecated) calls.

The maximum number of API calls to store in the component_call_logging database table. Once this number is reached, the oldest records are overwritten.

The default value is 1,000,000.

• True (default): Metric collection is enabled.
• False: Metric collection is disabled.

• True (default): JVM metric collection is enabled.
• False: JVM metric collection is disabled.

• True: Advanced metrics collection is enabled. Enabling this option has a negative impact on the performance of your environment.
• False (default): Advanced metrics collection is disabled.

The 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.

• True: A user can only open one session.
• False (default): A user can open multiple sessions.

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

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

Text widgets can contain full HTML. However, this means an attacker could potentially execute an XSS attack by injecting malicious HTML.

• True: Potentially dangerous HTML elements are removed from text attributes when you save the text field.
• False (default): No HTML elements are removed from text attributes when you save the text field.

• True: Anyone that can access the URL, has viewing rights to the system.
• False (default): The user is asked to sign in before having access to any data.

• True: Schema fields are shown during an introspection.
• False (default): Schema fields are hidden during an introspection.

• True (default): Schema fields are shown when using introspection for public APIs.
• False: Schema fields are hidden when using introspection.

• True: The LDAP integration is enabled.
• False (default): The LDAP integration is disabled.

• True (default): LDAP data is synchronized with Collibra when an initial data set is bootstrapped.
• False: 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 taken into account.

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 taken into account.

Specifies 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.

• True (default): The synchronization job is enabled.
• False: 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 Data Intelligence Platform stops responding.

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

The language and locale of the user. 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: pl, en_US, nl_BE.

The LDAP property that defines to which groups the user belongs. 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 have to have access to the application, even if they have not logged 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.

• True: 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.
• False (default): The LDAP context is not destroyed immediately.

Specifies what to do with referrals. 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.

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

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

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

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

• True (default): Passwords cannot be the username.
• False: 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 6 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.

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

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

• True: The HTTP referrer header is used to identify the origin of the request.
• False (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:

• True: The header has to contain the distinguished name (DN) of the user in the LDAP.
• False (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

• True: User accounts are not created automatically.
• False (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.

• True: Users cannot access the Collibra signin page.
• False (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.

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.

• True: 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.
• False (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.

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

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

• True: The reauthentication has to happen in the background.
• False (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.

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

• True: The validation of the client IP address in the assertion message is disabled.
• False (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.

• True: The requested authentication context section is not sent in the SAML request.
• False (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.

• True: Redirect the user to a specific website after signing out.
• False (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.

The pattern of the URLs to which the HTTP response header is applied.

This field supports wildcards such as **, *, and ?.

Tip The following pattern matches all URLs: /**

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

• True (default): Automatically add an escalation function to user tasks after a configurable period of time.
• False: Don't escalate task automatically.

This option only works for tasks that do not yet have a configured escalation path configured in Collibra Data Intelligence Platform.

The duration before a task is escalated.

For more information on the format, please refer to ISO 8601.

A list of AWS regions 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 the 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.

An option to enable database registration via Edge.

• True: Register a data source via Edge.
• False: Register a data source via Jobserver only.

Note Enabling data source registration via Edge does not prevent you from registering a data source via Jobserver as well.

An option to enable the Data Quality extraction interface in Collibra

• True: The Quality extraction tab is available on the configuration page of a database asset
• False (default): The Quality extraction tab is not available and as such, it is not possible to extract and synchronize data quality information.

You can only enable Collibra Data Quality & Observability synchronization if you also enabled Database registration via Edge.

An option to enable Google Cloud Storage file system registration and synchronization via Edge.

• True: You can register and synchronize a Google Cloud Storage file system via Edge.
• False: You can't register a Google Cloud Storage file system via Edge.

An option to enable Amazon S3 file system registration and synchronization via Edge.

• True: You can register and synchronize an Amazon S3 file system via Edge.
• False: You can only register an Amazon S3 file system via Jobserver.

Note Enabling the registration of an Amazon S3 file system via Edge does not prevent you from registering an Amazon S3 file system via Jobserver.

For more information, see Working with Amazon S3.

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.

A comma separated list of strings enclosed in double quotes. A value that matches one of those expressions is considered an empty value.

Please note that a database null value is always considered an empty value, for example "", "na" and "none".

An option to anonymize sensitive data.

• True: Content in columns with data type Text or Geo is removed or replaced by a random hash value before the profiling results are sent to the cloud.
• False (default): No content is removed or replaced by a random hash value.

Tip For anonymization via Edge, see setting "Anonymize Edge profiling results for all data types".

An option to enable profiling and classifying of synchronized metadata via Edge instead of Jobserver.

• True: Profiling and classification via Edge.
• False: Profile via Jobserver and classify via the Data Classification Platform.

Note You can enable Database profiling via Edge only if you also enabled Database registration via Edge.

The maximum time duration, in minutes, that a profiling Edge job can run before Data Profiling stops the job.

The default value is 20,160 minutes, 2 days.
You can increase this limit to a maximum of 4 days.

The maximum number of schemas that Edge can profile at the same time.

By default, the value of this setting is 4. This means Edge processes four profiling jobs at a time. This can have a huge positive impact on the performance of the profiling activity.
You can increase this number to a maximum of 16.

Enable this option to anonymize all Edge profiling results stored in Collibra.

• True: Profiling results via Edge are anonymized for all columns.
• False (default): Profiling results via Edge are anonymized only for columns with the Text or Geo data type.

Important Data similarity is a cloud-only feature and is not certified for Collibra Cloud for Government.

Enables the data similarity feature in your environment.

• True (default for cloud environments, except for Public sector): Extra algorithms can run during profiling via Edge allowing the calculation of data similarity scores. The data similarity scores are currently used in Data Marketplace to show similar Table assets.
  
• False: The beta feature is not enabled.

• True: Provisioning to Tableau is enabled.
• False (default): Provisioning to Tableau is disabled.

The maximum number of import jobs that can be executed at the same time via the API. This is to avoid memory issues.

Default value is 4, set to 0 if there is no limit.

• True (default): Workflow tasks appear in the sidebar on both resource pages an the task management page. Task forms appear in the sidebar instead of dialog boxes. Users can seamlessly complete their tasks from the task management page and have a side-by-side view of the tasks and resource details on resource pages.
• False : Workflow tasks appear in the task bar on resource pages and in a sidebar on the task management page. Task forms appear in dialog boxes. The behavior is the same as with older versions of Collibra.

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

• True: Enable the Workflow Designer access global permission which allows access to the Workflow Designer, a visual tool for creating process definitions.
• False (default): Disable the Workflow Designer access global permission.

Warning Do not enable this setting if you are working in a CPSH environment. Workflow Designer is not supported for CPSH.

• True(default): This setting is a prerequisite for the Homepage, Data Marketplace, Protect, and Usage Analytics applications. Enabling it will allow to enable these applications. This setting is also a prerequisite for the new frontend experience.
• False: If you set the value to False, the Homepage, Data Marketplace, Protect, and Usage Analytics applications, and the new frontend experience will be disabled.

This setting is not valid for Cloud customers.

• True: Enable the new asset page layout in the user interface.
• False (default): Disable the new asset page layout in the user interface.

Enables the new Unified Data Classification method on Edge.

• True (default in new environments from 2024.02): The environment uses the new classification method, Unified Data Classification. This has an impact on the available data classes, the required capabilities, and the way you classify data.

  Note All existing data classes and classifications become unavailable.

  Tip  A migration process will be available in a future release. This process will transfer all old data classes and classifications to the Unified Data Classification method. Old transferred data classes will need to be updated to include classification rules to work with the new automatic data classification method.

• False: The feature is not enabled.
  

  If you deactivate the setting, you revert back to your previous data classification setup and the previously defined data classes and classifications become available again.

Enable this setting to activate the use of collections in Data Marketplace.

• True: Collections can be used in Data Marketplace.
  • Users can add an asset to a collection from an asset preview in Data Marketplace. They can also remove an asset from a collection from the asset preview.
  • Users can access and manage all their collections from an overview page via their avatar → Collections.
• False: (default): The beta feature is not enabled.
  • When disabled, collections are not accessible via the UI.
  • Existing collections are not removed.

By enabling this setting, the process of checking the Edge cache for samples is much faster.

• True: If samples are already cached, they are immediately visible in the asset page.
  
• False (default): The optimization feature is not enabled.

Enables the latest Collibra user interface, providing a brand new design.

• True: The search function remains available and the current data is available for search, while the search index is rebuilding in the background. Search results, however, may not be up to date until the rebuild is complete. After the rebuild is complete, all new data and changes to the existing data become available for search.
• False (default): The search function becomes temporarily unavailable when the search index is rebuilding.

Allows users to ask Collibra AI for description suggestions for the following asset types:

• Column
• Table
• Database View
• Data Set

The possible values are:

• True: Collibra AI for asset descriptions is enabled.
• False (default): Collibra AI for asset descriptions is not available for users.

• True: 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.
• False (default): Does not show a dialog box when users click external links.

• True (default): Hibernate caching is enabled.
• False: Hibernate caching is disabled.

The list of associated cache configurations.

• True: The cache configuration is eternal.
• False: The cache configuration is not eternal.

Type the amount of seconds until the cache is idle.

Type the amount of seconds until the cache starts.

• True: The cache configuration overflows to the disk. When the cache has reached its maximum number of elements, the next elements will be stored on disk.
• False: The cache configuration does not overflow to the disk. This is the default value.

• True: The disk store is persistent between CacheManager instances.
• False: The disk store is not persistent between CacheManager instances. This is the default value.

This option is only relevant if Overflow to disk is set to True.

Enter the amount of seconds between runs of the disk expiry thread. This value is how often we check for expiry.

This option is only relevant if Overflow to disk is set to True.

Enter the policy how items are deleted from disk:

This option is only relevant if Overflow to disk is set to True.

• True: Tables can be sorted on multiple columns.
• False (default): Tables can be sorted on one column.

A Cron expression specifying the timing and frequency of purge cycles.

The default scheduled time is 002 * *, which equates to 02:00 every day.

If you create an invalid Cron pattern, Collibra Data Intelligence Platform stops responding.

Maximum amount of time (in seconds) allowed for each purge cycle.

The default value is 7,200, which is two hours.

Any qualifying data that is not purged in the allowed time will be addressed in a subsequent purge cycle, which picks up where the previous cycle left off.

The data elements that will be purged at the specified age, in a key-value format:

• The data elements to be purged (Field key). Possible data elements:
  • Statistics: Data that has been used to calculate data quality.
  • Authentication events: Data about authentication in your environment.
  • Validation results: Information about data validation.
  • Jobs: Data about all jobs that are created in your environment.
  • Workflows: Data about completed workflow instances and tasks.
  • License usage: Data about how licenses are used in your environment.
• The age (in months) at which each individual data element will be purged (Field value).

Option to enable the automatic deletion of tags that are not assigned to any assets.

• True (default): Orphan tags are deleted according to the timing and frequency that you specify.
• False: Orphan tags are not deleted.

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

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

Tip Start using this tool by manually accepting and rejecting the data classification suggestions. Only activate the automatic acceptance and rejection feature if you are comfortable with the data classification results.

The percentage from which data classification suggestions must be accepted automatically.
If you set this value to 75, then the classification suggestions with a confidence level of 75% or higher are automatically accepted.

If multiple classification suggestions meet the threshold condition for a column, the classification suggestion with the highest confidence level percentage is accepted automatically if this classification suggestion is the only one to have that confidence level percentage.

The default acceptance threshold is 90.

Cloud provider - AWS or GCP

The GUID of your Collibra environment.

Note This field is configured by Collibra Cloud Ops.

The name of the AWS S3 bucket in which your reporting data is stored.

Note This field is configured by Collibra Cloud Ops.

The AWS S3 region in which your data is processed.

Note This field is configured by Collibra Cloud Ops.

A pattern with the format "/zip/insights_%s.zip", where "%s" is replaced by the Collibra Insights snapshot date.

Note This field is configured by Collibra Cloud Ops.

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

• True: 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.
• False: Catalog experience is disabled.

The time limit, in seconds, after which a diagram stops fetching data.

The value must be a positive integer and cannot be greater than 3,600 (one hour).

The default value is 300.

Example A value of 300 means that if a diagram hasn’t fetched all data within 300 seconds, the diagram stops fetching data and an empty diagram with a notification is shown.

The maximum number of nodes plus edges that will be fetched by the backend, to build a diagram.

The value must be a positive integer and cannot be greater than 100,000.

The default value is 10,000.

Example A value of 10,000 means that if the total number of nodes plus edges is greater than 10,000, the diagram does not load and a notification is shown.

The maximum number of visible nodes plus edges that can be shown on the page.

The value must be a positive integer and cannot be greater than 10,000.

The default value is 2,000.

Example A value of 2,000 means that if the total number of visible nodes and edges is greater than 2,000, the diagram does not load and a notification is shown.

The system-wide maximum number of flow relations between the start node and any other diagram node.

The value must be an integer between 1 and 100.

The default value is 50.

The filter that is applied, by default, to search results. The value must be the UUID of the filter.

To find the UUID, open the Collibra environment and click in the Search box. Click the name of a search filter. In the address bar you will see the UUID of the filter.

Note Specifying a default search filter in the application will override the default filter that you specify here.

Placeholder text that appears in the Search field before a user enters search text.

The default text is "Search in Collibra".

Enable or disable the use of a keyboard shortcut to search for selected text in Collibra Data Intelligence Platform from within your browser or another application.

• True (default): Users can use the keyboard shortcut you specify in the following setting to search in Collibra Everywhere.
• False: Keyboard shortcut is disabled.

The keyboard shortcut to search for selected text in Collibra Data Intelligence Platform from within your browser or another application.

Tip The keyboard shortcut has to be a combination of Control, Alt or Shift with one letter or number. On macOS you can also use the Command key.

Option to enable automatic hyperlinking within Collibra for Desktop.

With this option enabled, the name of an asset automatically becomes a hyperlink when you fill out a text attribute.

This option only works if the Enable hyperlinking option in Collibra Console is also enabled.

Option to enable workflows in Collibra Everywhere.

This allows you to complete tasks or start a workflow in the app. The available workflows depend on the ones that you add to the Global workflows and Asset workflow configuration.

The Recommender helps users by suggesting relevant business assets and data sets, based on certain relation types and the past actions of similar users.

• True: Recommender is enabled.
• False (default): Recommender is disabled.

This feature only works if Analytics is enabled. You can enable Analytics in section 1 General of the DGC service configuration.

Option to automatically upgrade Collibra Everywhere when a new version is available.

• True (default): Collibra Everywhere is automatically upgraded when a new version is available.
• False: You need to manually upgrade Collibra Everywhere when a new version is available.

Note If you enable automatic updates, you have to whitelist the S3 bucket collibra-otg-desktop-installers in the region eu-west-1.

Option to allow users to edit personal settings in Collibra Everywhere.

• True (default): Users can edit personal settings.
• False: Users cannot edit personal settings.

The list of workflows that is available in the app's main menu.

Enter the UUIDs of the workflows. An example workflow could be "Create issue".

The list of workflows that is available on an asset page in the app.

Enter the UUIDs of the workflows. An example workflow could be "Ask the expert".

The workflows that are available if there are no search results found.

Enter the UUIDs of the workflows. An example workflow could be "Propose new business term".

The filter that is applied, by default, to your search results. The value must be the UUID of the filter.

This filter overrules any search filter that is set in the app.

To find the UUID, open the Collibra environment and click in the Search box. Click the name of a search filter. In the address bar you will see the UUID of the filter.

Option to enable workflows in Collibra for Mobile.

This allows you to complete tasks or start a workflow in the app. The available workflows depend on the ones that you add to the Global workflows and Asset workflow configuration.

The list of workflows that is available in the app's main menu.

Enter the UUIDs of the workflows. An example workflow could be "Create issue".

The list of workflows that is available on an asset page in the app.

Enter the UUIDs of the workflows. An example workflow could be "Ask the expert".

• True: Tableau metadata API is enabled. This enables you to ingest Tableau 2020.2 or newer into Data Catalog.
• False: Tableau metadata API is disabled. If you ingest Tableau 2020.2 or newer, the ingestion will fail. This prevents data loss of manually added relations and attributes.

Note This setting is only applicable if you are using the latest Collibra UI.

A comma-separated list of your on-premises Tableau URLs. This list represents the values that appear in the Tableau URL or endpoint drop-down list on Tableau Server asset pages. You select a URL when setting up a connection to the on-premises Tableau instance.

• True: Enable ingestion and technical lineage for Power BI and Tableau via Edge.
• False (default): Disable ingestion and technical lineage for Power BI and Tableau via Edge.

• True: Enable technical lineage for data sources by using JDBC connections via Edge. For an overview of the supported data sources, go to the Technical lineage documentation.
• False (default): Disable technical lineage for data sources by using JDBC connections via Edge.