Skip to content

Settings Areas and Important Fields

What this page helps with

Tenant Settings are used after the initial setup is complete. This page explains which settings matter during ongoing operation and what kind of impact they have.

General

This area maintains the stable identity and visibility of the tenant.

Typical entries:

  • tenant name
  • operating mode
  • data home directory
  • access groups

Use this area when you need to:

  • rename a tenant more clearly
  • correct the data location
  • limit which users or groups can see the tenant

Connection

This area controls the technical connection to CPI and, where relevant, Edge.

Typical entries:

  • setup type
  • CPI platform
  • CPI URL
  • UI URL
  • authentication
  • Edge URL
  • certificates
  • SSL behavior
  • connection tests

This area matters most after:

  • password rotation
  • OAuth client changes
  • certificate replacement
  • URL or landscape changes

Best practice:

  • update one connectivity topic at a time
  • run the available test immediately after the change
  • save only after the result looks plausible

Query and sync behavior

This area controls how aggressively data is collected and prioritized.

Typical topics:

  • filter query
  • start time
  • download strategy
  • hot window
  • attachment behavior

These settings are always a balance between:

  • more detail and broader visibility
  • lower load and lower storage growth

If a tenant becomes heavy, this is often the first place to review.

AI scenarios

This area controls tenant-specific AI behavior where the platform allows it.

Typical settings:

  • whether a scenario is enabled
  • AI mode
  • sensitivity

Important:

  • tenant settings refine local behavior
  • they do not override a globally disabled platform decision

Jobs

This area controls recurring background work for the tenant.

Typical jobs include:

  • messages
  • iFlows or artifacts
  • alerts
  • payloads
  • archive
  • keystore sync

Typical fields include:

  • enabled
  • interval
  • source
  • retention-related values
  • scheduled time

Use this area carefully. Changes here influence:

  • freshness of visible data
  • system load
  • archive behavior
  • the amount of operational noise

Practical examples

Credential rotation

Update the relevant connection values, run the test, then save.

Reduce load on a busy tenant

Review query filters, hot window, attachment behavior, and job intervals before changing anything else.

Restrict visibility

Adjust access groups so only the intended teams can open and operate the tenant.

Common mistakes

  • changing multiple connection parameters at once
  • making sync intervals too aggressive
  • forgetting that attachment behavior increases storage and load
  • widening visibility accidentally through access-group changes