Skip to content

Gen3 Admin Settings

GT AI OS Release edited this page Jun 11, 2026 · 4 revisions

Settings

Start Here

  1. Open Settings for deployment-wide operator policy.
  2. Review tenant appearance, default chat preferences, chat media retention, session, MFA, and branding; confirm whether object storage is fully enabled in your build.
  3. Use Backup & Restore for CNPG schedules and restore workflows when that route is enabled.
  4. Distinguish these from tenant Account Settings—different plane.
  5. Save changes during a maintenance window when sessions may reset.

Why this matters

Operator settings affect every tenant’s hosting environment; tenant settings only affect tenant-facing policy inside the tenant app.

Details

Settings is the Control Panel route for deployment-wide configuration that does not belong to a narrower admin page. It combines branding, tenant appearance, default chat window preferences, chat media retention, operator MFA posture, session timeout policy, and reusable object storage configuration. Sticky in-page section tabs link to each card. CloudNativePG backup schedules, on-demand runs, and staged restore workflows live on Backup & Restore when that workspace is enabled.

Main sections

Branding and tenant appearance

Use this section to manage the deployment display name, branding assets, and tenant appearance surfaced across the tenant app (not Control Panel chrome or Compliance Mode frames):

  • Primary accent — buttons, sidebar highlights, chips, and interactive emphasis
  • Icon backdrop — outer fill behind the sidebar logo and collapsed menu icon so square assets blend into menu chrome
  • Default color scheme — organization default light or dark mode for new tenant sessions (users can override per account in Accessibility)

Accent variant rows support grouped core/readable colors, soft tints, per-row reset, and compact layout for large palettes.

Operator security

This section controls the Control Panel operator MFA posture. It is distinct from tenant-user MFA management on Users.

Session timeout policy

Use this section to adjust the deployment-wide idle timeout applied across GT AI OS sessions.

Default chat window preferences

Operators set platform defaults for tenant Chat Window Preferences: request-process visibility, supporting details, message details row, message action button labels (icons vs icons-with-labels), response behavior (streaming cadence), and chat width preset. Tenant users can override and restore defaults from GT Chat.

Chat media retention

Configure how long chat-attached images and audio remain available before automatic cleanup. This policy applies deployment-wide to conversation-scoped media artifacts; adjust during maintenance windows when retention changes could affect in-flight reviews.

Object storage

This section defines reusable object-storage targets—S3-compatible bucket endpoints, path prefixes, and Kubernetes secret references—that backup and related deployment storage workflows consume. Configure object storage here before enabling CNPG backup automation on Backup & Restore.

When object-storage UX is gated in your build, this card shows an under development notice instead of live credential and preflight controls. Deep links such as #object-storage-title still land on the section for runbook cross-references.

When to use Settings

Use this page when the change affects the deployment as a whole rather than one business function such as licensing, email, or model configuration.

Recommended workflow

  1. Change one configuration area at a time.
  2. Save the update.
  3. Verify the affected surface before moving to the next section.

This keeps it clear which deployment-wide setting caused an observed change.

Best practices

  • Treat branding and security changes as separate decisions.
  • Review session timeout changes against evidence from Access Logs.
  • Confirm object-storage settings on this page before enabling or changing CNPG backup automation on Backup & Restore.
  • Use the deployment display name deliberately because it appears across shared product surfaces.

Related pages

Clone this wiki locally