Use Tenant Settings to manage Tenant-scoped configuration in the PaletteAI UI. From this page, you can manage Tenant configuration such as display information, integrations, OpenID Connect (OIDC) group access, target namespace access control, model access control lists, per-Tenant and per-Project GPU limits, Tenant compute inventory, Compute Configs, Scaling Policies, and Model as a Service Mappings.
A Tenant represents an organization or major division within your company and serves as the top-level organizational unit in PaletteAI.
Delete a Tenant when the organization or division it represents is no longer needed. Tenant deletion is permanent and removes the Tenant from the PaletteAI hub cluster.
The PaletteAI Helm chart renders template ConfigMaps into the Helm release namespace. Each template holds a default list of Kubernetes PolicyRule entries used when defining Project-scoped access for a persona tier.
A Tenant groups one or more Projects under a single administrative boundary. Platform engineering teams manage Tenants: they configure Tenant-level settings and share Hugging Face and NVIDIA NGC integrations with Projects, set GPU quotas, control access, and create tenant-scoped resources that Projects can consume. This page collects the common ways to manage a Tenant and links to the detailed guide for each task.
This page provides troubleshooting guidance for common issues when creating and managing Tenants.