Skip to main content
Project settings give administrators and developers control over who can access the project, which models and tools are available, how the runtime behaves, and what security and compliance policies the system enforces. The Settings section covers membership, API keys, model configuration, runtime tuning, data retention, integrations, agent behavior overrides, PII protection, and channel policies. To access Settings, navigate to your project and select Settings from the sidebar.

​
Before You Begin

  • Most settings pages require Admin access. Developers can view settings but can’t modify membership, API keys, or security controls.
  • Adding project members requires them to exist as workspace members. Only workspace Owners and Admins can invite new people into the workspace.
  • Model configuration requires at least one LLM provider configured at the workspace level under Admin → Models.
  • Git integration requires a repository URL and authentication (SSH key or personal access token) prepared in advance.

​
Accessing Project Settings

Navigation: Project → Settings

General

Membership, API keys, models, runtime config, data retention, variables, and localization.

Integrations

Git version control and authentication profiles for connectors.

Agent Behavior

Behavior profiles, alerts, human handoff, and agent assist.

Security and Observability

PII protection, public API access, attachments, and omnichannel.

Catalog

Response templates, imported modules, publishing, and trace dimensions.

Advanced

LLM thinking, task prompts, escalation templates, and project deletion.