# Manage Deployment Settings and System Models

Deployment settings affect the services available across the deployment.
Organization administration and deployment administration are different scopes.

## Configuration Has a Wider Scope

Deployment settings can affect every workspace using the service. User preferences affect an individual’s experience; organization settings affect that organization. Confirm the scope before changing a provider or system-model configuration.

System models can support background features such as search and automatic decisions. A working thread model does not establish that those separate features are configured. Use the verification and activation controls for the intended revision, then check the feature it supports in the target environment.

![The workspace selector appears above Personal, Workspace, and Admin settings.](/screenshots/current/settings-navigation.png)

## Before you start

Confirm deployment-administration permission and the target environment. A local
configuration check does not prove that QA or production has the same providers
or settings.

## Configure system models

1. Open **Settings → System** and the offered model configuration.
2. Review the current provider and credential-configured state.
3. Use **Configure**, **Add API key**, or **Replace API key** as appropriate.
4. Set endpoint fields and model mappings required by the form.
5. Use **Save and verify** and inspect the verification result.
6. Activate the intended revision where the flow requires activation.

Document search and decision features can use system models separately from a
user-selected thread model. Check each required service rather than
assuming a working chat provider makes every background feature ready.

## Review deployment configuration

Use the authorized configuration UI for available runtime settings. Read the
scope and validation errors before applying changes. Keep credentials in the
dedicated secret controls and verify that displayed configuration is redacted.

After a change, inspect the relevant service health and perform a bounded
feature check. If activation or verification fails, retain the current working
configuration while investigating. Do not use user-level preferences to work
around unavailable deployment capabilities.

Related: [provider integrations](/admin/integrations/),
[model selection](/threads/models/), and [usage](/admin/usage/).
