Skip to content

Customer Operations Tenant ​

Customer operations tenants are available in private deployments. They give customer operations staff a restricted management entry to maintain business tenants in the deployment without granting all permissions of the system operations tenant.

Who Can Use It ​

Users must meet both conditions to access customer operations capabilities:

  • Their tenant has the Customer Operations Tenant type (CUSTOMER_OPS);
  • They have the Super Administrator role (SUPER_ADMIN) in that tenant.

A deployment can have at most one customer operations tenant. A system operations tenant administrator creates or designates it. Customer operations staff cannot elevate their own tenant type or permissions.

What You Can Do ​

The customer operations tenant's System Management entry provides only the following four capabilities.

After signing in, its super administrators can access them under System Management.

CapabilityAvailable ActionsData Scope
User ManagementFind and maintain users, manage account linking and merging, and perform related operations.Users outside the system operations tenant. Members of the system operations tenant cannot be viewed or managed.
Model Configuration CenterMaintain model aliases, service endpoints, and keys for eligible business tenants.Available only in private deployments with a license that includes private models. Shows only tenants eligible for private models, excluding the system operations tenant.
License ManagementView license status and upload records, upload or register licenses, and assign purchased packages to regular business tenants.License status and upload records are shared across the instance. Packages can be assigned only to regular business tenants, excluding system and customer operations tenants.
Audit LogsSearch, filter, and view operation audit records across tenants.Records outside the system operations tenant. The server enforces exclusion of system operations tenant records.

Common Use Cases ​

  • Use Model Configuration Center to connect or adjust private models for business tenants.
  • Use License Management to renew a private deployment instance, import a new license, or assign purchased packages to business tenants.
  • Use Audit Logs to trace sensitive operations within business tenants.
  • Use User Management to handle account ownership, account linking, or duplicate accounts in business tenants.

Scope and Limits ​

A customer operations tenant does not replace the system operations tenant. It provides only the four explicitly allowed capabilities needed for routine customer operations. System operations tenant data is outside the customer operations management scope in User Management, Model Configuration Center, License Management, and Audit Logs.