Tenant Settings Reference

This page is the short working reference for people who maintain an existing CPI configuration.

Settings area guide

Area	What it controls in practice	Who typically changes it
General	name, mode, data home, and ownership context	admin or responsible operator
Connection	CPI access, Edge access, OAuth, certificates, host details	admin or technical operator
Query and Sync	query windows, start points, download scope, hot behavior	admin with monitoring responsibility
AI Scenarios	optional tenant-specific AI switches and sensitivity	admin or controlled pilot owner
Jobs	sync timing, archive behavior, runtime collection cadence	admin or system-oriented operator

Change	Typical effect in the product	Recommended follow-up
connection change	can restore or break tenant communication	run a connection test
query or start-time change	changes which runtime data can be collected	check messages and archives after the next cycle
visibility or group change	changes who can see the tenant	confirm expected user access
job interval change	changes how fresh lists and alerts become	watch the next sync cycle

Topic	Why it exists	Operational boundary
tenant mode	separates different operating styles or sources	do not change casually on a live tenant
data home	keeps tenant data assigned to the intended environment	align with company responsibility
access groups	restrict tenant visibility to the right audience	review after role changes
sync scope	balances completeness and runtime cost	widen only with a clear reason

For shared role language, visibility, masking, and cross-module state meanings, see Product Reference and Shared Product Values.

See: