Configuring Organization Properties

A user with the Organization Administrator role can review and configure organization properties.

  1. In the Navigation panel, click Manage > My Organization.
  2. Configure the following general organization properties:
    General Property Description
    Organization Name Name of the organization.
    Valid Domains List of trusted domains that can make authentication requests to Control Hub on behalf of your organization.
  3. Click Save to save changes made to general properties.
  4. Click Advanced to configure advanced organization properties.

    Some of the advanced properties can be modified only up to the maximum system limit. For example, the system limit for the maximum number of job runs is 100. You can configure a lower limit for the maximum number of job runs, such as 50, but cannot configure a limit higher than 100.

  5. Configure the following advanced properties:
    Advanced Property Description
    Enable events to trigger subscriptions Enables events so that Control Hub can trigger subscriptions for organizations. Disable events if you do not want users to use subscriptions.
    Enable WebSocket Tunneling for UI Communication Enables execution engines to use the WebSocket Secure (wss) protocol to establish a WebSocket tunnel with Control Hub over an encrypted SSL/TLS connection.
    Important: Before you disable this property, you must configure all engines to use the HTTPS protocol to directly communicate with the web browser.
    Enable Snowpark Preview Enables previewing data in Transformer for Snowflake pipelines when using the Transformer for Snowflake engine hosted and managed by StreamSets. Enabling this option allows Snowflake data to leave Snowflake servers for the preview.

    Not applicable when your organization uses a deployed Transformer for Snowflake engine.

    Disable this option to prevent all users in the organization from using data preview in Transformer for Snowflake pipelines.

    For more information, see the Transformer for Snowflake documentation.
    Enforce permissions during object access Enables permission enforcement to secure the integrity of organization data. Disable permission enforcement if you want all users in the organization to have full access to all objects.
    Default authoring engine timeout Number of milliseconds that Control Hub waits for a response from an authoring engine before considering the engine as not accessible.

    When the engine is not accessible, you cannot select that engine as the authoring engine when designing pipelines or creating connections.

    In most cases, the default value should be appropriate. Try increasing the value when the authoring engines are running, but the authoring engine selection pages indicate that engines are not accessible.

    Users can override this default value when configuring their browser settings within the My Account window.

    Default is 5000 milliseconds.
    Execution engine heartbeat interval Maximum number of seconds since the last reported execution engine heartbeat before Control Hub considers the execution engine - Data Collector, Data Collector Edge, or Transformer - as unresponsive. In most cases, the default value of 300 seconds, or five minutes, is sufficient.

    System limit is 1,800.
    Maximum number of days before job status history is purged Maximum number of days to retain the run history for each job and draft run.

    System limit is 7.
    Maximum number of job runs Maximum number of job and draft runs to retain the run history for, including runs of job instances started from a job template.

    System limit is 100.
    Enable Multiple Job Start Synchronization Enables Control Hub to synchronize the start of multiple jobs. Use to ensure that the number of pipelines running on an engine does not exceed the configured resource threshold. Enabling the property can cause jobs to take longer to start.

    When disabled, the number of pipelines running on an engine can exceed the configured Max Running Pipeline Count only if you start multiple jobs at the exact same time using the scheduler or using the Control Hub REST API. For more information, see ../Deployments/ResourceThresh.html#concept_zxb_spx_t4b.
    Default AWS Environment Feature Version Default feature version to use for new AWS environments.
    Default Azure Environment Feature Version Default feature version to use for new Azure environments.
    Default GCP Environment Feature Version Default feature version to use for new GCP environments.
    Default Kubernetes Environment Feature Version Default feature version to use for new Kubernetes environments.
    Default Self-Managed Environment Feature Version Default feature version to use for new self-managed environments.
    Show the Stage Library Mode UI field for CSP Deployments Displays the Stage Library Mode property for deployments so that you can use the user-provided stage library mode.
    Note: Use caution when enabling this property. In most situations, you can use the default managed stage library mode.
    Maximum number of scheduler runs Maximum number of scheduled task runs to retain the details for.

    System limit is 500.
    Maximum number of days before scheduler runs are purged Maximum number of days to retain run details for each scheduled task.

    System limit is 30.
    Inactivity period for session termination Maximum number of minutes that a user session can remain inactive before timing out.
  6. Click Save to save changes made to advanced properties.

    It can take a few minutes for the changes to take effect.

  7. Click Configure SAML to enable SAML authentication for the organization.

    For more information about configuring SAML, see ../Authentication/SAML.html#concept_kkx_wgm_jrb.