-
Notifications
You must be signed in to change notification settings - Fork 0
Gen3 Admin Settings
- Open Settings for deployment-wide operator policy.
- Review session, MFA, branding, and object-storage controls; use Backup & Restore for CNPG schedules and restore workflows.
- Distinguish these from tenant Account Settings—different plane.
- Save changes during a maintenance window when sessions may reset.
Operator settings affect every tenant’s hosting environment; tenant settings only affect tenant-facing policy inside the tenant app.
Settings is the Control Panel route for deployment-wide configuration that does not belong to a narrower admin page. It combines branding, operator MFA posture, session timeout policy, and reusable object storage configuration. CloudNativePG backup schedules, on-demand runs, and staged restore workflows live on Backup & Restore.
Use this section to manage the deployment display name and branding assets surfaced across GT AI OS.
This section controls the Control Panel operator MFA posture. It is distinct from tenant-user MFA management on Users.
Use this section to adjust the deployment-wide idle timeout applied across GT AI OS sessions.
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.
Use this page when the change affects the deployment as a whole rather than one business function such as licensing, email, or model configuration.
- Change one configuration area at a time.
- Save the update.
- Verify the affected surface before moving to the next section.
This keeps it clear which deployment-wide setting caused an observed change.
- 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.