Organization Configuration Window
To display the Organization Configuration window, hover over your organization name, and then click the Configuration icon: .
The system administrator can set system limits on most of these properties at a global level to affect all organizations.
Organization 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 System Data Collector | Enables users to select the system Data Collector as the authoring Data Collector for creating new pipelines. Enable the system Data Collector as an authoring Data Collector to let users create pipelines when they cannot access a registered Data Collector that meets the requirements for an authoring Data Collector. The system Data Collector cannot be used for data preview or pipeline validation. Only enable the system Data Collector if the system Data Collector is installed. Disable the system Data Collector to force users to create pipelines with a registered Data Collector. Designing pipelines using an authoring Data Collector that is a newer version than the execution Data Collector can cause errors. |
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. |
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. |
Maximum number of days before job status history is purged | Maximum number of days to retain the job history from each retained job run. |
Maximum number of job runs | Maximum number of job runs to retain the job history for. |
Maximum number of scheduler runs | Maximum number of scheduled task runs to retain the details for. |
Maximum number of days before scheduler runs are purged | Maximum number of days to retain run details for each scheduled task. |
Inactivity period for session termination | Maximum number of minutes that a user session can remain inactive before timing out. |
Maximum number of days before time series metrics are purged | Maximum number of days that a job can be inactive before the metrics for that job are deleted. |
On the SAML tabs, you can configure SAML authentication for your organization.