Please don't enter any sensitive information, such as passwords, into this form.
If sensitive information must be provided, let us know and we'll direct you to send an encrypted email to the appropriate address for secure transfer.

Select the best time for us to work with you.

If your account should be associated with multiple companies but there is no [Organization] dropdown field above (or a company is missing), then please specify the company name here.

Please reserve Urgent for emergency situations. E.g. business-critical activities are halted.

Your current Data Workbench (Quadrate or ERP²) version can be found under the "File > About" menu.

Your current Stewardship Tier (DSP) version can be found in the footer of each page. In older versions, it is found in the 'Change Settings' menu in the top-right corner.

The ID number can be copied by clicking your tenant name in the user menu in the top-right corner of the Knowledge Platform. More details here: https://support.syniti.com/hc/en-us/articles/4419712456471

If possible, please let us know the text that appears in your web browser's address bar when you are using the Syniti Knowledge Platform (SKP). In particular, it is helpful for us to see the URL of any page where you are encountering an issue. For example, https://knowledge.syniti.eu or https://knowledge.syniti.com/admin/categories.

Your current Data Replication (SDR or DBMoto) version can be found in the Management Center under the "HELP > About..." menu.

Your current Replicate version can be found in the Management Center under the "HELP > About..." menu.

Enter the email address of an administrator Account in your Catalog.

Leave this blank unless you have multiple custom dashboard VPNs.

Customers with a Syniti cloud deployment of the Stewardship Tier should NOT tick this checkbox. Our CloudOps team will be able to set up the VPN needed for custom dashboarding.

Leave this blank unless you can list gateway details such as the vendor, platform, and/or software version. We may be able to provide a complete VPN configuration file. Otherwise, we'll provide VPN configuration information that will need to be entered into the gateway.

Example: 10.20.30.40

Example: 10.20.30.0/24

Leave this blank unless you require the Catalog to use a specific /24 subnet for its end of the VPN. We will use 172.16.0.0/24 as a default if it doesn't conflict with the SQL Server subnet.

Leave this blank to use the default label, which is the name of the SQL Server Database.

1433 is the default port for SQL Server.

We recommend creating a database named [dgDashboards] to populate with data for the custom dashboards. However, you are free to specify any SQL Server database.

We recommend creating a read-only login named [quicksight_readonly] to allow the custom dashboards to access your specified database. However, you are free to specify any SQL Server login.

The SQL Server login's password must be sent via encrypted email to T1@syniti.com.

If SSL is used, the data source server's certificate MUST be issued by a publicly trusted certificate authority. Self-signed certificates and certificates signed by internal CAs will be rejected.

List the email address of each Catalog Account for which you wish to enable (or disable) custom dashboard authoring. Note that your Catalog is limited to 10 of these custom dashboard author Accounts.

Please enter any questions about these SSO configuration requirements into the [Description] field above. --newline-- 1) The Identity Provider must provision users in predefined groups that can be aligned with the 4 user roles in the Catalog (Admin, Business Admin, Author, & Viewer). --newline-- 2) The Identity Provider must specify a user's email address, full name, group membership, & immutable ID via an identity token or endpoint. In the case of SAML, the identity token is called the assertion. --newline-- 3) The Identity Provider must use a 2-hour or longer lifespan for session tokens and identity tokens. --newline-- 4) You must provide a list of each existing user in your Catalog to be migrated over to SSO. The list should include email address, unique ID from the Identity Provider, and user role in the Catalog (Admin, Business Admin, Author, & Viewer). --newline-- 5) You must provide 4 sets of user credentials for testing SSO. 1 set is required for each of the 4 user roles in the Catalog. Send the credentials via encrypted email to T1@syniti.com.

Knowledge Platform engineers may need to request additional technical details from your company's IT and/or Security team(s). List the email address of each person who should be included in these requests.

Enter "tbd" if you will be providing this information later. List each user email domain that might ever need to access your Catalog.

Listed providers are certified with the Catalog. Any provider using the SAML 2.0, OAuth 2.0, or OpenID Connect protocol is also supported.

WARNING: If Okta is your organization's Identity Provider, then we only support OpenID Connect. Okta configurations with SAML 2.0 will often break the 2-hour lifespan requirement listed above.

Americas: https://api.syniti.com/saml/metadata.xml --newline-- EMEA: https://api.syniti.eu/saml/metadata.xml

We strongly recommend providing a URL link to the metadata XML so that we can automatically monitor for updates. This allows you to change certificates or other configurations without the need to contact us. Alternatively, you can attach static metadata in an XML file.

The Client ID and Secret must be sent via encrypted email to T1@syniti.com.

Enter "tbd" if you will be providing this information later. Group names should be provided exactly as they appear in the Identity Provider's group membership claims. 1 group is needed for each of the 4 user roles in the Catalog (Admin, Business Admin, Author, & Viewer).

Enter "tbd" if you will be providing this information later. List the names of the 4 required attributes exactly as they appear in the identity token or endpoint. In the case of SAML, the identity token is called the assertion.

Add file or drop files here

    You must be signed in and eligible to submit a request

    Sign in

    Reasons why you may not be eligible after signing in:

    • Your registration is linked to a company without an active subscription or maintenance agreement for Syniti software.
    • Your registration is linked to a company that purchased Syniti software through a partner (such as SAP) that asks for requests to be submitted in their own Support system.