Self-service tenant configuration
Learn about self-service tenant configurations to empower administrators to manage their own tenant settings
Our support team is always happy to connect with you, and always has your back! But, let's face it, when it comes to this straightforward process for configuring your tenant by yourself – you're probably eager to dive in and get it done.
Do you have ROLE_ADMIN_TENANT Access permissions? If so, dive into this topic, specifically designed with your Tenant Configuration needs in mind! For more information, see topic View and edit tenant configuration.
Here's a rundown of the self-service tenant configuration parameters you can customize:
Cleanse configurations
Explore the Cleanse configurations to tailor how addresses are cleansed, verified, and processed, ensuring they meet your specific needs:
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Address cleanser licensed country | List of countries where address cleansing is supported based on your current license. Contact your Reltio
Account Manager to update your license. Note: View only mode | Active values (license-dependent) | Licensed countries | Address Cleansing Properties |
| Address cleanser process | List of applicable address cleanser processes supported based on your current license. Contact your Reltio Account Manager to
include CASS2 or SERP, and Reltio Support for other processes. For more information, see topic Need some help? Note: View only mode | Active values (license-dependent) | Verified
| Address Cleansing Properties |
| Verification status mapping | Address Verification Code (AVC) shows how closely an input address matches reference data. AVC mapping and status offer flexibility in managing the verified status of standardized addresses returned by the address cleansing function. Contact Reltio support to update the configuration. For more information, see topic Need some help? Note: View only mode | Active values (license-dependent) | Verified
| Understanding Address Verification Code |
| Address cleanser default country | If you don't specify a country in your request, the system uses the United States (USA) as the default country for Loqate verification. A 3-char ISO country code is preferred. | USA | Country code defined in your configuration | Address Cleansing Properties |
| Return unverified status | Enable this option to return only status fields for Unverified addresses in address cleansing. | Disabled | Disabled
| Address Cleansing Properties |
| Return data by status | Select the statuses for which the address cleanser should return results. Note: You have the option to select multiple values. | Verified | Verified
| Understanding Address Verification Code |
| Ignore unverified results | Unverified results are not returned when this parameter is enabled. Applicable only for SERP and CASS2. | Enabled | Enabled
| Address Cleansing Properties |
| Handle duplicate data | Enable to eliminate duplicate values in address fields in preprocessing. | Disabled | Disabled
| Address Cleanse Options |
| Output casing | Select the casing format for address cleanser output fields. | Title | Title
| Address Cleanse Options |
| Output language | Specify the ISO 15924 code for the output encoding. Use 'Native' for the language of the country in the input address, or 'Latn' for English. | Native | Native
| Address Cleanse Options |
| Suppress address fields in output | Specify a comma-separated list of fields to exclude from the Address field output. | n/a | Address fields (user input) | Address Cleanse Options |
| Use raw value as default when lookup fails | Enable to use the raw value as cleanser input when the lookup value is not found. | Disabled | Disabled
| Configuring Cleanse to use Raw Value when lookup fails |
Nested partial override
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Nested partial override | A partial override for nested attributes lets you update specific parts of an entity or a relationship. Enable to allow partial override in nested attributes. | Disabled | Disabled
| enableNestedPartialOverride option |
Resolve lookup code
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Resolve lookup code | A lookup code is used to identify a lookup value. E.g., using "AS" to identify the lookup value "Abdominal Surgery". Enable to resolve and store lookup codes corresponding to raw values in the data. If enabled, raw values will be lost. | Disabled | Disabled
| Resolve attribute or tenant lookups |
Tenant per role security
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Tenant per role security | Enable to reuse the same role names and definitions across tenants. Note: Grant users different rights for different tenants. | Enabled | Enabled
| Role assignments behavior |
Export file compression
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Export file compression | Choose a compression format for your exported files. We recommend using GZIP. | GZIP | GZIP
| What compression file types does export support? |
Match strategy
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Match strategy | The Match Strategy parameter at the tenant level controls how the match engine operates while using your match rules. Select the appropriate matching configuration for your tenant. Merge on the fly is enabled / disabled at tenant level but can be updated for any entity type using metadata configuration. | Enabled with Merge on the fly disabled (recommended) | Enabled with Merge on the fly disabled (recommended)
| Tenant-level match strategy |
Search by operational value (OV)
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| Search by operational value (OV) | An OV is a dynamic value calculated in real-time, which is based on Survivorship Rules. Enable to allow search by operational values in the tenant. | Disabled | Disabled
| Search by Operational Value Only |
Role-based access control (RBAC) for RDM
| Parameter | Description | Default value | Allowed Values | Additional Info |
|---|---|---|---|---|
| RDM Role-based access control (RBAC) | Reference Data Management (RDM) is a product available on the Reltio Connected Customer 360 platform that enables you to define and maintain reference data for your MDM tenants and your enterprise in general. Enable RBAC to restrict access to RDM lookup values based on RBAC permissions configured in your linked RDM tenant. This ensures that MDM users only see and access RDM data they are authorized for, according to their roles. Important: Before enabling, ensure that RBAC permissions are properly configured in RDM. If RBAC permissions are not set, users may lose access to RDM lookup values. | Disabled | Disabled
| Role-based access control (RBAC) for RDM |